Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Sat, 13 Jan 2001 20:46:47 -0800
From:	Bradley Bell <bradleyb AT u DOT washington DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	[bradleyb AT u DOT washington DOT edu: Re: preliminary cygwin debs]
Message-ID:	<20010113204647.A16848@washington.edu>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.12i

forgot to send this to the list.

----- Forwarded message from Bradley Bell <bradleyb AT u DOT washington DOT edu> -----

On Fri, Jan 12, 2001 at 05:29:34PM -0600, Mumit Khan wrote:
> 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.

compiled, or just the headers?

> 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/

I've had a look, and there's lots of good info there, just not very
applicable to the newer releases.  As I said, I did get the single-tree
method to work, using symlinks more or less as describe in the cross-gcc
faq.
For anyone else who wants to build from the separate -src.tar.gz files,
http://people.debian.org/~btb/src/cygwin/cygwin-1.1.7-1/debian/rules
is actually a fairly generic makefile.  Even on a non-debian system, one
could run 'debian/rules unpack' to set up the tree, then just configure,
make, make install.

-brad

----- End forwarded message -----

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

- Raw text -