[MacPorts] #26138: qrupdate fails to build if libtool port is active

MacPorts noreply at macports.org
Thu Aug 19 14:19:34 PDT 2010


#26138: qrupdate fails to build if libtool port is active
--------------------------------+-------------------------------------------
 Reporter:  ned@…               |       Owner:  macports-tickets@…                   
     Type:  defect              |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  1.9.1                                
 Keywords:  qrupdate libtool    |        Port:  qrupdate                             
--------------------------------+-------------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Old description:

> The Portfile for qrupdate 1.1.1 edits src/Makefile to change the call to
> "ar -cr" into a call to "libtool -o". However, that usage of libtool only
> works with the system libtool in /usr/bin, not with the Macports libtool
> (which is a later version of GNU libtool).
>
> So if you have the Macports libtool port active, you get
>
> libtool: unrecognized option: -o
>
> The workaround is to deactivate the libtool port before building
> qrupdate.
>
> However, this should be fixed to allow usage with the Macports libtool
> port active.

New description:

 The Portfile for qrupdate 1.1.1 edits src/Makefile to change the call to
 "ar -cr" into a call to "libtool -o". However, that usage of libtool only
 works with the system libtool in /usr/bin, not with the Macports libtool
 (which is a later version of GNU libtool).

 So if you have the Macports libtool port active, you get

 {{{
 libtool: unrecognized option: -o
 }}}

 The workaround is to deactivate the libtool port before building qrupdate.

 However, this should be fixed to allow usage with the Macports libtool
 port active.

--

Comment:

 The libtool port does not install a program called "libtool", it installs
 a program called "glibtool", so this should not be a problem. Or have you
 created a symlink "libtool" pointing to "glibtool"? If so, then that is
 the problem.

-- 
Ticket URL: <http://trac.macports.org/ticket/26138#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list