Re: Stop installing /usr/bin/clang

> On Fri, Aug 16, 2019 at 08:57:13AM +0300, nonameless_at_ukr.net wrote:
> > I see the same thing with base?/usr/bin/ld and?/usr/local/bin/ld from binutils.
> Yes but a direct ld use is very rare. When it is needed, usually the
> level of hackery applied is already high enough for the user to already
> know what she does.  I did not see it causing issues practically, while
> multiple clangs in the path cause real problems.

Though I have accepted the change, I have now heard this "multiple foo
in path" argument twice, could you please elaborate on it?

If /usr/bin /bin are first I should get base stuff, 
if /usr/local/bin are first I should get local stuff,
what exactly is this "real problems" your refering too?

Is it that something is flipping paths around?  If so that
should be fixed!  People have been using path to pick which
overload order they prefer for decades, and if we have some
how broken this.. well that should get fixed asap, not
removing stuff out of base because something is broken by
incorrect path manipulations.

Regards,
Rod
> > --- Original message ---
> > From: "Konstantin?Belousov"?<kostikbel_at_gmail.com>
> > Date: 15?August?2019,?19:48:37
> > 
> > Please look at https://reviews.freebsd.org/D21060
> > I propose to stop installing /usr/bin/clang, clang++, clang-cpp.
> > 
> > It probably does not matter when all your software comes from ports or
> > packages, but is actually very annoying when developing on FreeBSD.
> > In particular, you never know which `clang' is called in the user
> > environment, because it depends on the $PATH elements ordering.
> > 
> > To clear some confusion: this has nothing to do with not installing
> > compiler from base, /usr/bin/c{c,++,pp} are still there after the change
> > is applied.  It only to make clang on par with gcc, and to remove one
> > thing that was quite time-consuming in multi-target environment for me
> > during porting something large in FreeBSD userspace.
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 
> 

-- 
Rod Grimes                                                 rgrimes_at_freebsd.org