DO NOT REPLY [Bug 33025] New: - libtool is part of httpd 2.0 build, libtoolize is not, buildconf fails

[bu...@apache.org]

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=33025>.
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=33025

           Summary: libtool is part of httpd 2.0 build, libtoolize is not,
                    buildconf fails
           Product: Apache httpd-2.0
           Version: 2.0.52
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Build
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: johnk@nstc.nec.com.au


Recently I introduced httpd 2.0.52 to the web infrastructure of our project.

I had to use mod_jk, and link it statically into httpd. This required running
autoconf's buildconf command to re-generate the configure script (due to the
addition of the mod_jk's m4 fragment to the autoconf input).

buildconf failed because it could not find libtoolize, which is command that is
part of libtool.

It appears libtool itself is incorporated in the httpd 2.0 build, and this
supports configure and the Makefile's resulting from the configure process.

Is it worth incorporating libtoolize in the httpd 2.0 build as well?
(to support anyone who must use autoconf to regenerate configure, etc.)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org