Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#63151 closed defect (fixed)

gtk3 @3.24.23_0+x11: Configure error on 10.4.11

Reported by: evanmiller (Evan Miller) Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: kencu (Ken)
Port: gtk3

Description

This report is nearly identical to #63149 but applies to gtk3 instead of gtk2.

main.log excerpt:

: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_gtk3/gtk3/work/gtk+-3.24.23':
: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
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.23" && ./configure --prefix=/opt/local --enable-static --disable-glibtest --enable-introspection --disable-cloudprint --disable-wayland-backend --disable-schemas-compile gio_can_sniff=yes --disable-cups --enable-xinerama --x-include=/opt/local/include --x-lib=/opt/local/lib --enable-x11-backend
:info:configure Exit code: 1
:error:configure Failed to configure gtk3: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.23/config.log
:error:configure Failed to configure gtk3: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/main.log for details.

config.log excerpt:

config.status:1938: cd modules/printbackends/test       && sed -e '/# am--include-marker/d' Makefile         | make -f - am--depfiles
config.status:1943: $? = 0
config.status:1947: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.23':
config.status:1949: 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:clean Starting logging for gtk3 @3.24.23_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

My understanding is that configuring with --disable-dependency-tracking on 10.4 targets will resolve the issue. Log files will be attached.

Attachments (2)

main.log (41.8 KB) - added by evanmiller (Evan Miller) 3 years ago.
gtk3 main.log
config.log (175.2 KB) - added by evanmiller (Evan Miller) 3 years ago.
gtk3 config.log

Download all attachments as: .zip

Change History (9)

Changed 3 years ago by evanmiller (Evan Miller)

Attachment: main.log added

gtk3 main.log

Changed 3 years ago by evanmiller (Evan Miller)

Attachment: config.log added

gtk3 config.log

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

Here is where we (I) really hope that you could try adding the one-liner fix to gtk3, seeing if it worked there too, and then let us know that it fixed the build and that we need to add it to gtk3 as well (which seems quite likely and obvious, but someone needs to try it).

There are relatively fewer users on Tiger, and we are hoping that people like you ( who seem so far to be quite skilled) might help us (me) by taking that extra step and coming up with the solutions as well!

Want to give it a go? Look at what I did with gtk2, see if the gtk3 Portfile has that same block, and if it looks clear enough, give it a try!

gtk2 and gtk3 used to build without adding --disable-dependency-tracking -- maybe the newer autoconf has changed that. If so, we might need to add this to 100 ports, or maybe 1000!

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

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

Thanks for doing that... it is much appreciated, and now that you've done that first step, further contributions will be much easier.

We need to wait a short period of time (3days) for the maintainer to review. Dave does not run Tiger any more, and can't test it, so may not weigh in. After 3 days, we can commit it.

MacPorts is quite trusting, but to make it easier for people to know that the change you made works, we often will add a little "proof-of-life" to the PR showing that the port is installed after this change.

I usually just do a quick port -v installed gtk3 for example and put the output in the PR, so that people know it really did work. This is optional, obviously, and don't worry about doing it now, but as most people can't test Tiger, it makes them a bit more comfortable committing the PR to see it worked.

Great to have you around! Much of MacPorts works on Tiger, and more can be made to work.

Last I checked I had over 1,000 ports installed on my Tiger box.

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

Well I am coming over from TigerBrew - I like that Tiger support is integrated into the main MacPorts tree, rather than forked off into a separate universe. Seems to be easier to get the latest software that way.

My interests are in testing a few of my C libraries on Tiger / PowerPC, since that seems like a good way to uncover endian and platform errors. So I've been installing packages to that end. I will submit tickets as I encounter errors, and pull requests as I have the time. I intend tickets as a means of documentation, but if you would prefer pull requests without tickets, I can do things that way. I'll plan to add installation proof to future PRs. GTK takes a while to compile, so I just sent it off as soon as the configure step was successful.

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

that all sounds great, we're glad to have you along!

There is a small but dedicated group of Tiger / Leopard / PPC enthusiasts who find a home in MacPorts.

The main group of MacPorts is not particularly interested in Tiger or Leopard (or PPC), but they are tolerant and agreeable to supporting such systems if the support does not overly confuse or render unsupportable the main focus on the current systems.

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

Resolution: fixed
Status: assignedclosed

In cc68a8221f22d4fe2c99cc23508681b776714c6d/macports-ports (master):

gtk3: Disable dependency tracking on Tiger

Closes #63151

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

All sounds fine. Since you're here – right now I'm attempting to install libgnomeui. This indirectly includes mozjs60, which fails due to issues outlined in #57032. It would be great to prune the dependency tree down so that mozjs is not needed for Gnome libraries.

Note: See TracTickets for help on using tickets.