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 1Qalcj-0006z4-IA for garchives@archives.gentoo.org; Sun, 26 Jun 2011 09:27:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 62F951C01E; Sun, 26 Jun 2011 09:25:43 +0000 (UTC) Received: from mail-iy0-f181.google.com (mail-iy0-f181.google.com [209.85.210.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 2D9531C01E for ; Sun, 26 Jun 2011 09:25:42 +0000 (UTC) Received: by iyf40 with SMTP id 40so4819589iyf.40 for ; Sun, 26 Jun 2011 02:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=d/I/H8BrP4xSRSXb/31ytDFvwXIsSX4bDDclR8MbTN0=; b=lADf8iwEf04HRiNWbkulpc1lm2x8nNxVxFTTwEIJ55FNdQC8Re3EU+hXvufjwVNWWl w5aRq+CVltXR2ZwDdASsYaAiqSCRtSO4loz19k+r8HOqWFSMDefiuzkr9wNcXpVfogAf dnSYupvEWc88DPwY1JwWEd/SDUBNQSJvVngTM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=imFYBN2mLwHKdE3recGV+8Q7ezB20LPsOFh0skVZhQHBatxeW+9wj4gCEXY3sBJUqd A/Rbfk+iW/Luar/6IKSugD/Zs3iN9RXaCi/T98iTXU8T03j5s39cavurseFZyyK9fre+ wWp3biocmd1I/Jg97fZNzrRBLNR+mtrHj+tkI= Received: by 10.42.28.195 with SMTP id o3mr5578420icc.297.1309080342633; Sun, 26 Jun 2011 02:25:42 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-120-31.jan.bellsouth.net [65.0.120.31]) by mx.google.com with ESMTPS id s2sm4292702icw.5.2011.06.26.02.25.40 (version=SSLv3 cipher=OTHER); Sun, 26 Jun 2011 02:25:41 -0700 (PDT) Message-ID: <4E06FB13.1000909@gmail.com> Date: Sun, 26 Jun 2011 04:25:39 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110606 Gentoo/2.0.14-r1 SeaMonkey/2.0.14 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> <4E06984D.5080800@kutulu.org> In-Reply-To: <4E06984D.5080800@kutulu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 515cba2f09edfa5e763e22b77d5d579f Mike Edenfield wrote: > On 6/25/2011 8:04 AM, Dale wrote: > >>> We restructured the dependency chain for fortran support, >>> which includes >>> a compile test now. The failure can be seen above. >>> >>> The Problem was in short, USE=fortran was enabled by >>> default for linux >>> arches, but people tend to disable it. Depending on >>> gcc[fortran] doesn't >>> work completely as gcc:4.4[fortran] and gcc:4.5[-fortran] >>> with gcc-4.5 >>> select can be installed, which would full fill the >>> dependency but >>> nevertheless doesn't give a working compiler. >>> >>> So now packages depend on virtual/fortran and use an >>> eclass to check for >>> a working compiler. So if you see this message, this means >>> you somehow >>> worked around gcc[fortran]. > >> That make sense? > > Yes. He's saying they didn't change the USE flag, they changed the > fortran dependency test to actually do a run-time check for fortran > because the USE flag alone wasn't sufficient. > > Which means you most likely had a non-working cantor and no fortran > compiler before and just didn't notice :) > > --Mike > > My understanding, USE flag was there and had been for a long time, got changed, this thread was started, discussion was had, USE flag was put back the way it was. So actually it was only not working while I was messing with it. That would be true ONLY if you were using the defaults. If you had -fortran then nothing should have changed as would having fortran enabled. It was only folks like me that didn't have any mention of fortran that were affected. Just one of those things. ;-) As someone else posted, this was minor compared to some things we have ran into. Dale :-) :-)