preliminary cygwin debs

preliminary cygwin debs

[Bradley Bell]

I've packaged up a Cygwin cross-compiler (compiling for cygwin, hosted on a
Debian (linux) system.)  These .debs are very alpha, to say the least, but
they can be found here, along with the source:
http://people.debian.org/~btb/src/cygwin/
The package names are binutils-i386-cygwin, gcc-i386-cygwin, and
libcygwin-dev, but even those are subject to change.  All three are built
from a single source tree, which is itself made of symlinks to the binutils,
gcc, and cygwin source packages included in the cygwin distribution.
If anyone knows of a better way to build a cygwin cross-compiler, please let
me know.

-brad

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

Re: preliminary cygwin debs

[Christopher Faylor]

On Thu, Jan 11, 2001 at 05:34:17AM -0800, Bradley Bell wrote:
>I've packaged up a Cygwin cross-compiler (compiling for cygwin, hosted on a
>Debian (linux) system.)  These .debs are very alpha, to say the least, but
>they can be found here, along with the source:
> http://people.debian.org/~btb/src/cygwin/
>The package names are binutils-i386-cygwin, gcc-i386-cygwin, and
>libcygwin-dev, but even those are subject to change.  All three are built
>from a single source tree, which is itself made of symlinks to the binutils,
>gcc, and cygwin source packages included in the cygwin distribution.
>If anyone knows of a better way to build a cygwin cross-compiler, please let
>me know.

I'm not sure what "better way" you're looking for.

Everything I build for cygwin is built from linux via a cygwin cross compiler.
You check out the sources, type in the appropriate configure options and type
"make".

It's pretty simple.

cgf

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

Re: preliminary cygwin debs

[Bradley Bell]

On Thu, Jan 11, 2001 at 11:51:53AM -0500, Christopher Faylor wrote:

> Everything I build for cygwin is built from linux via a cygwin cross compiler.
> You check out the sources, type in the appropriate configure options and type
> "make".
> 
> It's pretty simple.

You mean by that that you build and install them one at a time, right?
That's what I was trying to do, but I guess I just couldn't find the correct
configure options, so I essentially made it work like the old releases
(dev-src.tar.gz).  Can I see what you use for configure? 

-brad


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

Re: preliminary cygwin debs

[Christopher Faylor]

On Thu, Jan 11, 2001 at 05:54:27PM -0800, Bradley Bell wrote:
>On Thu, Jan 11, 2001 at 11:51:53AM -0500, Christopher Faylor wrote:
>
>> Everything I build for cygwin is built from linux via a cygwin cross compiler.
>> You check out the sources, type in the appropriate configure options and type
>> "make".
>> 
>> It's pretty simple.
>
>You mean by that that you build and install them one at a time, right?
>That's what I was trying to do, but I guess I just couldn't find the correct
>configure options, so I essentially made it work like the old releases
>(dev-src.tar.gz).  Can I see what you use for configure? 

/whereever/configure --target=i686-pc-cygwin --host=i686-pc-linux --build=i686-pc-linux

cgf

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

Re: preliminary cygwin debs

[Bradley Bell]

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?

-brad

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

Re: preliminary cygwin debs

[Christopher Faylor]

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.

cgf

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

Re: preliminary cygwin debs

[Bradley Bell]

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'?

-brad


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

Re: preliminary cygwin debs

[Mumit Khan]

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