Re: Building a cross compiler Solaris to Cygwin

[Brian Ford <ford at vss dot fsi dot com>]

Christophe LYON wrote:

> gcc -DHAVE_CONFIG_H -I. -I../../binutils-20040312-1/ld -I.
> -D_GNU_SOURCE
> -I. -I../../binutils-20040312-1/ld -I../bfd
> -I../../binutils-20040312-1/ld/../bfd
> -I../../binutils-20040312-1/ld/../include
> -I../../binutils-20040312-1/ld/../intl -I../intl
> -DLOCALEDIR="\"somepath/share/locale\""  -O2 -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes  -c
> ../../binutils-20040312-1/ld/pe-dll.c
> ../../binutils-20040312-1/ld/pe-dll.c:29: stdint.h: No such file or
> directory
> make[3]: *** [pe-dll.o] Error 1

This was introduced by this change:

2004-03-08  Danny Smith  <dannysmith@users.sourceforge.net>

        * pe-dll.c (pe_dll_generate_implib): Skip sections marked as
        private when building implib.

so I thought I'd direct this to the binutils mailing list for comment.

> My problem is that I haven't been able to find a description of the
> current way of building a cross compiler for Cygwin... except for the
> build-cross-gcc script mentionned above.

Not considering the bug above, building a cross toolchain from Solairs to
Cygwin shouldn't be different than building any other cross toolchain (he
says having never built that particular cross).  See
http://www.objsw.com/CrossGCC/ for generic instructions.

HTH.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/