Dear all,
It seems that RHEL4's gcc:
[bunny:0.05][mjw:src]$ gcc -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk
--host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)
does not like the -mtune=generic flag:
(current CVS checkout as of 2nd Nov 2009)
make -f Makefile_at
...snip...
make[1]: Entering directory
`/server-home/mjw/code/AMBER/amber11/src/carpack'
gcc -c -O3 -mtune=generic -mfpmath=sse -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -DBINTRAJ -o dgetv0.o dgetv0.c
dgetv0.c:1: error: bad value (generic) for -mtune= switch
make[1]: *** [dgetv0.o] Error 1
make[1]: Leaving directory `/server-home/mjw/code/AMBER/amber11/src/carpack'
make: *** [serial] Error 2
I think the cpu-types: "generic" and "native", are new as of gcc 4.2:
http://gcc.gnu.org/gcc-4.2/changes.html
(see the "New Targets and Target Specific Improvements" section)
I'm not sure on the best way to approach this problem since I think
these new flags are a good idea; maybe we need to determine if the
version of gcc is < 4.2 and then omit these flags?
regards,
Mark
--
Mark Williamson, Post Doc
Walker Molecular Dynamics Group
Room 395E
San Diego Supercomputer Center
9500 Gilman Drive
La Jolla, CA 92093-0505
Email: mjw at sdsc.edu
Office: 858-246-0827
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Mon Nov 02 2009 - 09:30:06 PST
