Hartmut Koptein <[EMAIL PROTECTED]> writes:
> > I've tried the slink-libc, and it gives me problems with the chown whenever
> > I try to use tar (tried to recompile tar as well).
> >
> > The same thing works fine with both the 980705-snap (which I've built a
> > deb from), and with the redhat gli
> > Native dpkg for powerpc under glibc-2.1 makes trouble! We have a little
> > workaround for this (thanks dan!).
>
> which problem and workaround is this?
The problem ... tja, hmmm ext2 or ar or gzip or
> I've tried the slink-libc, and it gives me problems with the chown whenever
> I t
>
> Make your own tarball. Extract the packages with:
>
> for i in *.deb
> do
> ar -x $i
> tar xfz data.tar.gz
> done
>
> But then you have no dpkg-database.
>
What about preinst, postinst and friends ???
I would give it a try tonight.
Friendly,
Sven LUTHER
--
To UNSUBSCRIBE, email t
> Should it not be possible to run an hamm/slink mixed system. I think
> this
> is the same as the libc5/libc6 situation on i386 an m68k. should the
> hamm
> libc6 not have been libc5 instead ?
You know that libc5 is incompatible to libc6!? Ok, let me explain:
libc6 (2.0.x) is compatible with glib
Hartmut Koptein <[EMAIL PROTECTED]> writes:
> > I tried to install slink iun a separate partition, but dpkg was not
> > happy at all.
>
> Native dpkg for powerpc under glibc-2.1 makes trouble! We have a little
> workaround for this (thanks dan!).
which problem and workaround is this?
> > Am i h
> > i tried to install some debian-ppc/slink packages on an linux/apus
> > system where i had previously an mixed redhat/debian-hamm installed.
>
> Hmmm which libc version do you use? 1.99 ? If so, you can't run slink
> binaries.
Should it not be possible to run an hamm/slink mixed system. I thi
> i tried to install some debian-ppc/slink packages on an linux/apus
> system where i had previously an mixed redhat/debian-hamm installed.
Hmmm which libc version do you use? 1.99 ? If so, you can't run slink
binaries.
> I tried to install slink iun a separate partition, but dpkg was not
> happ
Hello
> Now, this is a problem. You can't use that kernel on PPC because the libc
> was compiled with 2.1.106, as I understand it. You're having a variant of
> the chown()/lchown() war. I'm having another one and I don't seem to be
> able to get rid of it :)
>
What is the exact status on thi
8 matches
Mail list logo
