[
https://issues.jboss.org/browse/AS7-2695?page=com.atlassian.jira.plugin.s...
]
Mladen Turk commented on AS7-2695:
----------------------------------
What do you meany by: "Either the library is there and it's loaded, or it's
not and it's skipped"
Loaded by whom and when?
I still do not understand what are you talking about.
AS works out of box on my Fedora using tomcat-native rpm
without any setup.
Are you saying we should refuse to load anything outside module/lib?
Package APR native libraries correctly
--------------------------------------
Key: AS7-2695
URL:
https://issues.jboss.org/browse/AS7-2695
Project: Application Server 7
Issue Type: Task
Components: Web
Reporter: David Lloyd
Assignee: Remy Maucherat
Fix For: 7.1.0.Final
Attachments: jbossweb-native.jar.jar
The APR libraries for native jbossweb should be packaged in the "lib" directory
of the module under the platform specific name, e.g.
* {{lib/linux-i686/libxxxx.so}}
* {{lib/linux-x86_64/libxxxx.so}}
* {{lib/solaris-sparc/libxxxx.so}}
* {{lib/solaris-sparcv9/libxxxx.so}}
* {{lib/solaris-i686/libxxxx.so}}
* {{lib/solaris-x68_64/libxxxx.so}}
* {{lib/macosx-i686/libxxxx.sl}}
* {{lib/macosx-x86_64/libxxxx.sl}}
For the case where you need to vary the library based on the Solaris version, you have
two options:
* (best solution) rework the library to use weak symbols and/or libc probes and/or system
call error detection, to detect features which are present and absent and adjust at
runtime
* Introduce more than one library in each of the solaris-xxx directories with the version
suffix, e.g. libnative-2.8.so or similar and check for solaris at load time, and if
solaris, choose the library with the version encoded in the name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira