Multiarch in Linux? was Re (2): libc.so.6

[peter at easthope.ca]

From:	James Cameron <quozl at laptop.org>
Date:	Mon, 10 Nov 2014 13:20:20 +1100
> ... libc.so.6 is a symbolic link, not a file.

Thanks.

> But on 13.2.1 it might instead look in:
> 
>     /usr/lib/

OK!  An expedient solution is now the last or near last
submission here. 
http://www.ocp.inf.ethz.ch/forum/index.php/topic,918.0.html
Essentially, "sudo ln -s /lib /lib/i386-linux-gnu".

The body of /usr/aos/source/Linux.I386.Unix.Mod has 
	libraryPaths[0] := "/lib/i386-linux-gnu";
	libraryPaths[1] := "/usr/lib/i386-linux-gnu";
These paths are mentioned here, 
https://wiki.ubuntu.com/MultiarchSpec#Filesystem_layout

but not in any of these.
http://www.linuxbase.org/betaspecs/fhs/fhs.html
https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html
http://www.gnu.org/software/gnustep/resources/documentation/User/GNUstep/filesystem.html

*/lib/i386* appears to be an emerging multiarch thing.

> Meanwhile, get it packaged for Fedora to alleviate future pain?

Adoption of multiarch in Fedora seems possible.  If that 
happens, the i386-linux-gnu paths are likely to appear in the stock 
file system.  In the interim, the installation procedure for UnixAos is 
straightforward,
 http://www.informatik.uni-bremen.de/~fld/UnixAos/Readme.txt
and "sudo ln -s /lib /lib/i386-linux-gnu" is just one extra step.  

Also UnixAos is a moving target.  A package for Fedora or Debian would 
need an update several times in a year.  Unless there is a very strong justification, 
I'm reluctant to extend my "unfinished projects" list.

Regards,                        ... Peter E.

-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca