gershonh
asked on
gcc configuration problem
I am to compile gcc under winNT
after running "config.BAT winnt i386"
i run "make bootstrap" and the make finds
errors in the make file "Makefile:117 *** missing
separator"
line 117 is "@SET_MAKE@"
Thanks
after running "config.BAT winnt i386"
i run "make bootstrap" and the make finds
errors in the make file "Makefile:117 *** missing
separator"
line 117 is "@SET_MAKE@"
Thanks
Check up the separator in the previous line.
Most probably your line begins with space although it must begin with tab.
Andrew Rodionov
Andrew Rodionov
ASKER
Adjusted points to 75
ASKER
I think i have a problem with the configure.bat
I'm not sure that doing everything right
do you know if running (I have sed 3.02)
"configure winnt i386"
and then
"make bootstrap"
is the right way to install gcc
I'm not sure that doing everything right
do you know if running (I have sed 3.02)
"configure winnt i386"
and then
"make bootstrap"
is the right way to install gcc
What type of gcc are you using?
I know at least three ports: cygnus, mingw32 and djgpp+rsxntdj. There are some differences between them.
So give more information about it.
Andrew Rodionov
I know at least three ports: cygnus, mingw32 and djgpp+rsxntdj. There are some differences between them.
So give more information about it.
Andrew Rodionov
ASKER
I have cygnus already installed
and i want to compile gcc (I'll need gcc cross compiler at the
end) but now i want to be able to compile a native version.
but my problem is still in the configuration part , my makefile
is filled with unresolved expersions @.. something .. @ do you
know what should I do with them
and i want to compile gcc (I'll need gcc cross compiler at the
end) but now i want to be able to compile a native version.
but my problem is still in the configuration part , my makefile
is filled with unresolved expersions @.. something .. @ do you
know what should I do with them
ASKER
Adjusted points to 110
OK. I've built bash using cygwin.
I've run ./configure without any parameters and got Makefile. No warnings, no errors... ;)
Then I've comment out $(srcdir)/configure target and simply run make.
I haven't ( (un)fortunately ;) "unresolved expersions @.. something .. @" that you talk about. Was your configuration process successful? Show some lines with your problem "unresolved expersions".
WBR, Andrew Rodionov
I've run ./configure without any parameters and got Makefile. No warnings, no errors... ;)
Then I've comment out $(srcdir)/configure target and simply run make.
I haven't ( (un)fortunately ;) "unresolved expersions @.. something .. @" that you talk about. Was your configuration process successful? Show some lines with your problem "unresolved expersions".
WBR, Andrew Rodionov
if you still have @SET_MAKE@ meta-tags in your Makefile, your configuration did not run properly, these tags should have been replaced
ASKER
do you know what might be the problem with the configuration
all I did was
1. Installed cygwin
2. extracted gcc
3. ran "configure winnt i386" (I have SED)
4. configure returned
"Copy File...."
5. ran "make" and the maker tells me that
"Makefile:117 *** missing separator"
line 117 is "@SET_MAKE@"
do you know what might be the problem with the configuration
batch file
all I did was
1. Installed cygwin
2. extracted gcc
3. ran "configure winnt i386" (I have SED)
4. configure returned
"Copy File...."
5. ran "make" and the maker tells me that
"Makefile:117 *** missing separator"
line 117 is "@SET_MAKE@"
do you know what might be the problem with the configuration
batch file
ASKER
Adjusted points to 150
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you use cygwin, you need to use ./configure in your bash
ASKER
I followed your instructions and now i've got the
make file.
But when I try to build using "make bootstrap"
I get MAKE[2]: *** [bootstrap] Error 2
make file.
But when I try to build using "make bootstrap"
I get MAKE[2]: *** [bootstrap] Error 2
> MAKE[2]: *** [bootstrap] Error 2
sounds like a subsidary make fails.
Could you please test a simple target from Makefile, so that we are shure that there is no longer a syntax (or whatever) problem in this Makefile.
Thing i should work if you use such a target together with make -n
sounds like a subsidary make fails.
Could you please test a simple target from Makefile, so that we are shure that there is no longer a syntax (or whatever) problem in this Makefile.
Thing i should work if you use such a target together with make -n
Yes, ahoffmann is right.
And make sure that `bootstrap' is a valid taget for your Makefile.
Abdrew Rodionov
And make sure that `bootstrap' is a valid taget for your Makefile.
Abdrew Rodionov