Opened 14 years ago
Closed 14 years ago
#26138 closed defect (invalid)
qrupdate fails to build if libtool port is active
| Reported by: | ned@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | qrupdate libtool | Cc: | ryandesign (Ryan Carsten Schmidt) |
| Port: | qrupdate |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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.
Change History (3)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Description: | modified (diff) |
comment:2 Changed 14 years ago by ned@…
I did have a symlink called libtool; thanks for pointing out that possibility. Wonder why I did that (probably to get around a problem with another port). Thanks!
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Ok, glad you found the source of the problem!
Note: See
TracTickets for help on using
tickets.
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.