On Jan 16, 2013, at 22:06, Jeremy Huddleston Sequoia wrote: > We may need to figure out a way to deal with this ABI compatibility issue in > base … is there currently a way to query what configure.compiler was for > another installed port?
I don't think that information is recorded anywhere; I don't think it's in the binary packages, or in the registry. I once suggested we should include that in the name of the package at least, but it didn't matter in most cases, and the few where it did were bugs that were (or should be) fixed in other ways. There's a lot of information available at install time that's not recorded anywhere that might be useful later. Compiler used, Xcode version, OS X version and build number, number of CPUs, amount of memory, number of build jobs... We could record information like this, and provide a command to easily retrieve all the information, and ask users to include it with bug reports. But it would be a bit of work to implement, for a hypothetical future benefit. :/ _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
