Jason Bacon <jwbacon%tds.net@localhost> writes: > It sounds like I would need to bootstrap the whole pkgsrc installation > using GCC to make this work, which would probably not be difficult > using FreeBSD's GCC port (/usr/local/bin/gcc47, for example). You probably don't have to bootstrap again. I would expect that bootstrap notices clang and not gcc, and sets the default PKGSRC_COMPILER to clang. Try just having /usr/local/bin/gcc47 in PATH and changing PKGSRC_COMPILER to gcc. > What I was hoping to do, though, was bootstrap from the FreeBSD base > clang and trigger installation of a pkgsrc gcc package as a dependency > if needed. I think this would need more support in pkgsrc. The idea would be to have variables in a package NOT_WITH_COMPILER and ONLY_WITH_COMPILER that declare compilers that work, and have the framework build the other compilers with the default one as needed. So far we have been viewing it as a bug if a package does not build with gcc or clang, and fixing the packages instead. > This is what FreeBSD's USE_GCC will do if clang is the base compiler > (FreeBSD 10.0 and later). FTR, USE_GCC=any allows the use of the base > gcc compiler in FreeBSD systems prior to 10.0, while USE_GCC=yes > forces installation of a gcc port on any FreeBSD release, regardless > of whether the base compiler is gcc or clang. In NetBSD, USE_GCC sounds like a base system variable, not a package variable. We try to have pkgsrc controls and behavior not depend closely on any particular OS. So how pkgsrc copes with this on FreeBSD will likely be different from how the FreeBSD base system copes.
Attachment:
pgpVWQ6voAeAz.pgp
Description: PGP signature