1 |
Peter Humphrey wrote: |
2 |
> On Wednesday 22 June 2011 17:23:44 Mark Knecht wrote: |
3 |
> |
4 |
> |
5 |
>> When I removed the fortran flag it didn't change anything because (I |
6 |
>> suppose) the KDE profile has included it as a default. |
7 |
>> |
8 |
> So it seems. I've just tried "USE=-fortran emerge -upDvN world" and the only |
9 |
> thing that would be remerged because of fortran is gcc. So I'm going to put |
10 |
> -fortran into make.conf and see what breaks. |
11 |
> |
12 |
> |
13 |
|
14 |
It will break several things. This is what I just went through. It |
15 |
appears that if you emerge kde-meta, you have to have a fortran type |
16 |
compiler. So, you may as well keep what you got if it is working. When |
17 |
I started going down this road, I thought I could just disable fortran |
18 |
and have less packages installed. That is not the case. I removed |
19 |
fortran then had to replace that with even more packages than I had to |
20 |
begin with. |
21 |
|
22 |
If it works with fortran turned on, I'd leave it alone. With hindsight, |
23 |
I should have left well enough alone anyway. It wasn't hurting a |
24 |
thing. Watch the elog messages. It will tell you at some point to |
25 |
either enable fortran or emerge some other package that I forget the |
26 |
name of. That one package pulled several dependencies on my rig. YMMV. |
27 |
|
28 |
Just my $0.02 for whatever that's worth. |
29 |
|
30 |
Dale |
31 |
|
32 |
:-) :-) |