This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: $(exeext) misused in Makefile.in?
- To: tprince at cat dot e-mail dot com
- Subject: Re: $(exeext) misused in Makefile.in?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 16 Jul 1998 21:04:17 -0600
- cc: egcs-bugs at cygnus dot com
- Reply-To: law at cygnus dot com
> I'm wondering whether the $(exeext) really belongs in
> gcc/Makefile.in in the locations where stage1, 2, 3 are being built
> with the settings "CC=stage1/xgcc$(exeext) -B........" etc.
I think so. Imagine trying to do a 3-stage on cygwin -- seems to me
you want to make sure that you find xgcc.exe.
> to me like $(exeext) is being used correctly elsewhere but
> commands like "stage1/xgcc.exe" rather than "stage1/xgcc" don't
> always work even under cygwin32.
?!? Why?
> Another thing; under w95/cygwin32, include files aren't always
> picked up via -L./config; it seems more reliable to change the
> files so that this search path isn't needed. I can't blame egcs for
> that, however.
-L is not for include files. -I is for include files. If they are
not being correctly found, then that's a bug.
jeff