Thanks for the replies! Do (Mach-O?) binaries encode which extensions to the x86 set they make use of?
Can one expect a warning when loading an incompatible binary, or will it run with an undefined behavior? (I know this is a bit out-of-topic, but I think it might interest other readers of this thread.) Best wishes, Renaud. On 18 Aug 2010, at 18:59, Jean-François Mertens wrote: > > On 18 Aug 2010, at 18:42, David R. Morrison wrote: > >> There is one exception to this that I'm aware of: the gmp package >> does cpu-specific optimization at compile time. But the cpu- >> specific optimizations tend to be upward-compatible, so if you >> compile this package on your least-capable machine, it should run on >> the others. > > atlas and its deps are another exception, the whole purpose > of the pkg being to tune things to the specific CPU at hand. > And I've probably noticed a couple of other exceptions, > from glancing when they were building _ not sure this was > more than mere tuning... Anyway, there should be very few. > > JF Mertens > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Fink-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fink-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
