You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by "Joseph Southwell (JIRA)" <lo...@logging.apache.org> on 2014/01/11 17:31:50 UTC
[jira] [Assigned] (LOGCXX-396) log4cxx-0.10.0 - compile error on
OSX Lion using clang-3.1 building universal due to old libtool scripts
[ https://issues.apache.org/jira/browse/LOGCXX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Southwell reassigned LOGCXX-396:
---------------------------------------
Assignee: Joseph Southwell (was: Curt Arnold)
> log4cxx-0.10.0 - compile error on OSX Lion using clang-3.1 building universal due to old libtool scripts
> --------------------------------------------------------------------------------------------------------
>
> Key: LOGCXX-396
> URL: https://issues.apache.org/jira/browse/LOGCXX-396
> Project: Log4cxx
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.10.0
> Environment: Mac OSX Lion 10.7.4, XCode-4.3.2, clang-3.1 (build 318)
> Reporter: nibbles
> Assignee: Joseph Southwell
> Priority: Blocker
> Labels: build, clang, libtool
>
> I'm reporting a compile error on OSX Lion when using clang and building universal for i386 and x86_64 due to old libtool scripts crafting a non-functional compile command for the liblog4cxx.dylib. I'm doing this for Homebrew, a package installer for Macs. The issue is discussed at length here:
> https://github.com/mxcl/homebrew/issues/12127
> The clue that the libtool scripts are too old to be useful is that the commands they choose during configure are not the ones I always see.
> The error arises when libtool calls `clang++ -r` but fails to add the arch flags to that command, `-arch i386 -arch x86_64` which causes the liblog4cxx.dylib to be missing all the 32bit symbols while it does contain the 64bit symbols. Please see the issue linked above for all the details.
> The solution for us is to run `autogen.sh` before configure, which fixes the problem by updating the build scripts.
> Thanks for reading this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)