[Bug 690952] New: Failure of wxWidgets based application builds with obs or osc/build
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c0 Summary: Failure of wxWidgets based application builds with obs or osc/build Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: neil@darlow.co.uk QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=427371) --> (http://bugzilla.novell.com/attachment.cgi?id=427371) ldd output for /usr/lib/libwxsmith.so.0.0.1 from devel:tools:ide codeblocks download User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 I have observed a problem with codeblocks (a wxWidgets based IDE) failing to load some of its plugins (libraries) at startup, on the i586 platform, when built on the obs or locally with osc/build. The problem is not observed when the application is built locally using rpmbuild. The package in question is codeblocks-7114-1.2.src.rpm built using wxWidgets-wxcontainer-devel-2.8.11-3.9.1.i586. The build of codeblocks produces 3 plugins which fail to load at startup for packages downloaded from OBS (devel:tools:ide for openSUSE-11.4) or built locally from the .src.rpm using osc and build. The failing plugins are: /usr/lib/libwxsmithlib.so.0.0.1 /usr/lib/codeblocks/plugins/libwxSmithAui.so /usr/lib/codeblocks/plugins/libwxsmithcontribitems.so Comparing the ldd output for /usr/lib/libwxsmith.so.0.0.1 for the obs download and for a local rpmbuild operation indicates a difference in the dependent wxWidgets libraries (the other two libraries show the same differences). The packages which fail to load the 3 plugins at startup are missing dependencies for: libwx_gtk2u_qa-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_richtext-2_8-0-wxcontainer-2.8.11-3.9.1.i586 This problem does not seem to affect the x86_64 platform. Attached are ldd outputs for /usr/lib/libwxsmith.so.0.0.1 from the OBS project download (which fails) and a local rpmbuild (which is ok). My wxWidgets packages are: wxWidgets-wxcontainer-devel-2.8.11-3.9.1.i586 wxWidgets-lang-2.8.11-4.5.1.noarch libwx_gtk2u_adv-2_8-0-stl-2.8.11-4.5.1.i586 libwx_gtk2u_adv-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_aui-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_core-2_8-0-stl-2.8.11-4.5.1.i586 libwx_gtk2u_core-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_fl-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_gizmos-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_gizmos_xrc-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_gl-2_8-0-stl-2.8.11-4.5.1.i586 libwx_gtk2u_gl-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_html-2_8-0-stl-2.8.11-4.5.1.i586 libwx_gtk2u_html-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_media-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_mmedia-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_ogl-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_plot-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_qa-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_richtext-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_stc-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_svg-2_8-0-wxcontainer-2.8.11-3.9.1.i586 libwx_gtk2u_xrc-2_8-0-stl-2.8.11-4.5.1.i586 libwx_gtk2u_xrc-2_8-0-wxcontainer-2.8.11-3.9.1.i586 The -stl packages are required for pgAdmin3, I develop using the -wxcontainer variant. I have checked that my local osc/build installs the required qa and richtext packages and that codeblocks-contrib (the package owning the 3 plugins) requires those same packages. These conditions are indeed met but there seems to be a problem with OBS and osc/build created packages that does not occur for those created with rpmbuild. Reproducible: Always Steps to Reproduce: 1. Download codeblocks packages from OBS or build locally with osc/build 2. Execute codeblocks Actual Results: For x86_64 platform, and rpmbuild created packages, execution proceeds correctly. For i586 plaform packages from OBS or built with osc/build a warning is issued that 3 plugins have failed to load. Expected Results: Execution should be identical regardless of how the packages are built. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c1 --- Comment #1 from Neil Darlow <neil@darlow.co.uk> 2011-04-29 19:32:34 UTC --- Created an attachment (id=427372) --> (http://bugzilla.novell.com/attachment.cgi?id=427372) ldd output for /usr/lib/libwxsmith.so.0.0.1 from local osc/build of codeblocks-7114-1.2.src.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c Neil Darlow <neil@darlow.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #427372|ldd output for |ldd output for description|/usr/lib/libwxsmith.so.0.0. |/usr/lib/libwxsmith.so.0.0. |1 from local osc/build of |1 from local rpmbuild of |codeblocks-7114-1.2.src.rpm |codeblocks-7114-1.2.src.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c Stephan Kleine <bitdealer@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|pth@novell.com |sbrabec@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c2 Philipp Thomas <pth@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pth@novell.com --- Comment #2 from Philipp Thomas <pth@novell.com> 2011-05-02 11:54:32 CEST --- If an OBS build doesn't work but your local does it's a strong hint that the reason is the use of --as-needed as link option in OBS. With this option, the dynamic libraries are only linked in if the linker sees a need for them. So library names *must* be passed in strict use order, i.e. a library containing symbols must come after the one that needs it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c3 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED CC| |cmorve69@yahoo.es, | |pelliott@blackpatchpanel.co | |m --- Comment #3 from Stanislav Brabec <sbrabec@novell.com> 2011-05-02 17:22:27 CEST --- Philipp, many thanks for the hint. It seems that some libraries in wxWidgets are linked incorrectly, as this problem was reported for another application: http://lists.opensuse.org/opensuse-packaging/2011-02/msg00241.html The thread also describes a fast work-around. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c4 --- Comment #4 from Stanislav Brabec <sbrabec@novell.com> 2011-05-12 14:06:53 CEST --- I just analyzed the failure in deep, and it seems not to be related to the order of linking and not with as-needed, at least not directly. While building with osc, some modules link with wxWidgets libraries, but don't use the -rpath. As a consequence, the resulting module cannot find wxWidgets libraries. Now I have to check, why it is happening. All variables seems to be set properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c5 --- Comment #5 from Neil Darlow <neil@darlow.co.uk> 2011-05-12 14:06:18 UTC --- Perhaps I should also mention that the x86_64 packages for codeblocks downloaded from OBS do not exhibit the problem. I do not know if that is significant but it certainly is interesting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c6 --- Comment #6 from Stanislav Brabec <sbrabec@novell.com> 2011-05-13 14:53:49 CEST --- On my machine, even x86_64 packages exhibit the problem and three modules fail to load. I found an apparent linking definition bug in the codeblocks code: Libraries in src/plugins/contrib/wxSmith/wxwidgets apparently use wxWidgets, but they don't define dependency on wxWidgets. They include reference to src/sdk/libcodeblocks.la which link to wxWidgets. As the consequence, references to wxWidgets are evaluate correctly (it links even with a strict -no-undefined linking policy), but the linking infrastructure (libtool & co.) don't pass the required -rpath. As a consequence, these libraries are not able to find wxWidgets libraries. Here is my theory, why it exhibits problem only with -as-needed: The whole application probably links with all wxWidgets libraries without -as-needed. The library module inherits references to wxWidgets from the application. With -as-needed this does not happen. I have to check, whether it is only a bug of codeblocks (which is apparent), wxWidgets (extra option needed for -rpath inheritance?) or even libtool. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c7 --- Comment #7 from Stanislav Brabec <sbrabec@novell.com> 2011-05-13 18:20:10 CEST --- I guess that I have a simple reproducer. It looks eithwe like a disability of libtool or improper use of it. It is reproducible even with -as-needed. Link one library setting linker RPATH. Use library to build a binary. Even if the binary does not use wxWidgets directly, linker option is lost and binary is broken. codeblocks does something even more complicated: Link one library setting linker RPATH. Use library to build another library. Use this library as a module in a binary. This is broken as well. ------ empty-link.sh ----------------------- #!/bin/sh libtool --tag=CC --mode=compile gcc -shared emptylib.c -c -o emptylib.lo libtool --tag=CC --mode=link gcc -shared -rpath /usr/lib64 -Wl,-rpath,/usr/lib64/wx-2.8-wxcontainer -L/usr/lib64/wx-2.8-wxcontainer -lwx_gtk2u_aui-2.8 emptylib.lo -o libempty.la ldd .libs/libempty.so echo "You see it is OK." #libtool --tag=CC --mode=link gcc -shared -rpath /usr/lib64 libempty.la -o libempty2.la #ldd .libs/libempty2.so #echo "You see it look suspicious." #libtool --tag=CC --mode=compile gcc empty.c -c -o empty.o libtool --tag=CC --mode=link gcc empty.o libempty.la -o empty #libtool --tag=CC --mode=link gcc empty.o libempty2.la -o empty ldd empty LD_LIBRARY_PATH=$PWD/.libs ldd .libs/empty echo "And you see it is appparently broken." /empty ------ emptylib.c ----------------------- int nothing(void) { return 0; } ------ empty.c ----------------------- int main() { return 0; } ----------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c8 --- Comment #8 from Stanislav Brabec <sbrabec@novell.com> 2011-05-16 21:52:08 CEST --- I finally see, where is the problem and how to fix: Affected third party packages use libtool to link libraries. libtool has its own heuristic, which decides, whether -Wl,-rpath should be included. The libtool heuristic fails here. This heuristic uses .la files. But wxWidgets libraries are not linked by libtool, and no .la files exist there. wx-config explicitly provides -Wl,-rpath. It is used by the libraries directly linked against wxWidgets (and this linking succeeds), but their .la file does not store -Wl,-rpath. Second level libraries or binaries that link against these first level libraries are linked with wxWidgets again (however it makes no sense in a modern GNU-Linux system, it is a standard libtool behavior), but as the .la file does not contain -Wl,-rpath information, the inherited -Wl,-rpath are not added to LDFLAGS. Linking succeeds, but runtime is not able to find libraries. I see two possible fixes: 1. Fast and easy: Create syntethic .la files for wxWidgets libraries to work-around linking problem. 2. Complex: Learn libtool to be smarter if .la file does not exist. Here are reproducers: ------ empty-link-with-la.sh ----------------------- #!/bin/sh libtool --tag=CC --mode=compile gcc -shared emptylib.c -c -o emptylib.lo # -Wl,-rpath,/usr/lib64/wx-2.8-wxcontainer -L/usr/lib64/wx-2.8-wxcontainer libtool --tag=CC --mode=link gcc -shared -rpath $PWD/empty_install emptylib.lo -o libempty.la mkdir -p $PWD/empty_install libtool --mode=install install -c libempty.la $PWD/empty_install ldd empty_install/libempty.so echo "You see it is OK." # emulate different directory rm -rf .libs libempty.la libtool --tag=CC --mode=link gcc -shared -rpath /usr/lib64 /home/sbrabec/empty_install/libempty.la -o libempty2.la ldd .libs/libempty2.so echo "Yes, it is OK." libtool --tag=CC --mode=compile gcc empty.c -c -o empty.o libtool --tag=CC --mode=link gcc empty.o libempty2.la -o empty LD_LIBRARY_PATH=$PWD/.libs ldd .libs/empty echo "Yes, it is OK as well." /empty ------ empty-link-no-la.sh ----------------------- #!/bin/sh libtool --tag=CC --mode=compile gcc -shared emptylib.c -c -o emptylib.lo # -Wl,-rpath,/usr/lib64/wx-2.8-wxcontainer -L/usr/lib64/wx-2.8-wxcontainer libtool --tag=CC --mode=link gcc -shared -rpath $PWD/empty_install emptylib.lo -o libempty.la mkdir -p $PWD/empty_install libtool --mode=install install -c libempty.la $PWD/empty_install ldd empty_install/libempty.so echo "You see it is OK." # emulate different directory rm -rf .libs libempty.la libtool --tag=CC --mode=compile gcc -shared emptylib.c -c -o emptylib.lo # emulate SUSE Shared Library Policy rm empty_install/libempty.la libtool --tag=CC --mode=link gcc -shared -rpath /usr/lib64 -Wl,-rpath -Wl,$PWD/empty_install emptylib.lo -L$PWD/empty_install -lempty -o libempty2.la LD_LIBRARY_PATH=$PWD/.libs ldd .libs/libempty2.so echo "This is still OK." libtool --tag=CC --mode=compile gcc empty.c -c -o empty.o libtool --tag=CC --mode=link gcc empty.o libempty2.la -o empty LD_LIBRARY_PATH=$PWD/.libs ldd .libs/empty echo "OOPS, this fails." LD_LIBRARY_PATH=$PWD/.libs ./empty ----------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c9 --- Comment #9 from Neil Darlow <neil@darlow.co.uk> 2011-05-16 20:41:56 UTC --- Perhaps it will assist in choosing the best solution by knowing the following facts regarding codeblocks build: 1) The codeblocks project prefers the use of a monolithic wxWidgets library for building codeblocks. Use of a modularized wxWidgets is not well supported. 2) The codeblocks project provides the GNU Makefile build mechanism as a secondary means of building codeblocks. Their preferred method is to use codeblocks to (re)build itself. These two preferences (should I say restrictions?) don't seem to fit well with packaging methods for a typical GNU/Linux distribution. From my previous experience with fixing bugs in the GNU Makefile build mechanism, I don't think we will have much success in persuading the codeblocks project to make major changes to that build mechanism - unless we can persuade them it is severely broken. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c10 --- Comment #10 from Stanislav Brabec <sbrabec@novell.com> 2011-05-18 18:05:06 CEST --- I just confirmed that adding of synthetic .la files helps and codeblocks linked with such wxWidgets build correctly. You can test them here: OBS link: https://build.opensuse.org/package/show?package=codeblocks&project=home%3Asbrabec%3Abranches%3Adevel%3Atools%3Aide Binaries: http://download.opensuse.org/repositories/home:/sbrabec:/branches:/devel:/to... fixed wxWidgets (you don't need them to run codeblocks, just to compile them): OBS link: https://build.opensuse.org/project/packages?project=home%3Asbrabec%3Abranche... Binaries: http://download.opensuse.org/repositories/home:/sbrabec:/branches:/X11:/wxWi... To Neil Darlow (comment 9): 1) As long as codeblocks uses wx-config (and it uses), it should be always OK. 2) Bootstrapping will always need Makefile-based build. In fact, codeblock just correctly uses libtool (well, not completely correctly, see comment 6). But the libtool does incorrect thing - it passes wxWidgets libraries to the third level libraries/binaries linker but does not inherits linking flags needed to link against xWidgets libraries. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c11 --- Comment #11 from Stanislav Brabec <sbrabec@novell.com> 2011-05-18 18:16:21 CEST --- Regarding maitreya project and its already fixed failure, it seems to be a different problem, that was unrelated to this one. maitreya was not able to find wxWidgets symbols during compilation, codeblocks were not able to find libraries in the runtime. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c12 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #12 from Stanislav Brabec <sbrabec@novell.com> 2011-05-19 17:12:41 CEST --- Synthetic .la files seems to work-around libtool linking problem. Requesting another online update of wxWidgets. I just verified, that no package in openSUSE:11.4 is affected, so again - only development packages of wxWidgets needs to be upgraded. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c13 --- Comment #13 from Marcus Meissner <meissner@novell.com> 2011-05-20 08:34:29 UTC --- okay... +1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c14 --- Comment #14 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-05-20 18:00:09 CEST --- This is an autogenerated message for OBS integration: This bug (690952) was mentioned in https://build.opensuse.org/request/show/70836 Factory / wxWidgets -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c15 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:41091:low --- Comment #15 from Swamp Workflow Management <swamp@suse.com> 2011-05-23 14:16:19 UTC --- The SWAMPID for this issue is 41091. This issue was rated as low. Please submit fixed packages until 2011-06-20. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/41091 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c16 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |cdengler@novell.com InfoProvider|maintenance@opensuse.org | --- Comment #16 from Christian Dengler <cdengler@novell.com> 2011-05-23 14:16:30 UTC --- okay +1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c17 --- Comment #17 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-05-23 18:00:16 CEST --- This is an autogenerated message for OBS integration: This bug (690952) was mentioned in https://build.opensuse.org/request/show/71066 11.4 / wxWidgets -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c18 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41091:low |maint:running:41091:low | |maint:released:11.4:41102 --- Comment #18 from Swamp Workflow Management <swamp@suse.com> 2011-05-31 13:37:54 UTC --- Update released for: libwx_base-2_8-0-compat-lib-wxcontainer, libwx_base-2_8-0-wxcontainer, libwx_base-2_8-0-wxcontainer-debuginfo, libwx_base_net-2_8-0-compat-lib-wxcontainer, libwx_base_net-2_8-0-wxcontainer, libwx_base_net-2_8-0-wxcontainer-debuginfo, libwx_base_xml-2_8-0-compat-lib-wxcontainer, libwx_base_xml-2_8-0-wxcontainer, libwx_base_xml-2_8-0-wxcontainer-debuginfo, libwx_baseu-2_8-0-compat-lib-stl, libwx_baseu-2_8-0-compat-lib-wxcontainer, libwx_baseu-2_8-0-stl, libwx_baseu-2_8-0-stl-debuginfo, libwx_baseu-2_8-0-wxcontainer, libwx_baseu-2_8-0-wxcontainer-debuginfo, libwx_baseu_net-2_8-0-compat-lib-stl, libwx_baseu_net-2_8-0-compat-lib-wxcontainer, libwx_baseu_net-2_8-0-stl, libwx_baseu_net-2_8-0-stl-debuginfo, libwx_baseu_net-2_8-0-wxcontainer, libwx_baseu_net-2_8-0-wxcontainer-debuginfo, libwx_baseu_xml-2_8-0-compat-lib-stl, libwx_baseu_xml-2_8-0-compat-lib-wxcontainer, libwx_baseu_xml-2_8-0-stl, libwx_baseu_xml-2_8-0-stl-debuginfo, libwx_baseu_xml-2_8-0-wxcontainer, libwx_baseu_xml-2_8-0-wxcontainer-debuginfo, libwx_gtk2_adv-2_8-0-compat-lib-wxcontainer, libwx_gtk2_adv-2_8-0-wxcontainer, libwx_gtk2_adv-2_8-0-wxcontainer-debuginfo, libwx_gtk2_aui-2_8-0-compat-lib-wxcontainer, libwx_gtk2_aui-2_8-0-wxcontainer, libwx_gtk2_aui-2_8-0-wxcontainer-debuginfo, libwx_gtk2_core-2_8-0-compat-lib-wxcontainer, libwx_gtk2_core-2_8-0-wxcontainer, libwx_gtk2_core-2_8-0-wxcontainer-debuginfo, libwx_gtk2_fl-2_8-0-compat-lib-wxcontainer, libwx_gtk2_fl-2_8-0-wxcontainer, libwx_gtk2_fl-2_8-0-wxcontainer-debuginfo, libwx_gtk2_gizmos-2_8-0-compat-lib-wxcontainer, libwx_gtk2_gizmos-2_8-0-wxcontainer, libwx_gtk2_gizmos-2_8-0-wxcontainer-debuginfo, libwx_gtk2_gizmos_xrc-2_8-0-compat-lib-wxcontainer, libwx_gtk2_gizmos_xrc-2_8-0-wxcontainer, libwx_gtk2_gizmos_xrc-2_8-0-wxcontainer-debuginfo, libwx_gtk2_gl-2_8-0-compat-lib-wxcontainer, libwx_gtk2_gl-2_8-0-wxcontainer, libwx_gtk2_gl-2_8-0-wxcontainer-debuginfo, libwx_gtk2_html-2_8-0-compat-lib-wxcontainer, libwx_gtk2_html-2_8-0-wxcontainer, libwx_gtk2_html-2_8-0-wxcontainer-debuginfo, libwx_gtk2_media-2_8-0-compat-lib-wxcontainer, libwx_gtk2_media-2_8-0-wxcontainer, libwx_gtk2_media-2_8-0-wxcontainer-debuginfo, libwx_gtk2_mmedia-2_8-0-compat-lib-wxcontainer, libwx_gtk2_mmedia-2_8-0-wxcontainer, libwx_gtk2_mmedia-2_8-0-wxcontainer-debuginfo, libwx_gtk2_ogl-2_8-0-compat-lib-wxcontainer, libwx_gtk2_ogl-2_8-0-wxcontainer, libwx_gtk2_ogl-2_8-0-wxcontainer-debuginfo, libwx_gtk2_plot-2_8-0-compat-lib-wxcontainer, libwx_gtk2_plot-2_8-0-wxcontainer, libwx_gtk2_plot-2_8-0-wxcontainer-debuginfo, libwx_gtk2_qa-2_8-0-compat-lib-wxcontainer, libwx_gtk2_qa-2_8-0-wxcontainer, libwx_gtk2_qa-2_8-0-wxcontainer-debuginfo, libwx_gtk2_richtext-2_8-0-compat-lib-wxcontainer, libwx_gtk2_richtext-2_8-0-wxcontainer, libwx_gtk2_richtext-2_8-0-wxcontainer-debuginfo, libwx_gtk2_stc-2_8-0-compat-lib-wxcontainer, libwx_gtk2_stc-2_8-0-wxcontainer, libwx_gtk2_stc-2_8-0-wxcontainer-debuginfo, libwx_gtk2_svg-2_8-0-compat-lib-wxcontainer, libwx_gtk2_svg-2_8-0-wxcontainer, libwx_gtk2_svg-2_8-0-wxcontainer-debuginfo, libwx_gtk2_xrc-2_8-0-compat-lib-wxcontainer, libwx_gtk2_xrc-2_8-0-wxcontainer, libwx_gtk2_xrc-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_adv-2_8-0-compat-lib-stl, libwx_gtk2u_adv-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_adv-2_8-0-stl, libwx_gtk2u_adv-2_8-0-stl-debuginfo, libwx_gtk2u_adv-2_8-0-wxcontainer, libwx_gtk2u_adv-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_aui-2_8-0-compat-lib-stl, libwx_gtk2u_aui-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_aui-2_8-0-stl, libwx_gtk2u_aui-2_8-0-stl-debuginfo, libwx_gtk2u_aui-2_8-0-wxcontainer, libwx_gtk2u_aui-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_core-2_8-0-compat-lib-stl, libwx_gtk2u_core-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_core-2_8-0-stl, libwx_gtk2u_core-2_8-0-stl-debuginfo, libwx_gtk2u_core-2_8-0-wxcontainer, libwx_gtk2u_core-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_fl-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_fl-2_8-0-wxcontainer, libwx_gtk2u_fl-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_gizmos-2_8-0-compat-lib-stl, libwx_gtk2u_gizmos-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_gizmos-2_8-0-stl, libwx_gtk2u_gizmos-2_8-0-stl-debuginfo, libwx_gtk2u_gizmos-2_8-0-wxcontainer, libwx_gtk2u_gizmos-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_gizmos_xrc-2_8-0-compat-lib-stl, libwx_gtk2u_gizmos_xrc-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_gizmos_xrc-2_8-0-stl, libwx_gtk2u_gizmos_xrc-2_8-0-stl-debuginfo, libwx_gtk2u_gizmos_xrc-2_8-0-wxcontainer, libwx_gtk2u_gizmos_xrc-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_gl-2_8-0-compat-lib-stl, libwx_gtk2u_gl-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_gl-2_8-0-stl, libwx_gtk2u_gl-2_8-0-stl-debuginfo, libwx_gtk2u_gl-2_8-0-wxcontainer, libwx_gtk2u_gl-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_html-2_8-0-compat-lib-stl, libwx_gtk2u_html-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_html-2_8-0-stl, libwx_gtk2u_html-2_8-0-stl-debuginfo, libwx_gtk2u_html-2_8-0-wxcontainer, libwx_gtk2u_html-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_media-2_8-0-compat-lib-stl, libwx_gtk2u_media-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_media-2_8-0-stl, libwx_gtk2u_media-2_8-0-stl-debuginfo, libwx_gtk2u_media-2_8-0-wxcontainer, libwx_gtk2u_media-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_mmedia-2_8-0-compat-lib-stl, libwx_gtk2u_mmedia-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_mmedia-2_8-0-stl, libwx_gtk2u_mmedia-2_8-0-stl-debuginfo, libwx_gtk2u_mmedia-2_8-0-wxcontainer, libwx_gtk2u_mmedia-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_ogl-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_ogl-2_8-0-wxcontainer, libwx_gtk2u_ogl-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_plot-2_8-0-compat-lib-stl, libwx_gtk2u_plot-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_plot-2_8-0-stl, libwx_gtk2u_plot-2_8-0-stl-debuginfo, libwx_gtk2u_plot-2_8-0-wxcontainer, libwx_gtk2u_plot-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_qa-2_8-0-compat-lib-stl, libwx_gtk2u_qa-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_qa-2_8-0-stl, libwx_gtk2u_qa-2_8-0-stl-debuginfo, libwx_gtk2u_qa-2_8-0-wxcontainer, libwx_gtk2u_qa-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_richtext-2_8-0-compat-lib-stl, libwx_gtk2u_richtext-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_richtext-2_8-0-stl, libwx_gtk2u_richtext-2_8-0-stl-debuginfo, libwx_gtk2u_richtext-2_8-0-wxcontainer, libwx_gtk2u_richtext-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_stc-2_8-0-compat-lib-stl, libwx_gtk2u_stc-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_stc-2_8-0-stl, libwx_gtk2u_stc-2_8-0-stl-debuginfo, libwx_gtk2u_stc-2_8-0-wxcontainer, libwx_gtk2u_stc-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_svg-2_8-0-compat-lib-stl, libwx_gtk2u_svg-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_svg-2_8-0-stl, libwx_gtk2u_svg-2_8-0-stl-debuginfo, libwx_gtk2u_svg-2_8-0-wxcontainer, libwx_gtk2u_svg-2_8-0-wxcontainer-debuginfo, libwx_gtk2u_xrc-2_8-0-compat-lib-stl, libwx_gtk2u_xrc-2_8-0-compat-lib-wxcontainer, libwx_gtk2u_xrc-2_8-0-stl, libwx_gtk2u_xrc-2_8-0-stl-debuginfo, libwx_gtk2u_xrc-2_8-0-wxcontainer, libwx_gtk2u_xrc-2_8-0-wxcontainer-debuginfo, wxWidgets, wxWidgets-ansi, wxWidgets-ansi-compat-lib-config, wxWidgets-ansi-debugsource, wxWidgets-ansi-devel, wxWidgets-ansi-devel-debuginfo, wxWidgets-ansi-plugin-sound_sdl-2_8-wxcontainer, wxWidgets-ansi-plugin-sound_sdl-2_8-wxcontainer-debuginfo, wxWidgets-compat-lib-config, wxWidgets-debugsource, wxWidgets-devel, wxWidgets-devel-debuginfo, wxWidgets-lang, wxWidgets-plugin-sound_sdlu-2_8-stl, wxWidgets-plugin-sound_sdlu-2_8-stl-debuginfo, wxWidgets-wxcontainer, wxWidgets-wxcontainer-compat-lib-config, wxWidgets-wxcontainer-debugsource, wxWidgets-wxcontainer-devel, wxWidgets-wxcontainer-devel-debuginfo, wxWidgets-wxcontainer-plugin-sound_sdlu-2_8-wxcontainer, wxWidgets-wxcontainer-plugin-sound_sdlu-2_8-wxcontainer-debuginfo Products: openSUSE 11.4 (debug, i586, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41091:low |. |maint:released:11.4:41102 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c19 --- Comment #19 from Neil Darlow <neil@darlow.co.uk> 2011-05-31 16:34:20 UTC --- Many thanks to Stanislav Brabec for the amount of effort he put into identifying the cause of, and fixing, this bug. It is efforts like this that make openSUSE/SuSE the outstanding distribution that it is! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=690952 https://bugzilla.novell.com/show_bug.cgi?id=690952#c20 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #20 from Stanislav Brabec <sbrabec@novell.com> 2011-06-01 17:08:29 CEST --- Well, the note in http://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Best_Practic... says: Avoid packaging libtool config files (.la files). In general they are not needed if you do not package a static library and put the .so file in a system directory (i.e. %_lib, /usr/%_lib). If your shared library resides — for whatever reason — in, for example, /opt/package/lib/libfoo.so.7, you do need the libfoo.la file, or further programs using libtool to link against libfoo.so.7 will be lacking the correct path. However it took a lot of time to detect what is happening. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com