pkgconfig @0.29.1: gmessages.c:1077:3: error: data argument not used by format string [-Wformat-extra-args]

[cer54 (Carl Edward Rasmussen)]

sudo port clean pkgconfig
--->  Cleaning pkgconfig
sudo port install pkgconfig
--->  Computing dependencies for pkgconfig
--->  Fetching archive for pkgconfig
--->  Attempting to fetch pkgconfig-0.29.1_0.darwin_11.x86_64.tbz2 from https://packages.macports.org/pkgconfig
--->  Attempting to fetch pkgconfig-0.29.1_0.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/pkgconfig
--->  Attempting to fetch pkgconfig-0.29.1_0.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/pkgconfig
--->  Fetching distfiles for pkgconfig
--->  Verifying checksums for pkgconfig
--->  Extracting pkgconfig
--->  Applying patches to pkgconfig
--->  Configuring pkgconfig
--->  Building pkgconfig
Error: org.macports.build for port pkgconfig returned: command execution failed
Please see the log file for port pkgconfig for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_pkgconfig/pkgconfig/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port pkgconfig failed

[cer54 (Carl Edward Rasmussen)]

pkgconfig/main.log

[mf2k (Frank Schima)]

In the future, please Cc the port maintainers (port info --maintainers pkgconfig), if any.

[ryandesign (Ryan Carsten Schmidt)]

I see you're on Lion. What version of Xcode and clang do you have?

I see one proposed patch for this issue: ​https://mail-index.netbsd.org/pkgsrc-bugs/2013/10/16/msg052707.html Perhaps it only affects older versions of clang, such as we would find on Lion.

[cer54 (Carl Edward Rasmussen)]

Replying to ryandesign@…:

I see you're on Lion. What version of Xcode and clang do you have?

My Xcode version is Xcode 4.6.3 and clang is Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn).

I see one proposed patch for this issue: ​https://mail-index.netbsd.org/pkgsrc-bugs/2013/10/16/msg052707.html Perhaps it only affects older versions of clang, such as we would find on Lion.

Yes, I tried the above patch and that fixes the problem.

Thanks!

[ryandesign (Ryan Carsten Schmidt)]

Replying to cer54@…:

Replying to ryandesign@…:

I see you're on Lion. What version of Xcode and clang do you have?

My Xcode version is Xcode 4.6.3 and clang is Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn).

Xcode 4.6.3 is indeed the latest version you can use on Lion, however Apple clang version 2.1 a.k.a clang-163.7.1 does not correspond to that version of Xcode; it corresponds to Xcode 4.1. Please upgrade your clang by installing "Command Line Tools (OS X Lion) for Xcode - April 2013" which you can get at the ​Apple Developer Downloads page after logging in, or via the Downloads section of the Xcode application's Preferences window.

I see one proposed patch for this issue: ​https://mail-index.netbsd.org/pkgsrc-bugs/2013/10/16/msg052707.html Perhaps it only affects older versions of clang, such as we would find on Lion.

Yes, I tried the above patch and that fixes the problem.

Thanks for verifying that. It looks like even the current version of glib does not include such a change. However current compilers merely consider this condition a warning, not an error as your old version of clang does. I will try to find out if this problem was ever reported to the developers of glib, and if so, what their response was.

[cer54 (Carl Edward Rasmussen)]

Replying to ryandesign@…:

My Xcode version is Xcode 4.6.3 and clang is Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn).

Xcode 4.6.3 is indeed the latest version you can use on Lion, however Apple clang version 2.1 a.k.a clang-163.7.1 does not correspond to that version of Xcode; it corresponds to Xcode 4.1. Please upgrade your clang by installing "Command Line Tools (OS X Lion) for Xcode - April 2013" which you can get at the ​Apple Developer Downloads page after logging in, or via the Downloads section of the Xcode application's Preferences window.

Thanks for the precise instructions. I upgraded to the newer command line tools, my clang version is now Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn). I then uninstalled the patched version of pkgconfig, and installed it again from fresh, this time without a hitch. Thanks for your help, and sorry for being unaware of the too old command line tools problem.

I see one proposed patch for this issue: ​https://mail-index.netbsd.org/pkgsrc-bugs/2013/10/16/msg052707.html Perhaps it only affects older versions of clang, such as we would find on Lion.

Yes, I tried the above patch and that fixes the problem.

Thanks for verifying that. It looks like even the current version of glib does not include such a change. However current compilers merely consider this condition a warning, not an error as your old version of clang does. I will try to find out if this problem was ever reported to the developers of glib, and if so, what their response was.

[ryandesign (Ryan Carsten Schmidt)]

Replying to cer54@…:

Thanks for the precise instructions. I upgraded to the newer command line tools, my clang version is now Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn). I then uninstalled the patched version of pkgconfig, and installed it again from fresh, this time without a hitch. Thanks for your help, and sorry for being unaware of the too old command line tools problem.

Thanks for confirming that. And don't worry, it happens a lot. It's Apple's fault for decoupling Xcode from the command line tools in Lion; in Snow Leopard and earlier they were part of a single installer so they couldn't get out of sync. And Apple fixed it in later versions of OS X by making both Xcode and the command line tools updatable via the App Store's software update.

[mojca (Mojca Miklavec)]

Ryan, may this ticket be closed?

[ryandesign (Ryan Carsten Schmidt)]

Rereading through the previous notes, I don't see anything that indicates I fixed the problem, so I would not close the ticket.

[kencu (Ken)]

As a datapoint, pkgconfig 0.29.2 builds successfully on all buildbots, including 10.7.

<​http://packages.macports.org/pkgconfig/>

[ryandesign (Ryan Carsten Schmidt)]

Replying to kencu:

As a datapoint, pkgconfig 0.29.2 builds successfully on all buildbots, including 10.7.

Right, and so did 0.29.1, because the buildbot workers have up to date compilers. The user who reported this ticket did not. The ticket is open until we decide how we should fix the problem for older compilers.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

Replying to cer54@…:

Replying to ryandesign@…:

I see one proposed patch for this issue: ​https://mail-index.netbsd.org/pkgsrc-bugs/2013/10/16/msg052707.html Perhaps it only affects older versions of clang, such as we would find on Lion.

Yes, I tried the above patch and that fixes the problem.

Thanks for verifying that. It looks like even the current version of glib does not include such a change. However current compilers merely consider this condition a warning, not an error as your old version of clang does. I will try to find out if this problem was ever reported to the developers of glib, and if so, what their response was.

It was ​reported to the developers and ​fixed in 2014. glib2 2.52.3 and glib2-devel 2.53.5 in MacPorts today already contain the fix. pkgconfig 0.29.2 doesn't, so I'll backport it.

[ryandesign (Ryan Carsten Schmidt)]

In eeded4006ac17609eed84113d3765f6c98bb14bc/macports-ports:

pkgconfig: Fix build with older clang compilers

Closes: #51312