[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Portability of -no-undefined

From: Roger Leigh
Subject: Portability of -no-undefined
Date: Tue, 19 Oct 2004 20:49:30 +0100
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Many Makefile.ams use logic like this:

    no_undefined = -no-undefined

    lib_LTLIBRARIES = libfoo
    libfoo_LDFLAGS = ... $(no_undefined)

This makes -no-undefined only get used when building DLLs on a Win32
platform.  However, if this were specified directly:

    foo_LDFLAGS = -no-undefined

does this do anything on other platforms where it's not required?

I tested both on GNU/Linux, and while I couldn't see any functional
difference between the two libs, the binaries were not identical.  It
does concern me that it had /some/ effect, especially since it isn't
obvious what exactly it actually did.

If there wasn't some (perhaps historical) reason for the former usage,
it seems a little odd to use platform-specific stuff in a tool that's
supposed to be platform-independent.

Please could anyone clarify exactly how -no-undefined should be used
when building shared libraries for a package that should build on all

Many thanks,

Roger Leigh

                Printing on GNU/Linux?
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]