From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0E777138247 for ; Sun, 12 Jan 2014 10:08:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2C95FE0C9D; Sun, 12 Jan 2014 10:08:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1D364E0B3F for ; Sun, 12 Jan 2014 10:08:28 +0000 (UTC) Received: from pomiot.lan (77-254-165-29.adsl.inetia.pl [77.254.165.29]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 44A1B33F6B0; Sun, 12 Jan 2014 10:08:26 +0000 (UTC) Date: Sun, 12 Jan 2014 11:08:18 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: dirtyepic@gentoo.org Subject: Re: [gentoo-dev] Re: Default USE changes for fortran and mudflap? Message-ID: <20140112110818.116e4c17@pomiot.lan> In-Reply-To: <20140112035053.56019304@caribou.gateway.pace.com> References: <20140112015347.5baf1bc0@caribou.gateway.pace.com> <20140112092420.6222fb44@pomiot.lan> <20140112035053.56019304@caribou.gateway.pace.com> Organization: Gentoo X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/FgDFSeEF2zrMZaphPDBCOAe"; protocol="application/pgp-signature" X-Archives-Salt: f5d31770-b947-46e4-8d6e-3eafc0cc762a X-Archives-Hash: ecf89bf76de0e6f23e8febad9cc784f2 --Sig_/FgDFSeEF2zrMZaphPDBCOAe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dnia 2014-01-12, o godz. 03:50:53 Ryan Hill napisa=C5=82(a): > On Sun, 12 Jan 2014 09:24:20 +0100 > Micha=C5=82 G=C3=B3rny wrote: >=20 > > Dnia 2014-01-12, o godz. 01:53:47 > > Ryan Hill napisa=C5=82(a): > >=20 > > > fortran: > > > Do we want to keep enabling fortran by default? The majority of user= s will > > > never get the urge to install a fortran package, and the fortran ecla= ss > > > handles those that do. I think it should be treated as all the other > > > optional languages and disabled by default, but I'd like to know if t= here > > > are other opinions. > >=20 > > Well, I'd say we should work on making 'other languages' buildable > > without rebuilding the whole giant gcc stack. Especially that > > the stacked build makes it impossible to use distcc at least partially. >=20 > Bootstrapping makes distcc impossible, and you can't bootstrap these days > without building C and C++. Even if you're not bootstrapping, the back a= nd > middle ends are shared. You have to build them to build the front-ends. = Maybe > you could cut out a couple of the target libraries, so you're really not = gaining > much. Yes but if C & C++ was installed after it is built, distcc/ccache could be then used to build the Fortran & GCJ & so on. Of course, there's another matter of matching gcc versions between hosts but that's just another problem that needs addressing elsewhere. Maybe I wouldn't gain much of Fortran. But if I recall correctly, gcj has a fair bit of C++ code to build. But after all, it's all purely theoretical. Unless we're going to patch gcc build system to make it more friendly. > Anyways, assuming we can't split out fortran, would you be for or against > enabling it by default? I'm good either way. Considering that it saves you like 5M? I'd rather keep it enabled. 5M won't save the day, while waiting extra 2 hours for gcc rebuild because some package needs Fortran is irritating. And I say two hours because, say, I had to enable USE=3Dgcj earlier and now I have to rebuild that huge thing. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/FgDFSeEF2zrMZaphPDBCOAe Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAEBCgBmBQJS0mmSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOC6AQAMaYgkJaloxde30yGheFgtNR /ow5Htjws+jcKn1WGg6+OpzAz6e2CoQ46HGQMkzZ9XGpfcIVUmsheZDmcCxXxb9q g1mSbMMQ531I2ae90CZg/Xz4bBgXRizcZevh/uT97YujjpSefvtEfnMC6zkVhk/n Q1dpFxtqzlc00QbyNqPejtm0y9gh0sjwlh2ALhLTo7Ua4RQHEy/cxKJQ0KRlIHke ldJLW4hKgWLwAAm/m+e89e7IC/tyilyPqweQ1zgvVx+tpxgougrTau1y4tgqcpIt yi8ZpoeL2rUXITIyAPzMjyS6oU0oCxEKUGyexs3sk3rlpTIoQ6PpKllXSDN0pzJS pRgmSKgsaxUSEYx26wkxXP4ssxpHqBkEaFqRUA4x9NEXSoFuQO6zf6IMprhs9DGB 9WRPbPnL96zSCZ+uh/f775iA2GgND4MViyLpWPpxKdv3b3sf1Nuh0ubp8cEZBZHC daY2t07iI9AhmpcvmRaT/dB/GsWr2ZwCW58SR88SN+1kho8wOAVrRXOu5MmqCvf4 a8HbFHS9sodX9uY2WI1NqUP599PsZujqjuXCaZUSBzn3ah4xHXJCem/leMAWAt5m yhhrMJwdVUis8pPJZJRulpmcBGTob+N5YVSGWiNrGRLQ8wdVQkJyNpc+rllL4MMr Ly+3BPVCsj0D+eT9JKnB =AXa4 -----END PGP SIGNATURE----- --Sig_/FgDFSeEF2zrMZaphPDBCOAe--