Date: Thu, 26 Oct 2000 21:07:55 -0700
From: Steve Bowman <[EMAIL PROTECTED]>
No bug report needed. /usr/i386-gnu/lib is indeed a symlink to /gnu/lib
and ldd under hurd shows:
libc.so.0.2 => /lib/libc.so.0.2 (0x01022000)
for all libraries. ldd under linux just finds t
On Wed, Oct 25, 2000 at 09:30:05AM -0600, Gordon Matzigkeit wrote:
> > Steve Bowman writes:
>
> SB> Hmmm. I checked a few with ldd and they are looking for
> SB> libc.so.6 which doesn't look good. These libs come with the
> SB> gcc-i386-gnu package. I have version 1.7-4 of this package
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 fine to cross-compile the hurd,
I know many who have done it like that.
may be you have some prob
On Thu, Oct 26, 2000 at 03:04:24PM -0500, Daniel E . Baumann wrote:
> > > and I
> > > would like to get the tunnel interface in pfinet (which Marcus commited
> > > to CVS a while ago) so I can get BSD user space PPP working with it.
> > > Although I think I may also have to build GNU Mach to get t
> > and I
> > would like to get the tunnel interface in pfinet (which Marcus commited
> > to CVS a while ago) so I can get BSD user space PPP working with it.
> > Although I think I may also have to build GNU Mach to get the com port fixes
> > there, also.
>
> The latest deb has them, but they ar
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
> Steve Bowman writes:
SB> Hmmm. I checked a few with ldd and they are looking for
SB> libc.so.6 which doesn't look good. These libs come with the
SB> gcc-i386-gnu package. I have version 1.7-4 of this package
SB> installed - and it looks broken.
1.7-3 only installs a symlink from /us
Am Mit, 25 Okt 2000 04:18:26 schrieb 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: l
On Wed, Oct 25, 2000 at 12:37:12AM -0700, Steve Bowman wrote:
> On Wed, Oct 25, 2000 at 01:57:14AM -0500, Daniel E . Baumann wrote:
> > Well I tried this:
> >
> > mkdir build; cd build
> > MIG=i386-gnu-mig CC=i386-gnu-gcc LD=i386-gnu-ld ../configure \
> > --build=i686-pc-linux-gnu --host=i386-pc
On Wed, Oct 25, 2000 at 01:57:14AM -0500, Daniel E . Baumann wrote:
> Well I tried this:
>
> mkdir build; cd build
> MIG=i386-gnu-mig CC=i386-gnu-gcc LD=i386-gnu-ld ../configure \
> --build=i686-pc-linux-gnu --host=i386-pc-gnu --target=i386-pc-gnu \
> --prefix=/gnu
>
> and I still get problems
Well I tried this:
mkdir build; cd build
MIG=i386-gnu-mig CC=i386-gnu-gcc LD=i386-gnu-ld ../configure \
--build=i686-pc-linux-gnu --host=i386-pc-gnu --target=i386-pc-gnu \
--prefix=/gnu
and I still get problems with /usr/i386-gnu/lib/libutil.so needing libc.so.6
and errors about symbol redefin
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
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
> > 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
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,
> 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
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
> > 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
> 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
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
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.
21 matches
Mail list logo
