On Fri, Feb 22, 2008 at 1:25 PM, Justin <[EMAIL PROTECTED]> wrote:
> Andrey Falko schrieb:
>
> > On Fri, Feb 22, 2008 at 3:56 AM,  <[EMAIL PROTECTED]> wrote:
>  >
>  >>  Hi all!
>  >>
>  >>  I have a little nasty problem. I am using a couple of fortran progs and 
> not
>  >>  all are happy with ifort but some benefit allot of its use. As I am lazy
>  >>  and dont want to change my make.conf all the time I provided the F77, FC
>  >>  and FLAGS for those packages which support ifort through
>  >>  /etc/portage/env/<categorie>/<package>. This worked for a long time, but
>  >>  now some thing has changed and I dont know what. The variables are still
>  >>  passed to the emerge but the F77 and FC isnt used by emake any more. See
>  >>  following example: ifort is chosen by the fortran.eclass and configure 
> uses
>  >>  it as well. But in the make part only the ifort spezific FFLAGS are use
>  >>  together with gfortran.
>  >>
>  >>
>  > What version of portage is this? emerge --info? It is possible that
>  > there might be a regression between portage versions. If you've
>  > updated portage recently, try downgrading by masking the current
>  > version in /etc/portage/package.mask.
>  >
>  I tryed this first. The second thing I tried was downgrading bash but
>  all that doesnt help.
>
You can try running emerge --debug, maybe that will hint the problem?
>
> >
>  >>  >>> Emerging (1 of 1) sci-chemistry/shelx-20060317 to /
>  >>   * shelx-20060317.tgz RMD160 SHA1 SHA256 size ;-) ...
>  >>                                                       [ ok ]
>  >>   * checking ebuild checksums ;-) ...
>  >>                                                       [ ok ]
>  >>   * checking auxfile checksums ;-) ...
>  >>                                                       [ ok ]
>  >>   * checking miscfile checksums ;-) ...
>  >>                                                       [ ok ]
>  >>   * checking shelx-20060317.tgz ;-) ...
>  >>                                                       [ ok ]
>  >>   * You need one of these Fortran Compilers: ifc gfortran
>  >>   * Installed are:  ifort gfortran
>  >>   * Using ifort
>  >>  >>> Unpacking source...
>  >>  >>> Unpacking shelx-20060317.tgz to
>  >>  /var/tmp/portage/sci-chemistry/shelx-20060317/work
>  >>   * Applying 20060317-autotool.patch ...
>  >>                                                       [ ok ]
>  >>   * Applying 20060317-gfortran.patch ...
>  >>                                                       [ ok ]
>  >>   * Running eautoreconf in
>  >>  '/var/tmp/portage/sci-chemistry/shelx-20060317/work/unix' ...
>  >>   * Running aclocal ...
>  >>                                                       [ ok ]
>  >>   * Running autoconf ...
>  >>                                                       [ ok ]
>  >>   * Running automake --add-missing --copy --foreign ...
>  >>                                                       [ ok ]
>  >>  >>> Source unpacked.
>  >>  >>> Compiling source in
>  >>  /var/tmp/portage/sci-chemistry/shelx-20060317/work/unix ...
>  >>  ./configure --prefix=/usr --host=i686-pc-linux-gnu 
> --mandir=/usr/share/man
>  >>  --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
>  >>  --localstatedir=/var/lib FC=ifort --build=i686-pc-linux-gnu
>  >>  checking for a BSD-compatible install... /usr/bin/install -c
>  >>  checking whether build environment is sane... yes
>  >>  checking for a thread-safe mkdir -p... /bin/mkdir -p
>  >>  checking for gawk... gawk
>  >>  checking whether make sets $(MAKE)... yes
>  >>  checking for i686-pc-linux-gnu-gfortran... ifort
>  >>  checking for Fortran compiler default output file name... a.out
>  >>  checking whether the Fortran compiler works... yes
>  >>  checking whether we are cross compiling... no
>  >>  checking for suffix of executables...
>  >>  checking for suffix of object files... o
>  >>  checking whether we are using the GNU Fortran compiler... no
>  >>  checking whether ifort accepts -g... yes
>  >>  checking for i686-pc-linux-gnu-g77... no
>  >>  checking for i686-pc-linux-gnu-xlf... no
>  >>  checking for i686-pc-linux-gnu-f77... no
>  >>  checking for i686-pc-linux-gnu-frt... no
>  >>  checking for i686-pc-linux-gnu-pgf77... no
>  >>  checking for i686-pc-linux-gnu-cf77... no
>  >>  checking for i686-pc-linux-gnu-fort77... no
>  >>  checking for i686-pc-linux-gnu-fl32... no
>  >>  checking for i686-pc-linux-gnu-af77... no
>  >>  checking for i686-pc-linux-gnu-xlf90... no
>  >>  checking for i686-pc-linux-gnu-f90... no
>  >>  checking for i686-pc-linux-gnu-pgf90... no
>  >>  checking for i686-pc-linux-gnu-pghpf... no
>  >>  checking for i686-pc-linux-gnu-epcf90... no
>  >>  checking for i686-pc-linux-gnu-gfortran... i686-pc-linux-gnu-gfortran
>  >>  checking whether we are using the GNU Fortran 77 compiler... no
>  >>  checking whether i686-pc-linux-gnu-gfortran accepts -g... yes
>  >>  configure: creating ./config.status
>  >>  config.status: creating Makefile
>  >>  i686-pc-linux-gnu-gfortran  -O3 -march=prescott -openmp -parallel -c -o
>  >>  ciftab.o ciftab.f
>  >>  i686-pc-linux-gnu-gfortran: unrecognized option '-parallel'
>  >>  i686-pc-linux-gnu-gfortran  -O3 -march=prescott -openmp -parallel -c -o
>  >>  shelxa.o shelxa.f
>  >>  i686-pc-linux-gnu-gfortran  -O3 -march=prescott -openmp -parallel -c -o
>  >>  shelxc.o shelxc.f
>  >>  i686-pc-linux-gnu-gfortran: unrecognized option '-parallel'
>  >>  i686-pc-linux-gnu-gfortran  -O3 -march=prescott -openmp -parallel -c -o
>  >>  shelxd.o shelxd.f
>  >>  i686-pc-linux-gnu-gfortran: unrecognized option '-parallel'
>  >>
>  >>
>  >>  --
>  >>  gentoo-user@lists.gentoo.org mailing list
>  >>
>  >>
>  >>
>  --
>
>
> gentoo-user@lists.gentoo.org mailing list
>
>
-- 
gentoo-user@lists.gentoo.org mailing list

Reply via email to