| 1 |
On Fri, Feb 22, 2008 at 1:25 PM, Justin <justin@×××××××××.net> wrote: |
| 2 |
> Andrey Falko schrieb: |
| 3 |
> |
| 4 |
> > On Fri, Feb 22, 2008 at 3:56 AM, <justin@×××××××××.net> wrote: |
| 5 |
> > |
| 6 |
> >> Hi all! |
| 7 |
> >> |
| 8 |
> >> I have a little nasty problem. I am using a couple of fortran progs and not |
| 9 |
> >> all are happy with ifort but some benefit allot of its use. As I am lazy |
| 10 |
> >> and dont want to change my make.conf all the time I provided the F77, FC |
| 11 |
> >> and FLAGS for those packages which support ifort through |
| 12 |
> >> /etc/portage/env/<categorie>/<package>. This worked for a long time, but |
| 13 |
> >> now some thing has changed and I dont know what. The variables are still |
| 14 |
> >> passed to the emerge but the F77 and FC isnt used by emake any more. See |
| 15 |
> >> following example: ifort is chosen by the fortran.eclass and configure uses |
| 16 |
> >> it as well. But in the make part only the ifort spezific FFLAGS are use |
| 17 |
> >> together with gfortran. |
| 18 |
> >> |
| 19 |
> >> |
| 20 |
> > What version of portage is this? emerge --info? It is possible that |
| 21 |
> > there might be a regression between portage versions. If you've |
| 22 |
> > updated portage recently, try downgrading by masking the current |
| 23 |
> > version in /etc/portage/package.mask. |
| 24 |
> > |
| 25 |
> I tryed this first. The second thing I tried was downgrading bash but |
| 26 |
> all that doesnt help. |
| 27 |
> |
| 28 |
You can try running emerge --debug, maybe that will hint the problem? |
| 29 |
> |
| 30 |
> > |
| 31 |
> >> >>> Emerging (1 of 1) sci-chemistry/shelx-20060317 to / |
| 32 |
> >> * shelx-20060317.tgz RMD160 SHA1 SHA256 size ;-) ... |
| 33 |
> >> [ ok ] |
| 34 |
> >> * checking ebuild checksums ;-) ... |
| 35 |
> >> [ ok ] |
| 36 |
> >> * checking auxfile checksums ;-) ... |
| 37 |
> >> [ ok ] |
| 38 |
> >> * checking miscfile checksums ;-) ... |
| 39 |
> >> [ ok ] |
| 40 |
> >> * checking shelx-20060317.tgz ;-) ... |
| 41 |
> >> [ ok ] |
| 42 |
> >> * You need one of these Fortran Compilers: ifc gfortran |
| 43 |
> >> * Installed are: ifort gfortran |
| 44 |
> >> * Using ifort |
| 45 |
> >> >>> Unpacking source... |
| 46 |
> >> >>> Unpacking shelx-20060317.tgz to |
| 47 |
> >> /var/tmp/portage/sci-chemistry/shelx-20060317/work |
| 48 |
> >> * Applying 20060317-autotool.patch ... |
| 49 |
> >> [ ok ] |
| 50 |
> >> * Applying 20060317-gfortran.patch ... |
| 51 |
> >> [ ok ] |
| 52 |
> >> * Running eautoreconf in |
| 53 |
> >> '/var/tmp/portage/sci-chemistry/shelx-20060317/work/unix' ... |
| 54 |
> >> * Running aclocal ... |
| 55 |
> >> [ ok ] |
| 56 |
> >> * Running autoconf ... |
| 57 |
> >> [ ok ] |
| 58 |
> >> * Running automake --add-missing --copy --foreign ... |
| 59 |
> >> [ ok ] |
| 60 |
> >> >>> Source unpacked. |
| 61 |
> >> >>> Compiling source in |
| 62 |
> >> /var/tmp/portage/sci-chemistry/shelx-20060317/work/unix ... |
| 63 |
> >> ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man |
| 64 |
> >> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc |
| 65 |
> >> --localstatedir=/var/lib FC=ifort --build=i686-pc-linux-gnu |
| 66 |
> >> checking for a BSD-compatible install... /usr/bin/install -c |
| 67 |
> >> checking whether build environment is sane... yes |
| 68 |
> >> checking for a thread-safe mkdir -p... /bin/mkdir -p |
| 69 |
> >> checking for gawk... gawk |
| 70 |
> >> checking whether make sets $(MAKE)... yes |
| 71 |
> >> checking for i686-pc-linux-gnu-gfortran... ifort |
| 72 |
> >> checking for Fortran compiler default output file name... a.out |
| 73 |
> >> checking whether the Fortran compiler works... yes |
| 74 |
> >> checking whether we are cross compiling... no |
| 75 |
> >> checking for suffix of executables... |
| 76 |
> >> checking for suffix of object files... o |
| 77 |
> >> checking whether we are using the GNU Fortran compiler... no |
| 78 |
> >> checking whether ifort accepts -g... yes |
| 79 |
> >> checking for i686-pc-linux-gnu-g77... no |
| 80 |
> >> checking for i686-pc-linux-gnu-xlf... no |
| 81 |
> >> checking for i686-pc-linux-gnu-f77... no |
| 82 |
> >> checking for i686-pc-linux-gnu-frt... no |
| 83 |
> >> checking for i686-pc-linux-gnu-pgf77... no |
| 84 |
> >> checking for i686-pc-linux-gnu-cf77... no |
| 85 |
> >> checking for i686-pc-linux-gnu-fort77... no |
| 86 |
> >> checking for i686-pc-linux-gnu-fl32... no |
| 87 |
> >> checking for i686-pc-linux-gnu-af77... no |
| 88 |
> >> checking for i686-pc-linux-gnu-xlf90... no |
| 89 |
> >> checking for i686-pc-linux-gnu-f90... no |
| 90 |
> >> checking for i686-pc-linux-gnu-pgf90... no |
| 91 |
> >> checking for i686-pc-linux-gnu-pghpf... no |
| 92 |
> >> checking for i686-pc-linux-gnu-epcf90... no |
| 93 |
> >> checking for i686-pc-linux-gnu-gfortran... i686-pc-linux-gnu-gfortran |
| 94 |
> >> checking whether we are using the GNU Fortran 77 compiler... no |
| 95 |
> >> checking whether i686-pc-linux-gnu-gfortran accepts -g... yes |
| 96 |
> >> configure: creating ./config.status |
| 97 |
> >> config.status: creating Makefile |
| 98 |
> >> i686-pc-linux-gnu-gfortran -O3 -march=prescott -openmp -parallel -c -o |
| 99 |
> >> ciftab.o ciftab.f |
| 100 |
> >> i686-pc-linux-gnu-gfortran: unrecognized option '-parallel' |
| 101 |
> >> i686-pc-linux-gnu-gfortran -O3 -march=prescott -openmp -parallel -c -o |
| 102 |
> >> shelxa.o shelxa.f |
| 103 |
> >> i686-pc-linux-gnu-gfortran -O3 -march=prescott -openmp -parallel -c -o |
| 104 |
> >> shelxc.o shelxc.f |
| 105 |
> >> i686-pc-linux-gnu-gfortran: unrecognized option '-parallel' |
| 106 |
> >> i686-pc-linux-gnu-gfortran -O3 -march=prescott -openmp -parallel -c -o |
| 107 |
> >> shelxd.o shelxd.f |
| 108 |
> >> i686-pc-linux-gnu-gfortran: unrecognized option '-parallel' |
| 109 |
> >> |
| 110 |
> >> |
| 111 |
> >> -- |
| 112 |
> >> gentoo-user@l.g.o mailing list |
| 113 |
> >> |
| 114 |
> >> |
| 115 |
> >> |
| 116 |
> -- |
| 117 |
> |
| 118 |
> |
| 119 |
> gentoo-user@l.g.o mailing list |
| 120 |
> |
| 121 |
> |
| 122 |
-- |
| 123 |
gentoo-user@l.g.o mailing list |
Archives