[jira] [Resolved] (LOGCXX-333) Centos 5 x64 fails to link with libexpat.so

["Thorsten Schöning (Jira)" <lo...@logging.apache.org>]

     [ https://issues.apache.org/jira/browse/LOGCXX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thorsten Schöning resolved LOGCXX-333.
--------------------------------------
    Resolution: Cannot Reproduce

Because we are trying to reduce the backlog of open issues, I'm closing this one right now. The described environment in which the problem has been reported originally is pretty outdated these days and things might have been fixed already with a newer version of log4cxx and/or a new environment. If this concrete problem is still relevant for someone, feel free to reopen and provide the necessary details. Otherwise it's best to create a new issue describing the new environment and problem.

> Centos 5 x64 fails to link with libexpat.so
> -------------------------------------------
>
>                 Key: LOGCXX-333
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-333
>             Project: Log4cxx
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.10.0
>         Environment: Centos 5 x64
>            Reporter: Mostafa
>            Assignee: Curt Arnold
>            Priority: Major
>
> log4cxx fails to link with libexpat.so on Centos 5 x64 with following error message:
> "/usr/lib/libexpat.so: could not read symbols: File in wrong format"
> (It's looking in the wrong dir, it should be searching /usr/lib64.)
> Had to use the following workaround:
> ./configure --with-expat=builtin
> SideNote:
> This sounds a lot like the problem that apr-util had with the same error message.
> See:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=28205
> http://blog.chaos-co.de/index.php?/archives/2-Apache-patch-for-libexpat.so-could-not-read-symbols-File-in-wrong-format.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)