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 Don Wakefield <do...@mentor.com> on 2015/04/17 22:44:10 UTC
Redhat Enterprise Linux Compatibility
Folks,
I apologize in advance if this should go to the users' mailing list...
We adopted log4cxx several years ago, building it against Redhat
Enterprise Linux 5.7, and using it with our product. Now a larger
corporate entity has begun pushing for our products to support RHEL7. We
have tried:
1) running the RHEL5.7 binary on a RHEL7 machine:
failure due to missing libraries (only newer named versions
of these libraries are installed on RHEL7 boxes)
2) rebuilding log4cxx on an RHEL7 box:
failure due to requiring specific versions of libraries (and
hence, differing headers)
Following up on the runtime failure messages, we find specific issues
with apr-util (for an example):
[donw@ostest lib]$ ldd libaprutil-1.so.0.2.2
linux-vdso.so.1 => (0x00007fff299fe000)
libgdbm.so.2 => not found
libdb-4.2.so => not found
libexpat.so.0 => not found
libapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x00007f08d7b73000)
libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f08d796d000)
librt.so.1 => /usr/lib64/librt.so.1 (0x00007f08d7765000)
libcrypt.so.1 => /usr/lib64/libcrypt.so.1 (0x00007f08d752e000)
libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007f08d7311000)
libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007f08d710d000)
libc.so.6 => /usr/lib64/libc.so.6 (0x00007f08d6d4c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f08d7ee9000)
libfreebl3.so => /usr/lib64/libfreebl3.so (0x00007f08d6ace000)
Looking just for libdb-4.2.so, we see the relevant entries are
[donw@ostest lib]$ ls -l /lib64/libdb*
-rwxr-xr-x. 1 root root 1544688 Jan 24 2014 /lib64/libdb-4.7.so
-rwxr-xr-x. 1 root root 1846248 Jan 26 2014 /lib64/libdb-5.3.so
lrwxrwxrwx. 1 root root 12 Feb 3 23:40 /lib64/libdb-5.so ->
libdb-5.3.so
-rwxr-xr-x. 1 root root 1665128 Jan 24 2014 /lib64/libdb_cxx-4.7.so
lrwxrwxrwx. 1 root root 12 Feb 3 23:42 /lib64/libdb.so ->
libdb-5.3.so
Similar results exist for /usr/lib64.
It appears that just running the RHEL57 binaries on a standard RHEL7 box
is not an option. We also can't tell our customers "just load these
older libdb/other libraries".
So I guess my main question is, are there any plans on updating log4cxx
and its ancillary apr libraries to build/be compatible with RHEL7?
--
Don Wakefield Mentor Graphics Corporation
(503) 685-1262 8005 S.W. Boeckman Road
don_wakefield@mentorg.com Wilsonville, OR 97070-7777
Re: Redhat Enterprise Linux Compatibility
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Don Wakefield,
am Freitag, 17. April 2015 um 22:44 schrieben Sie:
> So I guess my main question is, are there any plans on updating log4cxx
> and its ancillary apr libraries to build/be compatible with RHEL7?
I have no experience with RHEL, but isn't that something the
maintainer of the package should do? I don't see that log4cxx provides
any RHEL specific build instructions at all.
Besides that, it is very unlikely that the project will release any
new official version any time soon, even if we fix whatever needs to
be fixed. It tried in the past, but it simply didn't work out for
various reasons...
So to me it seems you need to take the current trunk and build the lib
on your own, fixing all build errors occurring. We may assist you with
that, but I'm for example more a Windows guy using ANT, so my
knowledge my be of less value. But I do have commit access and can
write bugs, so your work surely won't be lost, we can create a RHEL7
branch if your patches conflict with the trunk or whatever...
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow