Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 530456

Summary: sys-apps/kmod-19 fails to compile with gcc-4.8.3 because of unrecognized command line option '-fdiagnostics-color=auto'
Product: Gentoo Linux Reporter: drhopfen <smaarster>
Component: [OLD] Core systemAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bkohler
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
build.log
config.log

Description drhopfen 2014-11-24 20:03:53 UTC
When trying to emerge sys-apps/kmod-19 it fails in the configuration phase with the message:

x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-fdiagnostics-color=auto'

This seems to be an option introduced by gcc-4.9 which is masked.

Reproducible: Always

Steps to Reproduce:
1. emerge sys-apps/kmod:19

Actual Results:  
Build fails while running ./configure

Expected Results:  
compilation and installation of kmod
Comment 1 drhopfen 2014-11-24 20:04:52 UTC
Created attachment 390218 [details]
emerge --info
Comment 2 drhopfen 2014-11-24 20:05:51 UTC
Created attachment 390220 [details]
build.log
Comment 3 Ben Kohler gentoo-dev 2014-11-24 20:17:13 UTC
checking if x86_64-pc-linux-gnu-gcc -std=gnu99 supports flag -fdiagnostics-color=auto in envvar CFLAGS... yes


Can you also attach config.log so we can see what's going on with this test?  On my gcc-4.8.3 setup, I get "... no", I wonder why you get "... yes"
Comment 4 drhopfen 2014-11-24 21:14:03 UTC
Created attachment 390226 [details]
config.log
Comment 5 Ben Kohler gentoo-dev 2014-11-24 21:39:31 UTC
This is a ccache problem, when ccache is enabled that test gives a bogus result.
Comment 6 drhopfen 2014-11-24 21:46:34 UTC
Thank you, emerging without ccache solved the problem. Should I file this as a ccache bug?
Comment 7 Jeroen Roovers (RETIRED) gentoo-dev 2014-11-25 08:32:47 UTC

*** This bug has been marked as a duplicate of bug 530200 ***