Commit graph

6 commits

Author SHA1 Message Date
rillig
1e9fb5689a Only gcc understands those -W* flags for warnings. 2007-08-25 09:33:57 +00:00
joerg
06cbbe0491 Don't use ld -x or ld -X. Bump version to 20070810.
Discussed with and tested by various people over the last two month.
This problem was exposed by pbulk.
2007-08-10 13:04:13 +00:00
joerg
07eedea6c2 Split bootstrap into two phases:
- phase one builds the essential tools in the bare minimal version
  needed by the infrastructure to run "make install".
- phase two runs "make install" for all the bootstrap packages.

Set WRKOBJDIR for the second phase, we never want to leave garbage
around.

This increases the time for running bootstrap, but gives more
deterministic results. It also means that e.g. configuration files
in pkg_install can be handled normally. It is a prerequirement to
sanely allow pkg_install some more extended work like building
its own libarchive without having to worry too much about limitations
on some platforms.

This fixes the expansion of @gzcat@ in the download-vulnerability-list
script.

Tested by tnn@ on Interix and myself on DragonFly.
2007-07-27 10:43:24 +00:00
jschauma
4b05d984b2 Address PR pkg/34966 as suggested by Oliver Gould and apply the same
logic to all platforms:
Some packages (such as math/gap) create wrappers based on the name of
the compiler, so ${CC} should not contain any flags.  Move flags into
CFLAGS.
2006-11-11 18:24:52 +00:00
schwarz
ff389f044d CPP on IRIX 5 with IDO cc is /usr/lib/cpp 2006-08-06 18:59:41 +00:00
jlam
c71e325c08 Import pkgtools/bootstrap-mk-files, which is the collection of bmake *.mk
files from the bootstrap kit.  This package is used during bootstrap to
properly register the installed *.mk files.

The bootstrap bmake(1) utility uses some customised .mk files in order
to pre-define certain definitions and targets, which guide the build
process.  This package provides those *.mk files for the bmake(1)
utility.
2006-07-14 23:13:00 +00:00