NOPROFILE, make release, libcom_err [was: Re: make release: creating a trimmed down release?]

# neuhauser_at_chello.cz / 2004-10-19 00:55:32 +0200:
> I'd like to create a trimmed down release, but it looks like
> make release -DNO_CXX ... is not the way to go. What's the official
> way of doing this kind of stuff? Specifically, I've attempted the build
> with

    (...)

    It now appears I managed to get past self-inflicted problems, and
    seem to be facing a genuine bug:

    ===> lib/libcom_err
    cd /usr/src/lib/libcom_err;  make install -DNO_SUBDIR DESTDIR=/R/stage/trees/base SHARED=>
    install -C -o root -g wheel -m 444   libcom_err.a /R/stage/trees/base/usr/lib
    install -C -o root -g wheel -m 444   libcom_err_p.a /R/stage/trees/base/usr/lib
    install: libcom_err_p.a: No such file or directory

    -DNOPROFILE is among WORLD_FLAGS like this:

    make release \
        BUILDNAME=$buildname \
        CHROOTDIR=$chrootdir \
        CVSROOT=$cvsroot \
        EXTSRCDIR=$extsrcdir \
        RELEASETAG=$releasetag \
        -DRELEASENOUPDATE \
        -DNOPORTS \
        -DNODOC \
        KERNEL_FLAGS=-j8 \
        WORLD_FLAGS="-j8 KERNCONF?=GENERIC NO_CXX=yes NO_BLUETOOTH=yes NO_DYNAMICROOT=yes NO_FORTRAN=yes NO_I4B=yes NO_IPFILTER=yes NO_KERBEROS=yes NO_OBJC=yes NO_OPENSSH=yes NO_OPENSSL=yes NO_SENDMAIL=yes NO_TOOLCHAIN=yes NO_BIND=yes NOATM=yes NOGAMES=yes NOINET6=yes NOPROFILE=yes"

    shouldn't the NOPROFILE variable be included on the "make install"
    line? or should I forget building a release without profiled libs?

-- 
If you cc me or remove the list(s) completely I'll most likely ignore
your message.    see http://www.eyrie.org./~eagle/faqs/questions.html