Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 18383 - /usr/bin/wrappers directory is handy, it should be there by default, not only when using colorgcc ;)
Summary: /usr/bin/wrappers directory is handy, it should be there by default, not only...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High enhancement
Assignee: Please assign to toolchain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-28 13:31 UTC by Danny Milosavljevic
Modified: 2007-02-28 11:30 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Danny Milosavljevic 2003-03-28 13:31:49 UTC
The directory /usr/bin/wrappers gets created when emerging colorgcc. 
But it is useful in general. Also useful would be maybe a /usr/local/bin/wrappers directory in PATH ^^

Just an idea ^^

Reproducible: Always
Steps to Reproduce:
Comment 1 Zach Welch (RETIRED) gentoo-dev 2003-04-07 17:28:40 UTC
If you check with 15387, the wrappers are being move to a more appropriate
location to mimic the distcc and ccache installations.  Also, I'm not sure
of the implications of this suggestion withe regard to various filesystem
standards.
Comment 2 Danny Milosavljevic 2003-04-25 12:36:36 UTC
anyone checked that stuff? :)

I've got no idea what they are doing, all I want to have is my mplayer, emerge, whatever... wrappers somewhere in the PATH before /usr/bin and /usr/local/bin ;)
Comment 3 Alexander Gabert (RETIRED) gentoo-dev 2004-03-05 02:59:11 UTC
to my knowledge (and to the silence in this bug report) there is gcc-config and java-config being the only triggers to change gcc profiles and the jdk/jre in use.

the /usr/bin/gcc is always a simple execve() wrapper for gcc, selecting the appropriate gcc executable via the given environment variable defined for the system by gcc-config and the entries in /etc/env.../...gcc.

so this is where the ring is closing again.

using a further abstraction layer like an additionally prepared directory would seem nice in respect to the PATH variable used

but in my eyes, PATH and other env variables are the same kind of deal.

so if you decide upon a wrapper recognizing an env var or using the PATH variable with certain directories coming first to decide which gcc to use for example can technically be compared to the same benefits and drawbacks (in my eyes)

i also have some worries regarding the whole colorgcc, distcc, ccache and cross compiler world... because it belongs all in the same team...

same applies to embedded toolchains, debugging, bounds checking and profiling support...

but until we look at the whole implementation we will hardly be able to decide which implementation to choose :-)

your input is appreciated,

thanks,

Alex
Comment 4 Alexander Gabert (RETIRED) gentoo-dev 2004-07-08 13:17:23 UTC
Zwelch left the Gentoo team long time ago.

For historic reasons this bug will be archived now as CANTFIX.

Hope you won't mind, otherwise reopen and pump some fresh blood into this.

Thanks,

Alex