First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 58628
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Donnie Berkholz <dberkholz@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Peter Jensen <gentoo-bugs@pekaje.homeip.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
molden_check_g77.patch Proposed patch patch Peter Jensen 2004-07-28 00:17 0000 420 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 58628 depends on: Show dependency tree
Show dependency graph
Bug 58628 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-07-28 00:16 0000 
I came across this bug on Usenet in Message-ID: <2mmrh4Fop53qU1@uni-berlin.de>.
Basically, gcc needs to be compiled with the f77 USE flag in order to build g77.
However, no check is done and non-developers wouldn't know what to do with the error message.
The Bash built-in 'type' function can be used to find out if g77 exists on the system, and fail the build with a more useful error message.
I'll attach a solution that works for me.

------- Comment #1 From Peter Jensen 2004-07-28 00:17:20 0000 ------- 
Created an attachment (id=36304) [edit]
Proposed patch

------- Comment #2 From Donnie Berkholz 2004-07-28 01:09:12 0000 ------- 
Thanks. I've committed a slightly different fix. Feel free to take a look and
critique it.
First Last Prev Next    No search results available      Search page      Enter new bug