Summary: | sys-devel/gcc-config-1.4.0: gcc wrapper is slow when no PATH is set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Buchholz (RETIRED) <rbu> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dirk, jakub |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Buchholz (RETIRED)
![]() this is because i changed it all to use full CHOST's where as the older version would default to the same exact file ... for the sake of speed, it should be easy to drop in a symlink to the host compiler config so it doesnt need to be looked up every time you can see the same exact behavior with the old version if you execute a cross-compiler without PATH set properly ... the gcc wrapper needs to query portage to figure out the proper CHOST should be fixed with gcc-config-1.4.0-r1 ... the NATIVE entry appearing in gcc-config -l is somewhat confusing and disturbing and, btw., did you check for correct behavior when selecting NATIVE in gcc-config ? it is possible to select but selects the current selected compiler (by creating a file NATIVE as a copy of the current compiler config file). first, in this situation it's not really obvious which compiler is used. second, i don't actually know what happens when you upgrade the compiler and the current compiler gets unmerged ? even upgrade e.g. from 4.1.2 to 4.1.3 would render this NATIVE file incorrect and leave the system without a correct working compiler ?!? so dont select NATIVE and it isnt a problem |