You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/05/19 11:11:01 UTC
DO NOT REPLY [Bug 29078] New: -
Libtool distributed with apache does not work properly on AIX
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29078>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29078
Libtool distributed with apache does not work properly on AIX
Summary: Libtool distributed with apache does not work properly
on AIX
Product: Apache httpd-2.0
Version: 2.0.49
Platform: Other
OS/Version: AIX
Status: NEW
Severity: Blocker
Priority: Other
Component: Build
AssignedTo: bugs@httpd.apache.org
ReportedBy: krist.vanbesien@bit.admin.ch
I wanted to build mod_jk2 on AIX. The normal build process uses the libtool
distributed with apache. This libtool does not work on our system. The reason
seems to be a bug in libtool, which is triggerd by the fact that we keep apache
sources, binaries and docroots on different filesystem.
Under certain circumstances libtool tries to create a lockfile by creating a
hard link to from itself to the working directory:
if test "$need_locks" = yes; then
until $run ln "$0" "$lockfile" 2>/dev/null; do
$show "Waiting for $lockfile to be removed"
sleep 2
done
ln as it is called in libtool does not work across filesystems though. The
problem is worsened by the fact that libtool is often called with the --silent
option, and that ln's output is sent to /dev/null. So the user never gets to
find out what is going on...
I replaced the "ln" with "$LN_S" in libtool, and this allowed me to compile the
module without any problem.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org