Re: preliminary cygwin debs

[Mumit Khan <khan at NanoTech dot Wisc dot EDU>]

On Fri, 12 Jan 2001, Bradley Bell wrote:

> On Fri, Jan 12, 2001 at 12:57:36AM -0500, Christopher Faylor wrote:
> > On Thu, Jan 11, 2001 at 10:00:22PM -0800, Bradley Bell wrote:
> > >On Thu, Jan 11, 2001 at 08:54:19PM -0500, Christopher Faylor wrote:
> > >>/whereever/configure --target=i686-pc-cygwin --host=i686-pc-linux --build=i686-pc-linux
> > >
> > >that's what I used (well, i386-cygwin) binutils works fine, gcc fails with
> > >this:
> > >
> > >_muldi3
> > >../../gcc-2.95.2-5/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> > >../../gcc-2.95.2-5/gcc/libgcc2.c:42: unistd.h: No such file or directory
> > >
> > >cygwin, of course, needs gcc...
> > >Am I missing a step, or do I have some other problem?
> > 
> > Dunno.  Sorry.
> 
> Hmm, well, does anybody else with experience in making a linux->cygwin cross
> compiler know what's going on here?  Is it my setup, or do I need to give
> extra options to 'configure'?
> 

Chris probably uses a "single tree" build with newlib and all the other 
stuff needed right there where GCC can find it at cross-build time, so
he's not going to run into this issue.

If you build cross-gcc separately, you'll need to install the runtime
where GCC can find it. I believe I have most of the info needed on my
cross-build HOWTOs for Cygwin and Mingw, but most if it by now woefully
out of date. I'll have to update those sometime very soon.

  http://www.nanotech.wisc.edu/~khan/software/gnu-win32/

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple