Am Samstag, 4. Januar 2014, 12:29:24 schrieb Thanos Baloukas:
> I installed libffi-3.0.13 in chroot using destdir method
> with which I'm not familiar. I did
>
> make DESTDIR=${fakeroot} install
> cd ${fakeroot}
> sudo bash -c "tar cf - . | (cd / ; tar xf - --no-same-owner)"
>
> as the LFS fakeroot hint suggests
> (I added 'sudo bash -c' and --no-same-owner).
> That broke compiler because libffi installed it's libs in
> $DESTDIR/usr/lib64 directory
> and tar replaced the /usr/lib64 symlink with the directory.
> I also tried to do those as root,
> withought sudo and --no-same-owner, but nothing changed.
> I added -h (--dereference) option to tar xf and that fixed the problem.
> Did someone else have that? Will the constant use of -h option to tar
> cause other problems? Is there another - more reliable maybe - way
> to place files on / ?
>
> Thanks
I use in my 'installpkg' script
...
cd / &&
tar $v -xpJ --keep-directory-symlink -f $binname
...
That keep-directory-symlink I previously did not have included and run in the
same problems you describe.
Note that some BLFS instructions in the book needs some tweaks in order to
work proper when installing via DESTDIR. Some packages do not take care about
DESTDIR but uses INSTALL_ROOT or even do not care about DESTDIR at all. I
needed only for 5 of over 400 packages a patch (rcs, unzip, zip, xinetd and
cdparanoia). For some other packages its a valid approach to specify the
destdir in the prefix-argument. That occurse mostly on packages without a
configure script where the install command looks like "make prefix=/usr
install".
Btw, I installed a new LFS system including QT and the full KDE within minutes
using the binaries I created using that DESTDIR approach...
--
Thomas
--
Thomas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
