Re: cross compilation problems
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 \
> and I still get problems with /usr/i386-gnu/lib/libutil.so needing libc.so.6
> and errors about symbol redefinitions which come from libc.so.6. So maybe the
> cross compiler is broke? I do not know anything about building a debian
> package to know where to look to fix this.
I may be trying this yet tonight.... But I want to hack on trans/kbd.c
some more before I build again and it's late. Maybe tomorrow.
Hmmm. I checked a few with ldd and they are looking for libc.so.6
which doesn't look good. These libs come with the gcc-i386-gnu package.
I have version 1.7-4 of this package installed - and it looks broken.
It worked last time I built gnumach, but maybe it doesn't need any of
the broken libs. If I cannot build either, I'll report a bug against
gcc-i386-gnu. And I may report one anyway if I can confirm it's really
broken and not just my tired imagination.
> Using the dpkg-builpackage script where would you run that from? A build
>From the top directory (ls debian/rules should see a file if you're in
the right dir). Ummm. If the cross-compiler really is broken, don't
get your hopes up. I'd expect it to try linking the same broken libs.
> BTW, under Mach the first com port is /dev/com0 right?
AFAIK, yes. Also, MAKEDEV knows com[0-9] so this looks right.
BTW, these troubles only seem to come from cross-compiling. I've done
a number of native builds without problem. If that works for you,
there's a way to go....
Steve Bowman <firstname.lastname@example.org> (preferred)
Buckeye, AZ <email@example.com> <firstname.lastname@example.org>
Powered by Debian GNU/Linux and GNU/Hurd <http://www.debian.org>