Cristian Rodríguez wrote:
It doesnt!!, it aborts installation with "libraries are in /usr.." message.
Now extrapolate this to a non trivial C++ program, or even C ones, that use lots of libraries, it implies wasting lots and lots of time, fixing packages to move libraries around, fixing the regressions that get introduced by those changes ..repeat, ad nauseum..
ALl this work has to be done just to cover this corner, stone age use case.
--- Not a stone age case. People still use it today which you should obviously see by the amount of discourse and people SAYING they use it.
Sorry, not seeing the benefit here
--- First you have to have an idea for what makes a good boot design. During the boot, binaries should come from /sbin, /bin and *should* use static linkage, though /lib and /lib64 are also usually on a root disk, so conceivably, boot libs could be there. It's questionable the benefit of using something with as large a memory foot print as C++ at boot time...but that has only been historically true -- but that's why c++ progs are almost always dynamically linked.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org