Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#63149 closed defect (fixed)

gtk2 @2.24.32_0+x11: Configure error on 10.4.11

Reported by: evanmiller (Evan Miller) Owned by: kencu (Ken)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc:
Port: gtk2

Description

When attempting to install gtk2 I see this in the main log:

:info:configure config.status: executing depfiles commands
:info:configure config.status: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk2/gtk2/work/gtk+-2.24.32':
:info:configure config.status: error: Something went wrong bootstrapping makefile fragments
:info:configure     for automatic dependency tracking.  If GNU make was not used, consider
:info:configure     re-running the configure script with MAKE="gmake" (or whatever is
:info:configure     necessary).  You can also try re-running configure with the
:info:configure     '--disable-dependency-tracking' option to at least be able to build
:info:configure     the package (albeit without support for automatic dependency tracking).
:info:configure See `config.log' for more details

config.log contains (not much extra help):

config.status:1852: cd perf       && sed -e '/# am--include-marker/d' Makefile         | make -f - am--depfiles
config.status:1857: $? = 0
config.status:1861: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk2/gtk2/work/gtk+-2.24.32':
config.status:1863: error: Something went wrong bootstrapping makefile fragments
    for automatic dependency tracking.  If GNU make was not used, consider
    re-running the configure script with MAKE="gmake" (or whatever is
    necessary).  You can also try re-running configure with the
    '--disable-dependency-tracking' option to at least be able to build
    the package (albeit without support for automatic dependency tracking).
See `config.log' for more details

System information:

:debug:main Starting logging for gtk2 @2.24.32_0+x11
:debug:sysinfo Mac OS X 10.4.11 (darwin/8.11.0) arch powerpc
:debug:sysinfo MacPorts 2.7.1
:debug:sysinfo Xcode 2.5
:debug:sysinfo SDK 10.4
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.4

Attaching main.log and config.log for review.

Attachments (2)

main.log (59.6 KB) - added by evanmiller (Evan Miller) 3 years ago.
Main gtk2 log
config.log (174.1 KB) - added by evanmiller (Evan Miller) 3 years ago.
gtk2 configure log

Download all attachments as: .zip

Change History (10)

Changed 3 years ago by evanmiller (Evan Miller)

Attachment: main.log added

Main gtk2 log

Changed 3 years ago by evanmiller (Evan Miller)

Attachment: config.log added

gtk2 configure log

comment:1 Changed 3 years ago by kencu (Ken)

There are a few idiosyncracies when building things on Tiger. One of them is this --disable-dependency-tracking issue.

I forget just now why Tiger shows this more than other systems. Presumably it has to do with the older "make" program it defaults to, but somehow I think that is not all of the explanation. The "scientific basis" for it aside, in practical terms, what you do when this happens is to edit the Portfile:

bbedit `port file gtk2`

and add that configure argument it wants in the right place in the Portfile, below the other configure args, where it won't get clobbered:

configure.args-append --disable-dependency-tracking

and then clean your build and try again:

sudo port clean gtk2
sudo port -v install gtk2

and with luck you will either get a successful build, or at least get to the next issue down the chain.

Your portfile edits are all erased each time you do a sudo port selfuldate so you don't need to worry about making a mess of things. You can save your edits if you want to do that by creating a local repository of your edited Portfiles, but that is for another day.

comment:2 Changed 3 years ago by evanmiller (Evan Miller)

Thanks for the explanation and workaround – although I don't find either all that satisfying!

It sounds like if I implement the workaround, and gtk2 is later updated in the ports tree, then I may hit the issue again. Is that correct?

comment:3 Changed 3 years ago by kencu (Ken)

well that is where you open a PR with your fix and see if you can sell it here to MacPorts.

that is how I started -- 1.2 million PRs and commits ago ;>

comment:4 Changed 3 years ago by kencu (Ken)

If you have fixes that you have made to ports, and you can't seem to sell them, you can keep them for yourself locally.

It takes 2 minutes to set your second one up. The first one takes a bit longer while you sort it out. The gory details for local portfile repos are here:

https://guide.macports.org/chunked/development.local-repositories.html

my own local repo for Tiger is here:

http://github.com/kencu/TigerPorts.git

comment:5 Changed 3 years ago by evanmiller (Evan Miller)

Got it – thanks for the info. I'll see if I can make any progress on the issue.

comment:6 Changed 3 years ago by kencu (Ken)

Resolution: fixed
Status: assignedclosed

In a395e9281c8688b662a03b75f1bcb1e1d67ccee2/macports-ports (master):

gtk2: disable dependency tracking on Tiger

closes: #63149

comment:7 Changed 3 years ago by kencu (Ken)

that turns out to be all it wanted, in this case. So I pushed it.

comment:8 Changed 3 years ago by evanmiller (Evan Miller)

Thanks for the change - it configures just fine now. Just waiting on the G3 to build it...

Note: See TracTickets for help on using tickets.