When doing a catalyst run with a 2-day old snapshot, I've run across several errors during my builds. All three of these packages fail on the same section of code: # move shared libs to / dodir /$(get_libdir) mv "${D}"/usr/$(get_libdir)/*.so* "${D}"/$(get_libdir)/ || die "could not move shared" In all three cases, the files in image are under /usr/lib, not /usr/lib64, so the move fails. Changing the move to: mv "${D}"/usr/lib*/*.so* "${D}"/$(get_libdir)/ || die "could not move shared" ...causes the packages to complete successfully. Is this the "proper" solution? Well, no. The proper one would be to determine why things are getting put into /usr/lib rather than /usr/lib64 and fixing that issue and sending it upstream, but I'm cool with the one-line change in the ebuilds for the time being, since we're on such a short time-table.
Ugh... OK. This is definitely a problem elsewhere. It seems to be something with calling get_libdir. I've checked the profile and even switched to another profile and it is still doing the same thing. It's either something with econf or something else that I haven't discovered yet. Sorry for all the confusion and trouble.