Done, and I am OK now with the compilers.
Ambertools configure is OK now, but still problems with install:
Starting installation of AmberTools, version 1.4 serial at Mon May 17 13:31:48 EDT 2010.
(cd ucpp-1.3 && make install )
gcc -o ucpp mem.o nhash.o cpp.o lexer.o assert.o macro.o eval.o
mv ucpp /usr/local/amber11/bin
(cd byacc && make install )
mv yacc /usr/local/amber11/bin
(cd arpack && make install );
ar rv arpack.a ivout.o dvout.o dgetv0.o dlaqrb.o dnaitr.o dnapps.o dnaup2.o dnaupd.o dnconv.o dneigh.o dmout.o dneupd.o dngets.o dsaitr.o dsapps.o dsaup2.o dsaupd.o dsconv.o dseigt.o dsesrt.o dseupd.o dsgets.o dsortc.o dsortr.o dstatn.o dstats.o dstqrb.o dsarpack.o wallclock.o
ar: arpack.a is a fat file (use libtool(1) or lipo(1) and ar(1) on it)
ar: arpack.a: Inappropriate file type or format
make[1]: *** [arpack.a] Error 1
make: *** [serial] Error 2
On May 17, 2010, at 12:44 PM, Mengjuei Hsieh wrote:
> On Mon, May 17, 2010 at 8:57 AM, erik zuiderweg <zuiderwe.umich.edu> wrote:
>
>> the gcc -v command gives me the wrong compiler:
>>
>
> This can be easily solved by tweaking your path environment variable.
>
> export PATH=/usr/local/bin:$PATH
>
> And write that command into your $HOME/.bashrc . By doing this, your shell
> will make use of /usr/local/bin/gcc first instead of /usr/bin/gcc .
>
> Although I would argue that the command should be put earlier than the
> macports setting in your .bashrc, but since you said your macports
> installation doesn't give you an updated .bashrc (or .profile ?), so I'd say
> just forget about it :-).
>
> All the best,
> --
> Mengjuei
> _______________________________________________
> AMBER mailing list
> AMBER.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber
>
>
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Mon May 17 2010 - 11:00:06 PDT
