On 22-04-17 22:28, Douglas R. Reno wrote:
On Sat, Apr 22, 2017 at 2:49 PM, Frans de Boer <[email protected]
<mailto:[email protected]>> wrote:
On 22-04-17 17:54, Bruce Dubbs wrote:
Frans de Boer wrote:
Dear Reader,
The current instance of LFS-dev still requires the use of
/lib64 (as a
link to /lib).
No it does not. /lib64 is a directory, not a symlink. It contains
exactly two files, both symbolic links:
$ ls -l /lib64
total 0
lrwxrwxrwx 1 root root 27 Feb 13 19:28 ld-linux-x86-64.so.2 ->
../lib/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 27 Feb 13 19:28 ld-lsb-x86-64.so.3 ->
../lib/ld-linux-x86-64.so.2
If have made changes to eliminate the use of the /lib64
link. Also, all relevant hard-coded references to /lib64 in
the used
packages are replaced with /lib. The only place I did not
touched sofar,
where the manuals and documentation. Oh, I did this for both
developments
(vinit and systemd).
When we released 8.0 we checked that nothing was installed in
/usr/lib64
or, except for the above, nothing else in /lib64.
You need to explain a little better what you see as the issue.
-- Bruce
Likewise, instead of using /lib I targeted the use of /lib64
without the
use of a symbolic link /lib. That took some more time, but
the part using
only vinit is now ready and booting and more importantly,
working.
Systemd
needs some tweaking, but given available time, that has to
wait a little
longer.
By the way, to do it right, one needs changes in the
toolchain (crucial)
as well in the next stage.
If interested, I can extract all additions and provide them
to be
included
in some future development cycle.
I also sure that some commands can be more integrated and/or
refined, but
that is a next step.
Kind Regards,
Frans.
Ok, my mistake: lib64 contains some links, I found out how to
eliminate the use of lib64 at all.
The case of using lib64 instead of lib required some more work since
many packages use hard-coded references to lib. Since the FHS does
not mandate the use of lib - it's in fact optional if using lib64/32
- I tried to find a way to create a system without the use of lib,
but instead use lib64 or lib32 only. In that way the system is aware
again of its architecture instead of using the antiquated - but
historical grown - lib directory.
No worry, the architectural independent /var/lib is still there.
--- Frans.
Frans,
We need /lib64 for binary compatibility for other distributions. Some of
us need that more than others. As a university student, I especially
need it.
Well, there is still the option to use the lib64 directory is some
binary blob needs that. It is just that you can have a system without
the lib64 directory. After all, LFS and BLFS etc. are created to educate
and make a base system from where you can proceed.
I mean, next thing we know is that there is software which relies on the
debian structure. Would LFS change then too?
I see no reason to forgo the educational focus of LFS just because some
binary software requires another scheme. One is always free to adapt the
system to its own needs. So, if you can't live without the /lib64
directory, then just add it for the sole purpose to accommodate that
binary piece.
--- Frans
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
