[opensuse-packaging] Fixing --as-needed packages (was [opensuse-factory] status distribution)
![](https://seccdn.libravatar.org/avatar/0006bf0ff51653f0a31c4a5ae55d3b0d.jpg?s=120&d=mm&r=g)
coolo published a list of packages that fail to build with --as-needed at http://www.suse.de/~coolo/asneeded/ (see Factory ML for details), so I continue this in opensuse-packaging ML so people can say in which packages they are working and so... I take care of alsa-tools (fltk is the problematic package), ami and DirectFB. 2009/6/17 Cristian Rodríguez <crrodriguez@opensuse.org>:
While I certainly cannot promise fix all the broken packages, please tell people to email me or this list if they have doubts about fixing this problems, this issue has to be sorted out.
Fixing fltk I also saw "fltk_gl" isn't linked against GL, so since I'm with it... it this a bug? The ld man says: "The reason that --allow-shlib-undefined is the default is that the shared library being specified at link time may not be the same as the one that is available at load time, so the symbols might actually be resolvable at load time." and the thing is that I don't know too much about openGL, but it's my understanding that there are multiple libraries (with different sonames?) implementing it (nVidia has one, ATI probably other...), I'm correct? If so, is the fltk_gl/openGL a case where it is really correct to allow undefined symbols? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/0006bf0ff51653f0a31c4a5ae55d3b0d.jpg?s=120&d=mm&r=g)
2009/6/17 Cristian Morales Vega <cmorve69@yahoo.es>:
Fixing fltk I also saw "fltk_gl" isn't linked against GL, so since I'm with it... it this a bug? The ld man says: "The reason that --allow-shlib-undefined is the default is that the shared library being specified at link time may not be the same as the one that is available at load time, so the symbols might actually be resolvable at load time." and the thing is that I don't know too much about openGL, but it's my understanding that there are multiple libraries (with different sonames?) implementing it (nVidia has one, ATI probably other...), I'm correct? If so, is the fltk_gl/openGL a case where it is really correct to allow undefined symbols?
After reading a little, and in case someone is interested... OpenGL extensions are searched through a glXGetProcAddress() function available in any libGL. So it's fine to link against libGL, any implementation dependent feature will be usable anyway even if the libGL at link time didn't provide it. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (1)
-
Cristian Morales Vega