On Fri, Nov 7, 2014 at 6:23 PM, Chris H <bsd-li...@bsdforge.com> wrote:
> Greetings,
>  Sorry for the long title. I've been [needlessly] struggling
> with getting ports within the ports tree to build, on a
> fresh 11-CURRENT install from 2014-11-05. With custom
> KERNEL and WORLD built, and installed.
> Here's my situation, which has worked well since ~8.2;
> make.conf(5)
> src.conf(5)
> I'll neither argue, nor defend rational for w/o clang. To
> boring and out of scope for this thread. That said; I
> realize that lang/clang(33/34/35) is the default toolchain
> for 10+, and that's just fine by me. So I shouldn't be

lang/clang(33/34/35) is not the default toolchain in 10+.  10+ uses a
version of clang that is included in the FreeBSD source (/usr/src).

> terribly surprised when install kernel/world, followed by
> make delete-old removes the clang built, or provided by
> the base install from the (initial) install procedure. But
> what _does_ surprise me, is that the install of lang/gcc-48
> does _not_ become the compiler of choice with the above
> $ENV, after [seemingly] deleting clang. I understand that

FAVORITE_COMPILER is used by Mk/Uses/compiler.mk.

If you want ports to build with lang/gcc-48, then you would need to
check that the ports you are trying to compile have either
USES=compiler or USES_GCC defined in their Makefile. Otherwise the
ports will use the compiler that is provided by the FreeBSD source
(gcc 2.4.x or clang).

When WITHOUT_CLANG is defined in make.conf/src.conf.  The FreeBSD
source will be built using gcc 2.4.x from the FreeBSD source.
/usr/bin/{cc,c++} will then be linked to the gcc versions.  The ports
will then use this version to build if there is no USES_GCC or
USES=compiler in the ports Makefile.


No electrons were maimed while sending this message. Only slightly bruised.
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to