Summary: | Patch to enable nano to be compiled using icc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Svein Erik Brostigen <svein.brostigen> |
Component: | [OLD] Development | Assignee: | SpanKY <vapier> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | dberkholz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to enable nano to be compiled using icc |
Description
Svein Erik Brostigen
2003-12-17 08:40:40 UTC
Created attachment 22357 [details, diff]
Patch to enable nano to be compiled using icc
fixed in cvs, thanks I don't feel that USE flags are an appropriate way to choose a compiler. It should be based purely on what $CC is in the environment, to eventually be set by gcc-config. Did the ebuild previously respect `CC=icc emerge nano`? tbh, i dont really care anymore whether controling icc/uclibc usage via USE is 'correct' ... people have talked about the ideal solution of controlling the system compiler ala gcc-config or whatever, but nothing has happened this is a fine temporary solution and until someone starts producing real usuable code, it'll stay this way That was more for the reporter's benefit, as he's in training to be the new ICC person. |