Opened 6 years ago
Closed 5 years ago
#58436 closed defect (fixed)
Automatic dependency tracking install dbus on OS X 10.4.11
Reported by: | SamBushman | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | tiger powerpc | Cc: | |
Port: | dbus |
Description
While attempting to install Pidgin on my iMac G4 (running OS X 10.4.11), I encountered an error during the configure stage of installing the dbus dependency. The error I see may be reproduced by simply attempting to install the dbus package on its own. Attached are the Main.log and Config.log files from my reproduction.
Attachments (2)
Change History (12)
Changed 6 years ago by SamBushman
Changed 6 years ago by SamBushman
Attachment: | config.log added |
---|
comment:1 Changed 6 years ago by kencu (Ken)
comment:2 Changed 6 years ago by SamBushman
Awesome! Thank you for the quick response! For those who don't know how to edit a ports file (like me up to about 10 minutes ago), the following page was useful: https://trac.macports.org/wiki/howto/Upgrade
Hopefully calling out the error and a clean solution will help others googling around.
comment:3 Changed 6 years ago by kencu (Ken)
If you like, spend a moment to learn how to open a PR on github for these fixes, and I'll commit them.
comment:4 Changed 6 years ago by mf2k (Frank Schima)
In the future, please fill in the Port field and add the port maintainer(s) to Cc (port info --maintainers dbus
), if any.
comment:5 Changed 6 years ago by mf2k (Frank Schima)
Keywords: | tiger added |
---|---|
Owner: | set to MarcusCalhoun-Lopez |
Port: | dbus added |
Status: | new → assigned |
comment:6 Changed 6 years ago by mf2k (Frank Schima)
Keywords: | powerpc added |
---|
comment:7 Changed 6 years ago by kencu (Ken)
not really a problem with dbus. Basically every port that uses autotools will need that block added on Tiger, unless I can figure out why it's actually occurring.
comment:8 Changed 6 years ago by kencu (Ken)
Looks like what is happening is that the configure script is calling make
to generate the dependency tracking information now -- this appears to have re-enabled in some recent update to autotools.
And when the configure script on Tiger calls make, it finds the old one in /usr/bin/make
rather than the new one in /opt/local/bin/gmake
(obviously), and the old make
barfs on the newer command syntax.
One way to fix this is to set up some configure & build env vars to point MAKE to the new gmake -- ugh - in every port -ugh.
OR -- if I just make a symlink from /opt/local/bin/gmake to /opt/local/bin/make then everything works without touching any portfiles.
This is getting to be too much work -- one symlink vs. tweaking hundreds of ports. I'm going to see if I can sell adding a symlink from gmake to make on Tiger by default, and save us all 1000 hours.
comment:10 Changed 5 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This is a common error lately on 10.4. I think it has to do with the older
make
program used on Tiger, together with a newer version ofautotools
that has come along recently.the immediate solution is to add a block like this to the Portfile
I don't know if there is a general solution we can apply to every build in
macports base
. I think we might solve this if we defaulted to a newer version ofmake
on Tiger, but I haven't explored that fully as yet.