Re: Bug#24334: libc4 missing in hamm
On Fri, Jul 10, 1998 at 12:15:10PM -0400, Raul Miller wrote:
> Hamish Moffatt <hamish@debian.org> wrote:
> > The binary package from bo should just be fine. I just used apt
> > on my bo system to install it, so I can test aout-gcc.
>
> That's not the issue. Can you take it apart with ar?
$ ls libc4*
libc4_4.6.27-15.deb
$ file libc4*
libc4_4.6.27-15.deb: current ar archive
$ cp libc4* ~
$ cd
$ ar x libc4_4.6.27-15.deb
$ ls -l
total 481
drwx------ 2 hamish Debian 1024 Aug 24 1997 Mail
-rw-r--r-- 1 hamish Debian 503 Jul 10 20:59 control.tar.gz
-rw-r--r-- 1 hamish Debian 242249 Jul 10 20:59 data.tar.gz
-rw-r--r-- 1 hamish Debian 4 Jul 10 20:59 debian-binary
-rw-rw-r-- 1 hamish Debian 242946 Jul 10 20:59 libc4_4.6.27-15.deb
drwxrwxr-x 3 hamish Debian 1024 Mar 18 02:53 tmp
It doesn't build on bo for the same reason it won't on hamm;
when it goes to build the shared libraries,
make[2]: Entering directory `/local/home/hamish/tmp/libc4-4.6.27/jump/libm'
(cd ../..; for l in *.a; do \
/usr/i486-linuxaout/bin/ar -d $l __.SYMDEF; \
/usr/i486-linuxaout/bin/ranlib $l; done)
(cd ../../shared; for l in *.a; do \
/usr/i486-linuxaout/bin/ar -d $l __.SYMDEF; \
/usr/i486-linuxaout/bin/ranlib $l; done)
/usr/bin/mkimage -l libm -v 4.6.27 -a 0x600e0000 \
-d 0x600f8000 -j 0x00000800 -g 0x00000100 \
-- ../../shared/libm.a ../../shared/libgcc/libgcc3.a ../libc/libc.sa ../
../libmalias.a
system: No such file or directory
/usr/bin/mkimage: error running '/usr/i486-linuxaout/bin/ld -x -Ttext 600df000 -
Tdata 600f7000 -o libm.so.4.6.27 ../../jump/libm/__jump.o ../../shared/libm.a ..
/../shared/libgcc/libgcc3.a ../libc/libc.sa ../../libmalias.a'
Hamish
--
Hamish Moffatt, hamish@debian.org, hamish@rising.com.au, hmoffatt@mail.com
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: