Re: [gentoo-user] Do we have to build gcc with fortran now?

[Dale <rdalek1967@gmail.com>]

Mark Knecht wrote:
> On Wed, Jun 22, 2011 at 8:50 AM, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Mark Knecht wrote:
>>      
>>> I guess I can stop playing scaredicat and remove it. :-)
>>>
>>> - Mark
>>>
>>>
>>>
>>>        
>> I think the dev added it back.  So, if you really don't need it, put the
>> minus sign in front.
>>
>> If you use KDE like me, be prepared to put the thing back tho.  Some KDE
>> packages depend on things that seem to need it enabled.
>>
>> I just love running in circles.
>>
>> Dale
>>      
> Actually, for me it's a non-issue. I've had it in all along. Even when
> I remove it from make.conf and package.use it still shows up in gcc:
>
> c2stable ~ # emerge -pv gcc
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R    ] sys-devel/gcc-4.4.5  USE="fortran gtk mudflap
> (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc
> (-fixed-point) -gcj -graphite (-hardened) (-libffi) -multislot -nocxx
> -nopie -nossp -objc -objc++ -objc-gc -test -vanilla (-n32%) (-n64%)"
> 61,647 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 61,647 kB
> c2stable ~ #
>
> so nothing is getting rebuilt on my system by removing it. As not
> every system here uses the KDE profile I'll investigate removing it
> later, or just leave it in case they start using KDE.
>
> Cheers,
> Mark
>
>    

I put -fortran in make.conf.  I ran emerge -uvDNa world and let it 
rebuild a few packages.  Then I get this:

 >>> Emerging (1 of 2) sci-libs/blas-reference-20070226
  * lapack-lite-3.1.1.tgz RMD160 SHA1 SHA256 size ;-) 
...                                                                                                            
[ ok ]
  * Package:    sci-libs/blas-reference-20070226
  * Repository: gentoo
  * Maintainer: sci@gentoo.org
  * USE:        amd64 consolekit elibc_glibc kernel_linux multilib 
policykit userland_GNU
  * FEATURES:   preserve-libs sandbox

  * Please install currently selected gcc version with USE=fortran.
  * If you intend to use a different compiler then gfortran, please
  * set FC variable accordingly and take care that the neccessary
  * fortran dialects are support.

  * ERROR: sci-libs/blas-reference-20070226 failed (setup phase):
  *   Currently no working fortran compiler is available
  *
  * Call stack:
  *          ebuild.sh, line   56:  Called pkg_setup
  *          ebuild.sh, line 1446:  Called fortran-2_pkg_setup
  *   fortran-2.eclass, line  134:  Called _die_msg
  *   fortran-2.eclass, line  120:  Called die
  * The specific snippet of code:
  *      die "Currently no working fortran compiler is available"
  *
  * If you need support, post the output of 'emerge --info 
=sci-libs/blas-reference-20070226',
  * the complete build log and the output of 'emerge -pqv 
=sci-libs/blas-reference-20070226'.
  * The complete build log is located at 
'/var/log/portage/sci-libs:blas-reference-20070226:20110622-180601.log'.
  * The ebuild environment file is located at 
'/var/tmp/portage/sci-libs/blas-reference-20070226/temp/die.env'.
  * S: 
'/var/tmp/portage/sci-libs/blas-reference-20070226/work/lapack-lite-3.1.1'

 >>> Failed to emerge sci-libs/blas-reference-20070226, Log file:

 >>>  
'/var/log/portage/sci-libs:blas-reference-20070226:20110622-180601.log'
root@fireball / #

Am I going in circles again?  I don't drink because I don't like being 
drunk.  I also don't spin around in my chair for the same reason.  One 
of those may be needed to reverse the problem here.

Now to go see how to fix this mess once and for all.

Dale

:-)  :-)