#38879 closed defect (fixed)
log4cplus: Use macports libtool and thus support compilation against libc++
Reported by: | dh@… | Owned by: | macports@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | vhaisman@… | |
Port: | log4cplus |
Description
I am currently attempting to build various ports (in a separate tree) against libc++
rather than the default libstdc++
. Currently log4cplus
builds using its own libtool
shipped in the distribution. That libtool
does not support linking against libc++
(as it discards any -stdlib
option passed).
The following patch makes log4cplus
use the macports provided libtool
which correctly handles the -stdlib option.
Index: Portfile =================================================================== --- Portfile (revision 105277) +++ Portfile (working copy) @@ -19,3 +19,7 @@ checksums md5 306f758596f3a78cbe21a41e2362bac2 \ sha1 cffac9b8c6f7b7c2f6e19a029403b2f844aaf5fc \ rmd160 962ec0a49af0d345ce452799a2395cbe7eda3868 + +# macports libtool allows linking against libc++, the libtool in the distribution does not +depends_build port:libtool +build.args LIBTOOL=${prefix}/bin/glibtool
Change History (4)
comment:1 Changed 12 years ago by vhaisman@…
comment:3 Changed 12 years ago by dh@…
I believe this has been pushed (and accepted) upstream and will appear in 2.4.3. (At least the commentary on the patches we make of libtool 2.4.2 would indicate this)
comment:4 Changed 11 years ago by dh@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in r109789, also bumped to 1.1.x which I have been using in my tree for the last few months without issues
Note: See
TracTickets for help on using
tickets.
Why are the libtool changes necessary for this not part of the upstream libtool? Or are they and I have missed an update?