f8a308ad6a
(1) rework how command-line arguments are parsed: instead of --command=<arg>, use --command <arg> This allows us to not rely on certain commands for which we first need to figure out where they are to parse the arguments, which in turn allows us to (2) add the command-line option --preserve-path to prevent bootstrap from munging the PATH (as it does on some platforms) and look in places that are not currently in the PATH Finally, (3) add a check to see if we're using gcc, and set and add the PKGSRC_COMPILER=<compiler> flag to the sample mk.conf. This is particularly useful (and actually necessary) under IRIX. Bump BOOTSTRAP_VERSION. |
||
---|---|---|
.. | ||
bmake | ||
files | ||
mods | ||
bootstrap | ||
cleanup | ||
mkbinarykit | ||
mkbootstrapkit | ||
pkg.sh | ||
README | ||
README.AIX | ||
README.Darwin | ||
README.FreeBSD | ||
README.Interix | ||
README.IRIX | ||
README.Linux | ||
README.MacOSX | ||
README.OpenBSD | ||
README.OSF1 | ||
README.Solaris | ||
testbootstrap | ||
ufsdiskimage |
$NetBSD: README,v 1.4 2004/06/23 19:06:40 wiz Exp $ To try to get pkgsrc working on your system, please try the following as root: # ./bootstrap [ --prefix=${PREFIX} ] [ --pkgdbdir=${PKG_DBDIR} ] \ [ --sysconfdir=${PKG_SYSCONFBASE} ] [ --workdir=working directory] \ [ --ignore-case-check ] [ --ignore-user-check ] [ --help ] The defaults for the arguments are as follows: --prefix /usr/pkg --pkgdbdir /var/db/pkg --sysconfdir /usr/pkg/etc --workdir work It is perfectly acceptable to place ${PKG_DBDIR} under ${PREFIX}. The working directory will be created if it doesn't exist and has to be writable by the user executing ./bootstrap. Make sure that you have a working C compiler and make(1) binary in your path. See http://www.netbsd.org/Documentation/software/packages.html for more information about bootstrapping and using pkgsrc. We'd be very interested in hearing of any successes or failures on "unknown" (to us) systems.