Jason,
On Fri, May 21, 2010 at 5:51 AM, Jason Swails <jason.swails.gmail.com> wrote:
> On Fri, May 21, 2010 at 1:53 AM, Mengjuei Hsieh <mjhsieh.gmail.com> wrote:
>> 2010/5/20 Jason Swails <jason.swails.gmail.com>:
>> > P.S. perhaps another approach to building Amber10/AmberTools1.2 on Mac OS
>> > X 10.6 is to boot into the 64-bit kernel to perform the install (do this by
>> > holding the numbers 6 and 4 down when the computer is first turned on).
>> > That way the configure script will recognize a 64-bit kernel (uname -m returns
>> > x86_64 instead of i386)
>>
>> That would be a no-no for laptop and desktop users since using 64bit
>> only mode will disable some certain 3rd party drivers and thus make
>> life less comfortable. (Having that been said, I do recommend that for
>> people who have dedicated mac computing workstations.)
>
> Even if they boot back into 32-bit after they're done? I've done that on
> several occasions on my laptop, since any binary compiled in 64-bit mode can
> still run in the 32-bit kernel. I've done that with other packages that put
> in spurious -m32 flags everywhere and it worked just fine... Also, don't
> dedicated workstations do that by default? I'm pretty sure Xserves do, but
> not sure about Mac Pros.
That would be okay if users boot back to default 32/64 hybrid kernel.
I was just not comfortable telling users with unknown OS knowledge to
do so. I think 64-only mode is only default on sever version of OS if
I recall it correctly.
Sincerely,
--
Mengjuei
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Fri May 21 2010 - 11:00:07 PDT
