GDC build comes with C/C++ ... ?
Joseph Rushton Wakeling
joseph.wakeling at webdrake.net
Wed Nov 21 05:45:50 PST 2012
On 11/20/2012 11:51 PM, H. S. Teoh wrote:
> Don't install gdc into the system directories; put it in its own tree,
> say, /usr/src/gdc/{bin,include,...}, then add a symlink from
> /usr/bin/gdc -> /usr/src/gdc/bin/gdc. Don't include /usr/src/gdc in your
> $PATH, but just let the symlink do its job.
Well, I'd already put it in /opt/gdc (since there's no uninstall option it feels
dangerous to put it anywhere else), but I had added /opt/gdc/bin to the path --
which as you say is the problem.
Rather than putting in symlinks, I decided to tweak the script which adds stuff
in /opt to $PATH -- adding it to the end rather than the beginning. It works,
because there's no overlap between what's in /opt and what's elsewhere in the
system, bar these C/C++ instances -- and I don't want to use them.
I was just curious whether having them was actually necessary for the GDC
install, or whether they could be discarded as byproducts, and whether there was
a way to do that at make install time ...
More information about the D.gnu
mailing list