Links to libc and libm would be useful
|Reported by:||haiqu||Owned by:||bonefish|
When configuring new software using the familiar
./configure; make; make install regimen, special parameters often have to be passed on the commanline to ensure that certain libraries are detected correctly. In the worst case, if a configure script isn't well written, it can fail to find the required libraries.
We have examples of fixes already implemented in Haiku. libnetwork.so is already symlinked to both libbind.so and libsocket.so which are the names expected on most varieties of Unix.
My suggestion is to add the following additional symlinks:
/boot/system/lib/libroot.so -> /boot/system/lib/libm.so /boot/system/lib/libroot.so -> /boot/develop/lib/x86/libm.so /boot/system/lib/libbe.so -> /boot/system/lib/libc.so /boot/system/lib/libbe.so -> /boot/develop/lib/x86/libc.so
This idea came about after I noticed the Python-3.1a2 configure script test for the presence of a function in libc (and fail to find it) and then later on recognise that I had passed an alternative to this name. i.e. the script was doing things in the wrong order. Nasty indeed unless you're watching the output of configure like a hawk as it scrolls by...