I haven't booted my clfs install as unfortunately I did it on an a
partition managed by LVM - I have to wait to get a new HD to create a
non LVM partition (I do want to figure out how to do clfs with full LVM
support - but I think keeping things simple initially is better) but I
am using the CLFS partition via chroot to script the building of some of
the utilities I know I'll need so that once I redo clfs (which I
scripted and verified the scripts work) I can fairly quickly get the
utilities I need working.
One of them is openssl - but reading the instructions at
http://cblfs.cross-lfs.org/index.php/OpenSSL
I have a question.
Since openssl does install a binary into /usr/bin - should the 32-bit
and 64-bit binaries be renamed and the multiarch wrapper used?
Looking at my CentOS 5.2 system, it seems that both packages (32 and 64)
have ownership of /usr/bin/openssl - but ldd on the binary reveals it is
the 64-bit binary, I'm guessing with multilib packages in RHEL/CentOS
that both own the same file in /usr/bin that the 64-bit version is the
only one actually available, but I'm not positive how they handle it.
Anyway, should I rename the 32-bit binary before installing 64-bit
version and use the wrapper, or is it OK for the 64-bit to overwrite the
32-bit version?
_______________________________________________
Clfs-support mailing list
Clfs-support@lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
