First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 140092
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Markus Dittrich <markusle@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jakub Moc <jakub@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
fftw-3.1.2.ebuild.diff fftw-3.1.2.ebuild.diff text/plain Jakub Moc 2006-07-12 03:12 0000 457 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 140092 depends on: Show dependency tree
Show dependency graph
Bug 140092 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: 2006-07-12 03:08 0000 
This builds perfectly fine here w/o any fortran once the inherit is removed,
confirmed by another user as well. Also the docs confirm that fortran is
optional. So, forcing people to re-emerge gcc w/ USE=fortran "since configure
checks for fortran" is not very nice, and also not needed. 

---

[ebuild   R   ] sys-devel/gcc-4.1.1  USE="-bootstrap -build -doc -fortran -gcj
-gtk -hardened -ip28 -ip32r10k% -mudflap -multislot nls -nocxx -objc -objc++
-objc-gc -vanilla" 48 kB 

$ gcc-config -l
 [1] i686-pc-linux-gnu-3.4.4
 [2] i686-pc-linux-gnu-3.4.4-hardened
 [3] i686-pc-linux-gnu-3.4.4-hardenednopie
 [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.4-hardenednossp
 [6] i686-pc-linux-gnu-4.0.3
 [7] i686-pc-linux-gnu-4.1.1 *

I can attach the complete build log if needed, but don't think it's needed
(also, it's huge).

------- Comment #1 From Jakub Moc 2006-07-12 03:12:45 0000 ------- 
Created an attachment (id=91554) [edit]
fftw-3.1.2.ebuild.diff

A quick patch - only check for fortran w/ USE=fortran set. Alternatively, just
nuke the inherit again. :)

------- Comment #2 From Markus Dittrich 2006-07-12 05:45:05 0000 ------- 
Hmm, strange, I had several people complaining on the forums and by
mail that configure breaks when fortran is not present on their systems.
If configure works for you without fortran that's great and I'll remove
the inherit again.

Thanks for pointing this out.

Best,
Markus

------- Comment #3 From Markus Dittrich 2006-07-12 05:45:17 0000 ------- 
Hmm, strange, I had several people complaining on the forums and by
mail that configure breaks when fortran is not present on their systems.
If configure works for you without fortran that's great and I'll remove
the inherit again.

Thanks for pointing this out.

Best,
Markus

------- Comment #4 From Markus Dittrich 2006-07-12 05:46:32 0000 ------- 
I apologize for the double post - the network is terrible here today and
I was a little impatient :(

------- Comment #5 From Jakub Moc 2006-07-12 05:51:58 0000 ------- 
(In reply to comment #3)
> Hmm, strange, I had several people complaining on the forums and by
> mail that configure breaks when fortran is not present on their systems.

Well, I guess they are victims of "eselect-compiler doesn't clean up after
itself" bug :) - see Bug 135688, Bug 136363 (wrt fftw, Bug 137180 and Bug
138956 that are dupes of the former ones are relevant).

Thanks!

------- Comment #6 From Markus Dittrich 2006-07-12 05:57:51 0000 ------- 
Yeah, very possible! This eselect cleanup bug really is unpleasant.

cheers,
Markus
First Last Prev Next    No search results available      Search page      Enter new bug