Received: (qmail 83383 invoked by uid 501); 30 Mar 2001 21:55:36 -0000
Message-Id: <20010330215536.83382.qmail@apache.org>
Date: 30 Mar 2001 21:55:36 -0000
From: jun-ichiro hagino <itojun@iijlab.net>
Reply-To: itojun@iijlab.net
To: submit@bugz.apache.org
Subject: libtool issues: shlibs/mods does not get installed, installation does not use libtool
X-Send-Pr-Version: 3.110

>Number:         7491
>Category:       build
>Synopsis:       libtool issues: shlibs/mods does not get installed, installation does not use libtool
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Mar 30 14:00:01 PST 2001
>Closed-Date:    Fri Aug 31 15:33:31 PDT 2001
>Last-Modified:  Fri Aug 31 15:33:31 PDT 2001
>Originator:     itojun@iijlab.net
>Release:        2.0.15
>Organization:
>Environment:
NetBSD starfruit.itojun.org 1.5T NetBSD 1.5T (STARFRUIT) #431: Fri Mar 30 19:59:50 JST 2001     itojun@starfruit.itojun.org:/usr/home/itojun/NetBSD/src/sys/arch/i386/compile/STARFRUIT i386
>Description:
shared libraries does not seem to get installed by normal Makefile path.
nor DSO moduels are. (sorry if this is configuration issue on my side).

as far as I undrstand, binaries built with libtool must be installed by using
"libtool --mode=install install foobar", not by "cp -p".
>How-To-Repeat:
make install, and see the log carefully.
>Fix:
for the second item, define INSTALL_foo properly in build/rules.mk or other place to the appropriate one.
always use ${INSTALL_PROGRAM} or ${INSTALL_SCRIPT}.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: rbb
State-Changed-When: Fri Aug 31 15:33:31 PDT 2001
State-Changed-Why:
This has been fixed since 2.0.15, and will be available in
the next release of Apache 2.0.

Thank you for using Apache.
>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!     ]