Re: [gentoo-dev] Default USE changes for fortran and mudflap?
On 01:53 Sun 12 Jan , Ryan Hill wrote: fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. It's essentially only used by the small minority of people installing sci-* packages so I'd be fine with that. Reasonable defaults FTW. -- Thanks, Donnie Donnie Berkholz Council Member / Sr. Developer, Gentoo Linux http://dberkholz.com Analyst, RedMonk http://redmonk.com/dberkholz/ pgpKSLofMizut.pgp Description: PGP signature
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
On Sunday 12 January 2014 02:53:47 Ryan Hill wrote: While I'm adding USE defaults to toolchain.eclass and moving them out of the profiles, I thought now would be a good time to review a couple default flag settings. mudflap: This is currently enabled by default but I'd like to disable it. It controls libmudflap and the -fmudflap flag. I think the only reason this flag exists is so we can disable it in crossdev. It's not required by anything in the tree, the code is bitrotten and has been removed for GCC 4.9. If you know how to use -fmudflap, you know how to set a USE flag. it was the hot new checker when it was first added, but it never really caught on and asan is the way to go now. i occurred to me a few weeks ago to turn it off by default after watching another cross-compile go by with it on, but looks like you got it covered. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
Dnia 2014-01-12, o godz. 01:53:47 Ryan Hill dirtye...@gentoo.org napisał(a): fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. 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. -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
El dom, 12-01-2014 a las 09:24 +0100, Michał Górny escribió: Dnia 2014-01-12, o godz. 01:53:47 Ryan Hill dirtye...@gentoo.org napisał(a): fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. 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. I was also wondering about what we prefer if Michal's suggestion is not possible: - Build support for other langs by default - More time when we need to emerge gcc or update it but less time as we don't need to rebuild for that (I remember when I needed to build pdftk and needed to wait for a gcc rebuild giving gcj support) - Build support for other langs disabled by default - Well, does it save so much time to compensate the rebuilds we would need to do in the future when we need to emerge some package some time?
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
Am Sonntag, 12. Januar 2014, 08:53:47 schrieb Ryan Hill: fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. The problem with fortran is (was?) a bit that it creeps in in unexpected places via scientific libraries (e.g. image processing). Not so far in the past it was necessary to build media-gfx/digikam for example... I don't like the long gcc build times either, but would recommend keeping it enabled by default, for a simple reason: We do not have a clean way to depend on it (gcc[fortran] dependencies are pointless because of slotting and gcc- config), and an eclass can only output errors and ask for manual intervention. While just about everywhere else we try to automatize as much as possible... -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
On 01/12/2014 02:53 AM, Ryan Hill wrote: fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. A lot of popular fortran code is old scientific stuff without a build system, license, upstream etc. that isn't going to be in the tree for that reason. Some of these have only install gcc for build instructions, so it might cause confusion for a few minutes if gcc can't compile fortran. The only popular modern example I have on hand is sage[1]. The two easy choices for what-to-do are, * Disable everything by default. * USE-default everything to match GCC's default --enable-languages[2] (c, c++, fortran, java, objc) Either one is fine. A one-time gcc rebuild for fortran is not a big deal and at that point is probably the least of your problems. [1] http://www.sagemath.org/ [2] http://gcc.gnu.org/install/configure.html
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
On Sat, Jan 11, 2014 at 11:53 PM, Ryan Hill dirtye...@gentoo.org wrote: While I'm adding USE defaults to toolchain.eclass and moving them out of the profiles, I thought now would be a good time to review a couple default flag settings. mudflap: This is currently enabled by default but I'd like to disable it. It controls libmudflap and the -fmudflap flag. I think the only reason this flag exists is so we can disable it in crossdev. It's not required by anything in the tree, the code is bitrotten and has been removed for GCC 4.9. If you know how to use -fmudflap, you know how to set a USE flag. Sounds good. fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. I'm for removing fortran by default. Disabling fortran is always one of the first things I do on a new install. I've disabled it by default in the mips profile already.
Re: [gentoo-dev] Default USE changes for fortran and mudflap?
On Sun, Jan 12, 2014 at 1:53 AM, Ryan Hill dirtye...@gentoo.org wrote: fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. If you do disable fortran by default, please make a news item, if you don't mind. I know this will effect some percentage of our scientific user base (including myself). Thanks! Matt Matthew Summers Gentoo Foundation Inc. GPG: 111B C438 35FA EDB5 B5D3 736F 45EE 5DC0 0878 9D46
[gentoo-dev] Default USE changes for fortran and mudflap?
While I'm adding USE defaults to toolchain.eclass and moving them out of the profiles, I thought now would be a good time to review a couple default flag settings. mudflap: This is currently enabled by default but I'd like to disable it. It controls libmudflap and the -fmudflap flag. I think the only reason this flag exists is so we can disable it in crossdev. It's not required by anything in the tree, the code is bitrotten and has been removed for GCC 4.9. If you know how to use -fmudflap, you know how to set a USE flag. fortran: Do we want to keep enabling fortran by default? The majority of users will never get the urge to install a fortran package, and the fortran eclass 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 there are other opinions. -- Ryan Hillpsn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 signature.asc Description: PGP signature
