[MacPorts] #32982: libtool-2.4.2: patch to allow -stdlib=* as linker flags
MacPorts
noreply at macports.org
Sun Jan 22 08:56:16 PST 2012
#32982: libtool-2.4.2: patch to allow -stdlib=* as linker flags
--------------------------------+-------------------------------------------
Reporter: titus@… | Owner: ram@…
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port: libtool
--------------------------------+-------------------------------------------
Comment(by titus@…):
It's simply that libtool filters linker options that are unknown to it.
It refuses to pass -stdlib=libc++ to clang++ as the linker.
No macport uses this up to now, but it's necessary for my software.
I've just sent some general questions about that to the mailing list.
A simple test is to try to compile cppunit with libc++:
{{{
tar xzf /opt/local/var/macports/distfiles/cppunit/cppunit-1.12.1.tar.gz
cd cppunit-1.12.1
autoreconf -fvi
export CC=clang
export CXX=clang++
export CXXFLAGS=-libstdc++
export LDFLAGS=-libstdc++
./configure
make
}}}
This fails during linking the dylib because for compilation libc++ header
files get used,
but for linking the flag is dropped by libtool, so clang++ tries to link
to libstdc++,
which of course has to fail.
After modifying libtool with the patch, and executing "autoreconf -fvi"
before
./configuring cppunit, the dylib linking step is ok.
I don't know why the mail to gnu.org does not show up.
Is it a moderated list? Do I have to subscribe to something?
Did you successfully post to this address?
My server says
{{{
Jan 22 13:30:40 postfix/smtp[37774]: D8B951C583E1: to=<bug-
libtool at gnu.org>, relay=eggs.gnu.org[140.186.70.92]:25, status=sent (250
OK id=1RowZE-000499-DT)
}}}
--
Ticket URL: <https://trac.macports.org/ticket/32982#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list