Mail Archives: cygwin-developers/2000/03/28/18:42:37
Chris Faylor wrote:
> On Tue, Mar 28, 2000 at 10:52:05PM +0200, Corinna Vinschen wrote:
> >[...]
> > The top level Makefile.in contains
> >
> > -L$$r/$(TARGET_SUBDIR)/winsup
>
> > in CC_FOR_TARGET and CXX_FOR_TARGET which is wrong. It should be
> >
> > -L$$r/$(TARGET_SUBDIR)/winsup/w32api/lib
>
> This needs to be there in case somebody has an older winsup directory.
> I guess this needs to be added there. If this works, would you
> check it into sourceware?
Would you please first look into the patch file that is attached to my
mail from 0:29am? Those patches have allowed to build everything in one
go. The patch of winsup/cygwin/Makefile.in result in a cvs conflict in
the meantime but that is easy to solve.
> Also, can we simplify the DLL creation now using the newer linker?
Umm, I don't know. I'm happy for today to have the cross build working
anyway.
> >- in the mingw Makefile SUBDIRS computes to an empty list which results
> > in a syntax error in the "subdirs:" rule. I have temporary solved it
> > by adding a "dummy" entry.
>
> I don't see a syntax error. It seems to be legal to have:
>
> for f ; in stuff; do
>
> I don't know why you're seeing an error. Is the above command an error
> on your system?
It is a syntax error in bash which is the default /bin/sh on my linux
system. I'm sure to be not alone with that so I would prefer to change
the Makefile.in to be bash aware instead of forcing ash as /bin/sh.
> >- When trying to compile winsup/utils/strace.exe the include path
> > to winsup/w32api/include is missing. This may be a result of another
> > problem in the top level Makefile.in. CC_FOR_TARGET and CXX_FOR_TARGET
> > are containing
>
> Why is this? My Makefile.in has these lines:
> [...]
> So, unless MINGW_INCLUDES is being overridden, I don't see why the w32api/include directory
> is being excluded.
>
> cgf
I don't know yet. I will try it again tomorrow to see what's going on.
Corinna
- Raw text -