On 2010-12-03 13:34 , Ryan Schmidt wrote: > > On Dec 2, 2010, at 23:01, Jeremy Lavergne wrote: > >> I have a package that is on the path of being noarch, but `file` claims that >> the produced .mo files are a specific endian. Are .mo files >> architecture-specific? > > .mo files are machine-specific (that's what the "m" in ".mo" stands for). So > I don't know what that means for MacPorts arch indication. If we're keeping > an eye toward eventual binary distribution, I guess this means we would need > separate .mo files for big- and little-endian machines. But that doesn't fit > neatly into MacPorts supported_arch setting.
Here is a link to a discussion on this topic on the Debian mailing list. It might shed some light on this issue. http://lists.debian.org/debian-devel/2009/01/msg00452.html Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
