• C

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
gershonhAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DVBCommented:
Check up the separator in the previous line.
0
Andrei RodionovCommented:
Most probably your line begins with space although it must begin with tab.

Andrew Rodionov
0
gershonhAuthor Commented:
Adjusted points to 75
0
Redefine Your Security with AI & Machine Learning

The implications of AI and machine learning in cyber security are massive and constantly growing, creating both efficiencies and new challenges across the board. Check out our on-demand webinar to learn more about how AI can help your organization!

gershonhAuthor Commented:
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
0
Andrei RodionovCommented:
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
0
gershonhAuthor Commented:
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
0
gershonhAuthor Commented:
Adjusted points to 110
0
Andrei RodionovCommented:
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
0
ahoffmannCommented:
if you still have @SET_MAKE@ meta-tags in your Makefile, your configuration did not run properly, these tags should have been replaced
0
gershonhAuthor Commented:
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
                     
       
0
gershonhAuthor Commented:
Adjusted points to 150
0
Andrei RodionovCommented:
gershonh, I'm using cygwin b20.1 on Windows98 now.

I downloaded gcc sources version 2.95.2 and extract them. I ran ./configure without _any_ parameters.
It means that the standard directory for installing GNU CC is `/usr/local/lib', but you can change it with `--prefix=DIR'. Also I didn't use `--host=MACHINE' although you can change it too.

I'd got automatically generated Makefile without any unresolved @...something...@ expressions. So read the INSTALL file and be sure that your cygwin configuration is valid (it includes PATH, mount points and possible symbolic links).

Hope this helps, Andrew Rodionov
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ahoffmannCommented:
if you use cygwin, you need to use  ./configure in your bash
0
gershonhAuthor Commented:
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
0
ahoffmannCommented:
>  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
0
Andrei RodionovCommented:
Yes, ahoffmann is right.

And make sure that `bootstrap' is a valid taget for your Makefile.

Abdrew Rodionov
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C

From novice to tech pro — start learning today.