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 583010 - "RTLD_GLOBAL brokenness" test is broken
"RTLD_GLOBAL brokenness" test is broken
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: build
2.20.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-05-18 04:02 UTC by Daniel Macks
Modified: 2016-07-08 07:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Macks 2009-05-18 04:02:38 UTC
configure.in does:

>${SHELL} ./libtool --mode=compile ${CC} -shared \
>	-export-dynamic -o plugin.o plugin.c 2>&1 >/dev/null

and then uses plugin.o as part of a subsequent test. However, that libtool call is broken two ways, so the test section gives up well before actually doing $whatever with plugin.o. Building on OS X, I get:

checking for dlopen... yes
checking for dlsym... yes
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: unknown flag: -export-dynamic
collect2: ld returned 1 exit status

Yup, -export-dynamic is a flag for libtool --mode=link not --mode=compile. I have no idea what's really being tested next, but it looks like the AC_TRY_RUN program tries to dlopen the compiled object, which seems weird...shouldn't one be trying to dlopen a dynamic library of some sort rather than a simple .o?

But removing that flag doesn't help, because there's another mistake in the libtool syntax:

libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

Need to pass a --tag=CC (I think that became a hard requirement as of libtool2?).
Comment 1 Daniel Macks 2016-07-08 07:12:33 UTC
Fixed by 59ee6dbc004adda8c4e4c8ff58bf21a9173eb99f long ago.
Comment 2 Daniel Macks 2016-07-08 07:14:49 UTC
(In reply to Daniel Macks from comment #1)
> Fixed by 59ee6dbc004adda8c4e4c8ff58bf21a9173eb99f long ago.

...which was via Bug 640202