Re: cross compilation problems

2000-10-24 Thread Steve Bowman
On Wed, Oct 25, 2000 at 01:56:41AM -0400, Roland McGrath wrote: > > > It is perfectly fine to cross-compile the hurd, and it should work fine. > > > It looks like his cross-compiler was not set up right. > > > > I just installed the debian package. What else needs to be done? > > Then the packag

Re: cross compilation problems

2000-10-24 Thread Steve Bowman
On Wed, Oct 25, 2000 at 12:02:50AM -0500, Daniel E . Baumann wrote: > > It is perfectly fine to cross-compile the hurd, and it should work fine. > > It looks like his cross-compiler was not set up right. > > I just installed the debian package. What else needs to be done? Well, since I haven't d

Re: cross compilation problems

2000-10-24 Thread Roland McGrath
> > It is perfectly fine to cross-compile the hurd, and it should work fine. > > It looks like his cross-compiler was not set up right. > > I just installed the debian package. What else needs to be done? Then the package may be broken. Look into the scripts and specs files and see how it is th

Re: cross compilation problems

2000-10-24 Thread Steve Bowman
On Wed, Oct 25, 2000 at 12:59:36AM -0400, Roland McGrath wrote: > > > it's trying to link with libc6 from Linux, which I > > > don't want it to do so what do I do? What is the proper way to cross compile? > > > > Don't. Compile hurd natively. > > It is perfectly fine to cross-compile the hurd,

Re: cross compilation problems

2000-10-24 Thread Daniel E . Baumann
> It is perfectly fine to cross-compile the hurd, and it should work fine. > It looks like his cross-compiler was not set up right. I just installed the debian package. What else needs to be done? Daniel E. Baumann E-ma

Re: cross compilation problems

2000-10-24 Thread Steve Bowman
On Tue, Oct 24, 2000 at 11:21:53PM -0500, Daniel E . Baumann wrote: > > Don't. Compile hurd natively. > > Yeah I think I ran into some problem trying to do that. Although I did not > craete a separate build directory as I was discussing with someone on IRC the > other night. Do you need to make

Re: cross compilation problems

2000-10-24 Thread Roland McGrath
> > it's trying to link with libc6 from Linux, which I > > don't want it to do so what do I do? What is the proper way to cross compile? > > Don't. Compile hurd natively. It is perfectly fine to cross-compile the hurd, and it should work fine. It looks like his cross-compiler was not set up rig

Re: cross compilation problems

2000-10-24 Thread Daniel E . Baumann
> Don't. Compile hurd natively. Yeah I think I ran into some problem trying to do that. Although I did not craete a separate build directory as I was discussing with someone on IRC the other night. Do you need to make a separate build driectory? > Useful for compiling gnumach but hurd builds fi

Re: cross compilation problems

2000-10-24 Thread Steve Bowman
On Tue, Oct 24, 2000 at 09:18:26PM -0500, Daniel E. Baumann wrote: > I attempted to compile the HURD from CVS by doing the follwing: > > [snip] > > it's trying to link with libc6 from Linux, which I > don't want it to do so what do I do? What is the proper way to cross compile? Do

cross compilation problems

2000-10-24 Thread Daniel E . Baumann
I attempted to compile the HURD from CVS by doing the follwing: CC=i386-gnu-gcc LD=i386-gnu-ld ./configure --build=i686-pc-linux-gnu --host=i386-gnu --prefix=/gnu and I get linking errors: /usr/i386-gnu/bin/ld: warning: libc.so.6, needed by /usr/i386-gnu/lib/libutil.so, may conflict with libc.

Bug#75253: marked as done (cross-install: some options are broken)

2000-10-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Oct 2000 01:57:23 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#75253: cross-install: some options are broken has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas