看板 FB_current 關於我們 聯絡資訊
Hello, Dimitry. You wrote 7 =F1=E5=ED=F2=FF=E1=F0=FF 2011 =E3., 21:17:20: >> I'm building NanoBSD image based on latest HEAD sources. I've added >> WITHOUT_GCC to install configuration, as I don't need gcc/g++ (it is >> documented in man src.conf as disabling exactly gcc and g++), but it >> affect /usr/bin/cpp too. And I need cpp for some config processing. >> Is it bug in documentation (man src.conf) or build system? I know >> about WITHOUT_TOOLCHAIN, and it seems reasonable, that >> WITHOUT_TOOLCHAIN disables cpp too, but not WITHOUT_GCC :(. > It's a bug in the documentation. WITHOUT_GCC actually disables at IMHO, it is bug in build process ;-) -- see below > least the following executables: > /usr/bin/c++ > /usr/bin/c++filt > /usr/bin/CC > /usr/bin/cc > /usr/bin/cpp > /usr/bin/g++ > /usr/bin/gcc > /usr/bin/gcov > /usr/libexec/cc1 > /usr/libexec/cc1plus I think, that /usr/bin/cpp is valuable by itself, as it is handy generic preprocessor tool, useful for preparing complex ipfw scripts, for example. All others are bundled together, for sure. I think, it is good idea to exclude cpp from this list (but not from WITHOUT_TOOLCHAIN, of course). --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org> _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"