On Oct 12, 2011, at 13:39, Adam Dershowitz wrote: > So, this message has several points. > 1) Just a question about why these other libraries didn't get triggered to > rebuild, instead they just caused a build error? > > 2) I also wanted to let people know about this problem, and specifically, > for me, what I had to do in order to get it to build was: > > sudo port install jasper +universal > sudo port install libidl +universal > sudo port install libogg +universal > sudo port install libvorbis +universal > sudo port install libtheora +universal > > Then, the upgrade went fine (at least wine seems to be building fine > now....big one...takes a while).
This issue is now being tracked in https://trac.macports.org/ticket/31678 As we already discussed in the ticket you filed about the first such port you encountered, the behavior is consistent with the above ports having been installed prior to the release of MacPorts 1.9 on 2010-06-08. That's the first version that recorded architecture information in the registry; without that information, MacPorts doesn't know for what architectures the ports are installed, so it assumes they're installed for the correct architectures. Perhaps it might be better for MacPorts to assume the ports are installed for the wrong architectures and rebuild them, but it does not currently do that. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
