| Summary: | Building devel/gmake fails if system builded with WITHOUT_INFO in src.conf | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Alexey Markov <redrat> |
| Component: | Individual Port(s) | Assignee: | autotools |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Alexey Markov
2010-11-16 14:40:07 UTC
Responsible Changed From-To: freebsd-ports-bugs->autotools Fix synopsis and assign. State Changed From-To: open->closed This is not gmake-specific: [root@lab:/usr/ports] 150# grep -R '^INFO=' * | wc -l 415 So, 414 other ports will similarly fail in the WITHOUT_INFO case. Similarly, not much will work at all if world is built/installed with other WITHOUT_* flags (off the top of my head, BZIP2, CPP, CXX, DICT, GROFF, LIB32, MAN, MAN_UTILS, PKGTOOLS, PROFILE, TCSH, TEXTPROC, TOOLCHAIN) Just like having a partial ports tree checked out (usually via csup/cvsup refuse files), without a full world, you're essentially on your own in terms of support. Harsh? Possibly. But expecting ports to handle all possible ways in which world can be built/installed, on top of 3 (soon to be 2) -STABLE revisions, and -CURRENT, on multiple architectures is simply not going to happen. If you want a stripped down world image, use a builder box (or the pre-built packages) and assuming you haven't enabled WITHOUT_PKGTOOLS, add them to the image itself. That'll get you a little further, since things like devel/gmake are generally build-time dependencies rather than run-time, but you'll still run into problems. |