[opensuse-buildservice] Error building python-keyring for Ubuntu:9.10
I've been trying to build python-keyring for Ubuntu:9.10 for our local deployment of osc 0.123, but I'm getting this error: creating build/temp.linux-x86_64-2.6/keyring/backends gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wall -g -O2 -fPIC -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-keyring-1 -I/usr/include/python2.6 -c keyring/backends/gnome_keyring.c -o build/temp.linux-x86_64-2.6/keyring/backends/gnome_keyring.o In file included from /usr/include/python2.6/Python.h:8, from keyring/backends/gnome_keyring.c:8: /usr/include/python2.6/pyconfig.h:1028:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/limits.h:27, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/limits.h:122, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/limits.h:11, from /usr/lib/glib-2.0/include/glibconfig.h:11, from /usr/include/glib-2.0/glib/gtypes.h:34, from /usr/include/glib-2.0/glib/galloca.h:34, from /usr/include/glib-2.0/glib.h:32, from keyring/backends/gnome_keyring.c:4: /usr/include/features.h:210:1: warning: this is the location of the previous definition gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wall -g -O2 build/temp.linux-x86_64-2.6/keyring/backends/gnome_keyring.o -ldbus-1 -lpthread -lrt -lgnome-keyring -lglib-2.0 -o build/lib.linux-x86_64-2.6/gnome_keyring.so /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/libgnome-keyring.a(gnome-keyring.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/libgnome-keyring.a: could not read symbols: Bad value collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 7. Dezember 2009 21:09:18 schrieb Luke Imhoff: ...
The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform?
Last time I tried it looked to me that the swig on ubuntu was broken (but the error was different). But I did not look deeper. byer adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Looks like my build-root was just messed up, the .so.* files from libgnome-keyring0 weren't installed even though libgnome-keyring0 was, so gcc was seeing a dead libgnome-keyring.so link and so using the .a On Tue, 2009-12-08 at 00:44 -0600, Adrian Schröter wrote:
Am Montag, 7. Dezember 2009 21:09:18 schrieb Luke Imhoff: ...
The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform?
Last time I tried it looked to me that the swig on ubuntu was broken (but the error was different). But I did not look deeper.
byer adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
The KDE backend assumes that KDE is built against QT 4, but Ubuntu is using KDE against QT3 still. Any chance someone more familiar with QT could add support for QT3? On Tue, 2009-12-08 at 00:44 -0600, Adrian Schröter wrote:
Am Montag, 7. Dezember 2009 21:09:18 schrieb Luke Imhoff: ...
The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform?
Last time I tried it looked to me that the swig on ubuntu was broken (but the error was different). But I did not look deeper.
byer adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch, 9. Dezember 2009 21:24:45 schrieb Luke Imhoff:
The KDE backend assumes that KDE is built against QT 4, but Ubuntu is using KDE against QT3 still. Any chance someone more familiar with QT could add support for QT3?
Hm, KDE 3 is really history. I personally would not invest time here anymore. Better switch off the kde support on ubuntu than. bye adrian
On Tue, 2009-12-08 at 00:44 -0600, Adrian Schröter wrote:
Am Montag, 7. Dezember 2009 21:09:18 schrieb Luke Imhoff: ...
The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform?
Last time I tried it looked to me that the swig on ubuntu was broken (but the error was different). But I did not look deeper.
byer adrian
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I'm not using KDE, I was just trying to not drop features (since I believe the Ubuntu:9.10 repo is supposed to support Kubuntu too). I figured out what the old APIs were called, but I didn't actually test that the compiled backend works correctly, since like I said, I don't use KDE. Also, Ubuntu 9:10 uses KDE 4, but KDE4 uses QT 3. KDE 4 depends on libqt3-mt (multi-threaded). On Thu, 2009-12-10 at 00:13 -0600, Adrian Schröter wrote:
Am Mittwoch, 9. Dezember 2009 21:24:45 schrieb Luke Imhoff:
The KDE backend assumes that KDE is built against QT 4, but Ubuntu is using KDE against QT3 still. Any chance someone more familiar with QT could add support for QT3?
Hm, KDE 3 is really history. I personally would not invest time here anymore.
Better switch off the kde support on ubuntu than.
bye adrian
On Tue, 2009-12-08 at 00:44 -0600, Adrian Schröter wrote:
Am Montag, 7. Dezember 2009 21:09:18 schrieb Luke Imhoff: ...
The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform?
Last time I tried it looked to me that the swig on ubuntu was broken (but the error was different). But I did not look deeper.
byer adrian
--
Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 10. Dezember 2009 16:04:08 schrieb Luke Imhoff:
I'm not using KDE, I was just trying to not drop features (since I believe the Ubuntu:9.10 repo is supposed to support Kubuntu too). I figured out what the old APIs were called, but I didn't actually test that the compiled backend works correctly, since like I said, I don't use KDE.
Also, Ubuntu 9:10 uses KDE 4, but KDE4 uses QT 3. KDE 4 depends on libqt3-mt (multi-threaded).
Uh ? sounds a little bit broken. Usual KDE4 is not using qt3 at all. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 2009-12-10 at 09:11 -0600, Adrian Schröter wrote:
Am Donnerstag, 10. Dezember 2009 16:04:08 schrieb Luke Imhoff:
I'm not using KDE, I was just trying to not drop features (since I believe the Ubuntu:9.10 repo is supposed to support Kubuntu too). I figured out what the old APIs were called, but I didn't actually test that the compiled backend works correctly, since like I said, I don't use KDE.
Also, Ubuntu 9:10 uses KDE 4, but KDE4 uses QT 3. KDE 4 depends on libqt3-mt (multi-threaded).
Uh ? sounds a little bit broken. Usual KDE4 is not using qt3 at all.
KDE 4's headers were pulling in qptrlist.h, which is a QT 3 only file. Having just the QT 4 dev files didn't work. *shrug* Maybe I needed to add a define for the KDE headers to get them to not use QT 3.
bye adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 10. Dezember 2009 16:26:25 schrieb Luke Imhoff:
On Thu, 2009-12-10 at 09:11 -0600, Adrian Schröter wrote:
Am Donnerstag, 10. Dezember 2009 16:04:08 schrieb Luke Imhoff:
I'm not using KDE, I was just trying to not drop features (since I believe the Ubuntu:9.10 repo is supposed to support Kubuntu too). I figured out what the old APIs were called, but I didn't actually test that the compiled backend works correctly, since like I said, I don't use KDE.
Also, Ubuntu 9:10 uses KDE 4, but KDE4 uses QT 3. KDE 4 depends on libqt3-mt (multi-threaded).
Uh ? sounds a little bit broken. Usual KDE4 is not using qt3 at all.
KDE 4's headers were pulling in qptrlist.h, which is a QT 3 only file. Having just the QT 4 dev files didn't work. *shrug* Maybe I needed to add a define for the KDE headers to get them to not use QT 3.
There is a /usr/include/Qt3Support/q3ptrlist.h in the Qt4 lib. However, you need also to link against -lQt3Support afterwards. But you get rid of the original qt3 library stack via this. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter -
Luke Imhoff