From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QaSJj-0003Wj-Q6 for garchives@archives.gentoo.org; Sat, 25 Jun 2011 12:50:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2584C1C105; Sat, 25 Jun 2011 12:46:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id EA67C1C105 for ; Sat, 25 Jun 2011 12:46:39 +0000 (UTC) Received: from JMac.local (ip-62-143-16-215.unitymediagroup.de [62.143.16.215]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jlec) by smtp.gentoo.org (Postfix) with ESMTPSA id 84D9E1B4017; Sat, 25 Jun 2011 12:46:38 +0000 (UTC) Message-ID: <4E05D8AB.10403@gentoo.org> Date: Sat, 25 Jun 2011 14:46:35 +0200 From: justin User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Do we have to build gcc with fortran now? References: <4E0167C4.9080100@gmail.com> <6517863.YlIiSIDa8W@pc> <4E04ECE0.9010109@gmail.com> <1466587.PvB50u6JAg@pc> <4E04F91C.8070902@gmail.com> <20110624232018.03c2a706@digimed.co.uk> <4E055608.4060800@gmail.com> <20110625124829.3b9e05a8@digimed.co.uk> <4E05CEDC.6060006@gmail.com> In-Reply-To: <4E05CEDC.6060006@gmail.com> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF1112F19FB71996E4008EC60" X-Archives-Salt: X-Archives-Hash: 3302cdcaa53e04ff422bf367e8773eb3 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF1112F19FB71996E4008EC60 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable >> >> justin >> =20 >=20 > That make sense? >=20 > Dale >=20 > :-) :-) >=20 Hi, as most of you do not like to have fortran enabled by default, we tried to find a way around. We created a virtual/fortran which should depend on a working fortran compiler so that only ebuilds which need fortran compiler will build it. With that situation it was possible to remove USE=3Dfortran from the profile (btw profiles cannot have a version bump and don't need it) so that most of you could drop the fortran support from gcc except a ebuild depends on it. However I wasn't aware that there is no hierarchy in the dependencies in an ebuild and portage will choose a solution w/o a USE change first. That is the reason why many of you saw that ifc should be installed, instead of gcc with USE=3Dfortran. That was the point where I added it back to the profile as a default enabled USE. The solution for the average user is leaving all default USE on. This will gcc build the fortran support and you will have no problem. (Libs and compiler are 1.5MB on my system) Or remove add -fortran to your make.conf and add sys-devel/gcc fortran to your /etc/portage/package.use. Trying to avoid any fortran at all is stupid, because as already mentioned many math operations are faster if programmed in fortran. Cheers justin --------------enigF1112F19FB71996E4008EC60 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4F2KsACgkQgAnW8HDreRblVwCfamm/79B69mKq73YdtML/NTLe bOsAn2HQAJBu4DXejsEQgQlom1hamH2d =gPaM -----END PGP SIGNATURE----- --------------enigF1112F19FB71996E4008EC60--