After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 145514 - Galeon RPM does not compile on FC2 x86_64
Galeon RPM does not compile on FC2 x86_64
Status: RESOLVED DUPLICATE of bug 138997
Product: galeon
Classification: Deprecated
Component: general
1.3.16
Other Linux
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2004-07-06 15:52 UTC by Matt Hyclak
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matt Hyclak 2004-07-06 15:52:52 UTC
rpmbuild -ta galeon-1.3.16.tar.bz2

The build makes it to linking galeon-bin and fails with the following error:
/usr/lib/libpopt.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
Comment 1 Tommi Komulainen 2004-07-06 16:14:54 UTC
Galeon relies on pkgconfig to provide properly working compiler flags, that
error seem like 32- and 64-bit libraries are getting mixed up.  Please see if
the following thread is of any help.

http://sourceforge.net/mailarchive/forum.php?thread_id=3664093&forum_id=6200

If you're building against 64-bit libraries, the culprit is whoever is adding
libopt in the libraries list.
Comment 2 Matt Hyclak 2004-07-06 17:05:11 UTC
Hmm, you're right. Adding an "export CFLAGS=/usr/lib64" to the .spec file allows
it to compile, however galeon crashes on startup. Mozilla runs fine and is
compiled in 64-bit mode. I'm at a loss as to where to look. The backtrace is as
follows:

Backtrace was generated from '/usr/bin/galeon-bin'

Using host libthread_db library "/lib64/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 182902733024 (LWP 4613)]
[New Thread 1084225888 (LWP 4616)]
[Thread debugging using libthread_db enabled]
[New Thread 182902733024 (LWP 4613)]
[New Thread 1084225888 (LWP 4616)]
[Thread debugging using libthread_db enabled]
[New Thread 182902733024 (LWP 4613)]
[New Thread 1084225888 (LWP 4616)]
0x0000003fd390be74 in waitpid () from /lib64/tls/libpthread.so.0

Thread 1 (Thread 182902733024 (LWP 4613))

  • #0 waitpid
    from /lib64/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 nsProfileLock::FatalSignalHandler
    from /usr/lib64/mozilla-1.6/libgtkembedmoz.so
  • #3 <signal handler called>
  • #4 g_object_disconnect
    from /usr/lib64/libgobject-2.0.so.0
  • #5 gtk_ui_manager_remove_action_group
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 galeon_tabs_menu_rebuild
  • #7 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_by_name
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #12 gul_notebook_insert_page
  • #13 galeon_window_add_tab
  • #14 galeon_shell_new_tab_from_embed
  • #15 galeon_shell_new_tab
  • #16 galeon_automation_loadurl
  • #17 galeon_automation_complete_initialization
  • #18 main
  • #0 waitpid
    from /lib64/tls/libpthread.so.0

Comment 3 Tommi Komulainen 2004-07-06 17:27:33 UTC
You need more recent gtk+

*** This bug has been marked as a duplicate of 138997 ***