I'm following this thread here
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=23749&forum=3...
to build an rpm for thunderbird 3.1.6/3.1.7 from source. While it works well on i386, compilation fails for x86_64. Any advice how to fix the spec file?
... rm -f libthebes.so c++ -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long -pedantic -fno-strict-aliasing -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -Os -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -I/usr/src/redhat/BUILD/thunderbird-3.1.7/comm-1.9.2/objdir-tb/mozilla/dist/include/cairo -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -fPIC -shared -Wl,-z,defs -Wl,-h,libthebes.so -o libthebes.so cairo-xlib-utils.o woff.o gfxASurface.o gfxAlphaRecovery.o gfxBlur.o gfxContext.o gfxImageSurface.o gfxFont.o gfxFontMissingGlyphs.o gfxFontTest.o gfxFontUtils.o gfxMatrix.o gfxPath.o gfxPattern.o gfxPlatform.o gfxPlatformFontList.o gfxRect.o gfxSkipChars.o gfxTextRunCache.o gfxTextRunWordCache.o gfxUserFontSet.o gfxPangoFonts.o gfxXlibSurface.o gfxPlatformGtk.o gfxGdkNativeRenderer.o gfxPDFSurface.o gfxPSSurface.o gfxFontconfigUtils.o gfxFT2FontBase.o gfxFT2Utils.o nsUnicodeRange.o -lpthread -Wl,-rpath,/usr/lib64/thunderbird-3.1 -Wl,-rpath-link,/usr/src/redhat/BUILD/thunderbird-3.1.7/comm-1.9.2/objdir-tb/mozilla/dist/bin -Wl,-rpath-link,/usr/lib ../../../gfx/cairo/cairo/src/libmozcairo.a ../../../gfx/cairo/libpixman/src/libmozlibpixman.a -L/usr/lib64 -lXrender -lfreetype -lfontconfig /usr/src/redhat/BUILD/thunderbird-3.1.7/comm-1.9.2/objdir-tb/mozilla/dist/lib/libunicharutil_s.a -L/usr/src/redhat/BUILD/thunderbird-3.1.7/comm-1.9.2/objdir-tb/mozilla/dist/bin -lxpcom -lxpcom_core -L/usr/src/redhat/BUILD/thunderbird-3.1.7/comm-1.9.2/objdir-tb/mozilla/dist/lib -lplds4 -lplc4 -lnspr4 -lpthread -ldl -lz ../../../gfx/qcms/libmozqcms.a ../../../gfx/ots/src/libmozots.a -L/lib64 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lz -L/usr/lib64 -lX11 -L/lib64 -lgtk-x11-2.0 -latk-1.0 -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lasound -ldl -lm /usr/bin/ld: gfxUserFontSet.o: relocation R_X86_64_PC32 against `ots::Process(ots::OTSStream*, unsigned char const*, unsigned long, bool)' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
On Wed, 5 Jan 2011, lhecking@users.sourceforge.net wrote:
To: centos@centos.org From: lhecking@users.sourceforge.net Subject: [CentOS] Compiling thunderbird
I'm following this thread here
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=23749&forum=3...
to build an rpm for thunderbird 3.1.6/3.1.7 from source. While it works well on i386, compilation fails for x86_64. Any advice how to fix the spec file?
This doesn't look good.
rm -f libthebes.so
/usr/bin/ld: gfxUserFontSet.o: relocation R_X86_64_PC32 against `ots::Process(ots::OTSStream*, unsigned char const*, unsigned long, bool)' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status
HTH
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
/usr/bin/ld: gfxUserFontSet.o: relocation R_X86_64_PC32 against `ots::Process(ots::OTSStream*, unsigned char const*, unsigned long, bool)' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status
HTH
As far as I can tell, all objects are being compiled with -fPIC. And -m64. Including gfxUserFontSet.cpp.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
As far as I can tell, all objects are being compiled with -fPIC. And -m64. Including gfxUserFontSet.cpp.
It's a bug, and I was able to compile it by applying the fix from here:
https://bugzilla.mozilla.org/show_bug.cgi?id=615196
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
lhecking@users.sourceforge.net wrote:
As far as I can tell, all objects are being compiled with -fPIC. And -m64. Including gfxUserFontSet.cpp.
It's a bug, and I was able to compile it by applying the fix from here:
So are you going to offer the rpm to the testing repo? ;-)
This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Rob Kampen writes:
lhecking@users.sourceforge.net wrote:
As far as I can tell, all objects are being compiled with -fPIC. And -m64. Including gfxUserFontSet.cpp.
It's a bug, and I was able to compile it by applying the fix from here:
So are you going to offer the rpm to the testing repo? ;-)
I'm not sure I'll use this rpm myself because it doesn't work with Lightning ("lightning" could not be installed because it is not compatible with your Thunderbird build type (Linux_x86_64-gcc3). Please contact the author of this item about the problem).
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
lhecking@users.sourceforge.net writes:
Rob Kampen writes:
lhecking@users.sourceforge.net wrote:
As far as I can tell, all objects are being compiled with -fPIC. And -m64. Including gfxUserFontSet.cpp.
It's a bug, and I was able to compile it by applying the fix from here:
So are you going to offer the rpm to the testing repo? ;-)
I'm not sure I'll use this rpm myself because it doesn't work with Lightning ("lightning" could not be installed because it is not compatible with your Thunderbird build type (Linux_x86_64-gcc3). Please contact the author of this item about the problem).
There is a contributed build of Lightning for x86_64 here
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/1.0b...
but, frankly, this is useless in an environment where users may work on i386 machines today and x86_64 tomorrow. The 64-bit add-on will of course not work on 32-bit, and vice versa. The best solution here is to use the 32-bit version of tb everywhere.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------