Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=13003





------- Additional Comments From sqweek AT gmail.com  2006-08-20 11:01 -------
 I'm not suggesting sorcery uses the environment variable CC.
 My point is a -cc style option that tells sorcery "use this c compiler, 
m'fer" is:
a) more flexible (saves future "tcc support in sorcery", "uclibc support in
sorcery" requests)
b) no extra effort to implement if you need to put dietlibc stuff in the gcc
wrapper already

Andrew Stitt wrote:
> Of course, theres no reason the end user can't just set CC and have it work
> for most spells without sorcery having to do anything.

 This is a nice point, and raises the question whether any kind of support is
called for in sorcery. I'd say it's still useful as the wrapper solution 
doesn't
require the end user to know what kind of the build system the package uses 
(at
this point, they might aswell just custom build it themselvels and delve the
install). Though I guess it might even be hard to guarentee a wrapper script
solution will work with all build systems (does scons ignore even PATH?).

Seth Woolley wrote:
> I don't know why we're not installing diet to the normal paths so that it 
> can
> be used the same way as ccache and distcc, and even if it couldn't be
> installed in a regular path, why can't we just install a wrapper script or
> symlink from /usr/bin?

 Upstream default is to install in /opt/diet. But yes, /opt/diet/bin/diet is
designed to be dropped somewhere in the path.

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.