gtk2 fails to build on lion: `/opt/local/lib/libfreetype.la' is not a valid libtool archive

[hofione@…]

after

sudo port sync
sudo port selfupdate
sudo port upgrade outdated

gtk2 fails to build

[hofione@…]

Cc Me!

[hofione@…]

port info gtk2
gtk2 @2.24.5 (gnome, x11)
Variants:             no_x11, quartz, universal, [+]x11

Description:          GTK+ is a highly usable, feature rich toolkit for creating graphical user interfaces which boasts cross platform compatibility and an easy to use API. GTK+ it is written in C, but has bindings to many
                      other popular programming languages such as C++, Python and C# among others.
Homepage:             http://www.gtk.org/

Build Dependencies:   pkgconfig, perl5
Library Dependencies: atk, pango, gdk-pixbuf2, xorg-libXi, xorg-libXrandr, xorg-libXcursor, xorg-libXinerama, xorg-libXdamage, xorg-libXcomposite, xorg-libXfixes
Runtime Dependencies: shared-mime-info
Platforms:            darwin
License:              LGPL-2+
Maintainers:          nomaintainer@macports.org

[drkp (Dan Ports)]

This isn't a complete log; can you run a sudo port clean gtk2 then retry upgrading, and post the resulting log if it fails?

(and the ticket reporter is automatically cc'd, you don't need to cc yourself)

[ryandesign (Ryan Carsten Schmidt)]

I see:

libtool: link: `/opt/local/lib/libfreetype.la' is not a valid libtool archive

So, why isn't it a valid libtool archive? What's in it? What happens if you rebuild the freetype port?

[drkp (Dan Ports)]

jmr saw something similar today too, but with a different .la file.

[ryandesign (Ryan Carsten Schmidt)]

I've fielded at least one instance of this before too, in which the .la file and several other files were the right size but composed entirely of null bytes: #30136

[jmroot (Joshua Root)]

And today it built fine. I have no explanation.

[hofione@…]

Just like for me today Strange

[drkp (Dan Ports)]

I just hit this one myself, but I have no idea why. The .la files it's complaining about (two of them, this time) look perfectly fine, and the libtool command works when re-executed.

[ryandesign (Ryan Carsten Schmidt)]

If you are certain you are receiving the same error ('foo.la' is not a valid libtool archive), then can you please attach the libtool archive in question so I can take a look at it? I don't see how you could have gotten that message if retrying worked if and the libtool archive is fine.

[jmroot (Joshua Root)]

Same way I did, of course. Which is a complete mystery. I checked the .la file when the build failed and it was fine.

[drkp (Dan Ports)]

Sure, here are the libtool archives (I made a copy immediately after I saw the error, so they definitely haven't been modified in the interim). I don't have a build log handy, but the gtk build stopped when one libtool invocation errored out with not a valid libtool archive for both of these .la files, and the same command worked again when retried.

[ryandesign (Ryan Carsten Schmidt)]

Indeed. Your libXau.la is identical to mine, and your libpangocairo-1.0.la is practically identical (-lbz2 occurs at a slightly different position in yours but that wouldn't matter). I can only conclude that Lion and/or its Xcode are strange.

[ryandesign (Ryan Carsten Schmidt)]

Same problem was mentioned in #30322, in which ImageMagick couldn't be built because of allegedly invalid libICE.la and libXt.la archives, but which are identical to the ones on my system.

[drkp (Dan Ports)]

Yes, I've noticed this when building gtk2 and ImageMagick. I haven't run into it for any other ports (though obviously that doesn't mean there aren't any). Still no idea what's going on, though.

[qhuys@…]

So I had the same problem. The log file was:

:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_gtk2/gtk2/work/gtk+-2.24.6" && /usr/bin/make -j4 -w all " returned error 2
:error:build Target org.macports.build returned: shell command failed (see log for details)

So being new and naive, I cd'd into /opt/local.../work/gtk+-2.24.6 and simply typed:

make -j4 -w all

which ran happily without errors.

Then, I ran

sudo port install gtk2

again, and this time it happily continued. Mind you... I'm not sure whether I might have broken something?

[qhuys@…]

Cc Me!

[macports@…]

I tried running the command:

sudo port upgrade outdated

again. Same error. Then I ran the command again, and it worked! I think we might be seeing a Makefile dependency issue, where "-j" is causing one process to start linking before another process has finished creating the link archive.

[ryandesign (Ryan Carsten Schmidt)]

But if it's saying /opt/local/lib/libfreetype.la is not a valid archive... that file has already been successfully built and installed by the freetype port. You're past that and on to another port.

[ak.ml@…]

Cc Me!

[jmroot (Joshua Root)]

I haven't seen this with any gtk2 update since. If someone else has, feel free to reopen.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #36078.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #38130.

[cooljeanius (Eric Gallager)]

Cc Me!

[Ionic (Mihai Moldovan)]

FYI: I just did. But it does really look like a race condition... Probably too complex to fix, when re-running the upgrade works fine.

[mojca (Mojca Miklavec)]

Hit today by

libtool:   error: '/opt/local/lib/libxcb.la' is not a valid libtool archive

when upgrading gtk3. Reruning the build "fixed" the problem.

[kencu (Ken)]

a different port, a different archive, same error, on 10.7, installing pulseaudio:

libtool:   error: '/opt/local/lib/libX11.la' is not a valid libtool archive

again, rerunning the build (without cleaning) "fixed" the problem as well. Race condition sounds likely to me as well.