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 570072 - avoid duplicate symbols on OSX
avoid duplicate symbols on OSX
Status: RESOLVED DUPLICATE of bug 757374
Product: glib
Classification: Platform
Component: build
2.18.x
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-02-01 11:14 UTC by Fabian Groffen
Modified: 2017-11-21 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
avoid duplicate symbols on osx (475 bytes, patch)
2009-02-01 11:15 UTC, Fabian Groffen 		rejected Details | Review

Description Fabian Groffen 2009-02-01 11:14:35 UTC 
Please describe the problem:
/Users/shaunc/Gentoo/usr/lib/libiconv.dylib  -march=prescott -framework Carbon
-install_name  /Users/shaunc/Gentoo/usr/lib/libglade-2.0.0.dylib
-compatibility_version 1 -current_version 1.7 -Wl,-single_module
-Wl,-exported_symbols_list,.libs/libglade-2.0-symbols.expsym
ld: duplicate symbol _g_bit_nth_lsf in .libs/glade-xml.o and .libs/glade-init.o

collect2: ld returned 1 exit status
make[2]: *** [libglade-2.0.la] Error 1


Steps to reproduce:
1. compile it
2. 
3. 


Actual results:
collect2: ld returned 1 exit status

Expected results:
compile cleanly

Does this happen every time?
yes

Other information:
http://bugs.gentoo.org/221075

patch by Shaun Cloherty attached
Comment 1 Fabian Groffen 2009-02-01 11:15:22 UTC 
Created attachment 127689 [details] [review]
avoid duplicate symbols on osx
Comment 2 Philip Withnall 2017-11-21 11:53:18 UTC 
Review of attachment 127689 [details] [review]:

This was all changed radically in commit db2367e8782d7a39fc3e93d13f6a16f10cad04c2 (bug #757374), so this patch no longer applies or is relevant. Sorry for the delay in reviewing it.
Comment 3 Philip Withnall 2017-11-21 11:53:54 UTC 
If this is still a problem since bug #757374 was fixed, please file a new bug report. Thanks.

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