www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hixson <dhix...@lucent.com>
Subject general/7533: 'make install' fails during install of dso/unix on 'libtool' if /home/root/libtool does not exist
Date Fri, 06 Apr 2001 18:51:10 GMT

>Number:         7533
>Category:       general
>Synopsis:       'make install' fails during install of dso/unix on 'libtool' if /home/root/libtool
does not exist
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Apr 06 12:00:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     dhixson@lucent.com
>Release:        2.0.16
>Organization:
apache
>Environment:
# uname -a
HP-UX shield B.11.00 E 9000/888 2140000726 8-user license

11.00 box running current patch level, using gcc 2.95.2.
>Description:
# /opt/tusc/bin/tusc -fn -o /tmp/tusc1.out make install
Making install in srclib
Making install in apr
Making all in lib
Making all in strings
Making all in passwd
Making all in tables
Making all in file_io/unix
Making all in network_io/unix
Making all in threadproc/unix
Making all in misc/unix
Making all in locks/unix
Making all in time/unix
Making all in mmap/unix
Making all in shmem/unix
        (cd mm && make libmm.la)
`libmm.la' is up to date.
Making all in i18n/unix
Making all in user/unix
Making all in dso/unix
        if [ ! -d /opt/httpd-2_0_16/include ]; then \
            ./build/mkdir.sh /opt/httpd-2_0_16/include; \
        fi; \
        cp include/*.h /opt/httpd-2_0_16/include; \
        if [ ! -d /opt/httpd-2_0_16/lib ]; then \
            ./build/mkdir.sh /opt/httpd-2_0_16/lib; \
        fi; \
        libtool --mode=install cp libapr.la /opt/httpd-2_0_16/lib
sh[8]: libtool:  not found.
*** Error exit code 127

Stop.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.




Relevant output from tusc indicates the problem.



[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a80, 0x7f7e1a60) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a60, 0x7f7e1a80) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a80, 0x7f7e1a60) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a60, 0x7f7e1a80) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a80, 0x7f7e1a60) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a60, 0x7f7e1a80) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a80, 0x7f7e1a60) .. = 0
[sh -ce if [ ] execve("/home/root/libtool", 0x400247f8, 0x40024878) ERR#2 ENOENT
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e18f0, 0x7f7e1910) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1910, 0x7f7e18f0) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e18f0, 0x7f7e1910) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1910, 0x7f7e18f0) .. = 0
[sh -ce if [ ] open("/usr/lib/nls/msg/C/psh.cat", O_RDONLY, 0177777) = 4
[sh -ce if [ ] fstat(4, 0x7f7e25a8) .............................. = 0
[sh -ce if [ ] fcntl(4, F_SETFD, 1) .............................. = 0
[sh -ce if [ ] lseek(4, 0, SEEK_SET) ............................. = 0
[sh -ce if [ ] read(4, "m s g c a t 0 1 \0\0\09e\001\001".., 1212) = 1212
[sh -ce if [ ] lseek(4, 2090, SEEK_SET) .......................... = 2090
[sh -ce if [ ] read(4, "  n o t   f o u n d . ", 11) ............. = 11
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e19e0, 0x7f7e1a00) .. = 0
[sh -ce if [ ] sigprocmask(SIG_SETMASK, 0x7f7e1a00, 0x7f7e19e0) .. = 0



After I created the directory /home/root and placed a copy of the libtool file from the apache
directory out there, it worked like a champ.
>How-To-Repeat:
Problem should be reproducable on any UX system that doesn't have a copy of libtool in /home/root.
 Unsure of the behavior if libtool can be found in the path.
>Fix:
Since you seem to include or build a copy of libtool with the distribution, include a direct
reference to it in the build directory.
The workaround is easy enough for someone who can trace down the problem, and probably wouldn't
be seen on any machines that have gcc 'well configured' with all the the correct tools in
the path.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message