minutes of ESC call ...

[Stephan Bergmann]

On 02/09/2012 06:54 PM, Michael Meeks wrote:
> * system stdlibs for Linux universal builds ? (Stephan/Petr)
> 	+ https://bugs.freedesktop.org/show_bug.cgi?id=45696
> 	+ https://bugs.freedesktop.org/show_bug.cgi?id=45074
> 	+ problem is - that for generic RPMs/DEBs
> 		+ we include the gcc / C++ std-libraries
> 		+ in theory machines could not already have them
> 	+ 2x problems:
> 		+ extensions linked to newer C++ stdlib we ship
> 		  could fail to run
> 		+ old lib. that we ship, can give C++ exception
> 		  handling issues, that newer ones would not
> 		  expose.
> 	+ suggest
> 		+ no longer package it anymore on Linux (Stephan)
> 	+ can we add a Requires: line that works cross-distro ?
> 		+ probably not.
> 	+ we currently have very incomplete Requires anyway (mst)
> 	+ the lib has versioned symbols, so if installed on
> 	  an older system, we may fail on start (Fridrich)
> 	+ create a new separate package of just this stdlib, that
> 	  conflicts with the system (Fridrich)
> 	+ we build custom gcc&  binutils on our legacy systems (Fridrich)
> 	+ the very newest libraries would be another option,
> 	  for a while.
> 	+ Options:
> 		+ create new compat-stdlib package and refuse
> 		  to install if there are newer stdlib around (Fridrich)
> AA:		+ disable bundling of C++ stdlib in 3.5.1&  see
> 		  how it goes (Petr)
> 	+ re-think if lots of people complain.

Fridrich, saw your problems on IRC only after you'd left.  What should 
hopefully work is to put the two libs from the new compiler into some 
directory and let LD_LIBRARY_PATH point to it.  Ideally, all parts of 
the configure/build process should honour pre-existing LD_LIBRARY_PATH 
properly.

Stephan