On Tue, 24 Oct 2006, Alasdair Allan wrote:
>
> Tim Jenness wrote:
>> Isn't this simply because you are trying to run the starlink software using
>> rosetta rather than using native intel? If you build the intel native
>> starlink version from CVS (Brad did it yesterday and it doesn't take very
>> long) won't the problems go away?
>
> No its because we have both Intel and PPC iMacs and the software (and other
> software) is running on both platforms, shared from the same NFS drives I
> think. I don't think compiling a Universal binary would help. Brad told me he
> wasn't sure how to do this when we were at ADASS anyway?
>
Confused. If G95 endianness is set to the Intel form then g95 won't be
able to read any of the .ifc files because they were written in ppc form.
Starlink software will break.
Building universal is trivial. Especially since you have intel and ppc
macs. Just build an intel native version and use lipo to attach the ppc
and intel binaries/libraries into a universal. That will work fine until
someone tries to build something and relies on a include file that got
modified during configure (I'm not sure if compiling the include files
will get round that on C).
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|