Re: Status of NCL under MacOS 10.6 (64-bit)

You can run "file" on any one of the *.o or executable files, and it
will say something like this if it is 32-bit:

file error.o
error.o: Mach-O object i386

and something like this if it is 64-bit:

sheridan[362] file error.o
error.o: Mach-O 64-bit object x86_64

This doesn't seem to work for the library archive, the "libxxxx.a" file.

--Mary

On Nov 13, 2009, at 1:26 AM, Sourish Basu wrote:

>
>> I see that Sourish posted a response. The question I have about using
>> gcc 4.2 is whether you get a 64-bit compile by default. I think this
>> is the heart of the issue: HDF4 is not expecting the MacOS build
>> to be
>> on a 64-bit system, so it tries to treat the configuration as if it's
>> a 32-bit one. This causes conflicting information during the
>> "configure" phase.
>>
>> I believe that you could do a build from source if you went into
>> 32-bit mode, by forcing the "-m32" option. However this defeats the
>> purpose of getting a 64-bit system.
>
> I used gcc-4.4.1 to build HDF4. That version (at least the one
> installed
> by fink) does not accept the "-arch" flag. It does accept the
> "-m32/-m64" flag, but I didn't use it. So I'm not sure if the HDF
> library I have is 32 bit or 64 bit. Is there any way of checking?
>
> -Sourish
> _______________________________________________
> ncl-install mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-install

_______________________________________________
ncl-install mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-install
Received on Fri Nov 13 09:42:08 2009