summaryrefslogtreecommitdiffstats
path: root/release/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Set PATH statically, and use 'env -i' to kick chroot(8). As a result,matusita2002-06-191-2/+2
| | | | | | | | | the second buildworld environment is fully isolated from parent's environment variables. Tested virtually on: snapshots.jp.FreeBSD.org Approved by: arch@ (silently) MFC after: 2 weeks
* Explicitly set TARGET and TARGET_ARCH in a chroot sandbox.matusita2002-06-081-0/+6
| | | | | | | | | | | | | | | | In fact, these variable are set as environment variables since we run "make TARGET=xxx TARGET_ARCH=xxx"; TARGET and TARGET_ARCH are declared in the command line arguments. However, if you are not make(1) guy, it is hard to understand that TARGET/TARGET_ARCH are appropriately set in a chroot environment (as environment variables). Now, the only environment variable need to be set explicitly is 'PATH'. If we set PATH in /mk script, we can make pristine sandbox for release build (i.e., "env -i /usr/sbin/chroot ${CHROOT} /mk" will work). Valuable comments about this issue from: ru Tested on (virtually): snapshots.jp.FreeBSD.org MFC after: 2 weeks
* Install MD documentations in ${TARGET} directory instead of ${TARGET_ARCH}.nyan2002-06-041-6/+6
|
* Change the ">>> make release ..." output to also include ${TARGET}.ru2002-05-271-2/+2
|
* Fixed the nasty bug I introduced in rev. 1.671 that gotru2002-05-271-2/+1
| | | | | fatal in the previous delta. Repeat after me: exists() is executed at parse time.
* PC98 creates different BOOTMFS configs for different floppy sizes.ru2002-05-251-12/+14
| | | | | Broken in: rev. 1.672 Spotted by: nyan
* Convert Perl scripts to awk(1).ru2002-05-241-2/+2
|
* Build ports needed for release documentation WITHOUT_PYTHON.bmah2002-05-181-1/+1
|
* Split release.2 into two stages. release.2 now install the baseru2002-05-141-22/+26
| | | | | dist, while release.3 makes and installs crypto, krb4, and krb5 dists. This makes release.3 restartable (with "make rerelease").
* Make sure the first ${CHROOTDIR} installworld is done for the correctru2002-05-141-2/+3
| | | | | | | arch. This makes "make release TARGET_ARCH=foo" really work. (I only tested with "make rerelease" before to save some time and did not notice the problem.)
* GC now redundant BOOTSTRAPUTILS stuff.ru2002-05-141-20/+1
|
* Milestone #2 in cross-arch make releases. They now work!ru2002-04-301-51/+60
| | | | | | | | | You need to set TARGET_ARCH and possibly TARGET, the same way you normally do it for a cross build(7). Renamed `distribworld' to a more natutal `distributeworld'. Put pwd_mkdb(8) under ${INSTALLTMP}; for `distributeworld'.
* Some components of the crunched binaries may use build-toolsru2002-04-291-11/+14
| | | | | | that are to be run on the building host. (Currently, bin/sh and usr.sbin/sysinstall use them.) Make sure we build them in the correct environment, like we do it in the buildworld.
* Introduce CVSCMDARGS make variable to set command-line options for cvs.matusita2002-04-271-13/+15
| | | | | | | | | You may want set '-D data-spec' to this variable. PR: 31218 Submitted by: Alexandr Listopad <laa@laa.zp.ua> MFC after: 5 days (if re@ permits)
* If we are making a "release", we can obviously use -DNOCLEAN buildworld,ru2002-04-261-5/+0
| | | | to save some time, because ${CHROOTDIR}/usr/obj does not even exist.
* Milestone #1 in cross-arch make releases.ru2002-04-261-115/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not install games and profiled libraries to the ${CHROOTDIR} with the initial installworld. Eliminate the need in the second installworld. For that, make sure _everything_ is built in the "world" environment, using the right tool chain. Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the buildworld process into stages, and skip some stages when SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5 dists). Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running makewhatis(1) at the end of installworld (used when making crypto, krb4, and krb5 dists). In release/scripts/doFS.sh, ensure that the correct boot blocks are used. Moved the creation of the "crypto" dist from release.5 to release.2. In release.3 and doMFSKERN, build kernels in the "world" environment. KERNELS now means "additional" kernels, GENERIC is always built. Ensure we build crunched binaries in the "world" environment. Obfuscate release/Makefile some more (WMAKEENV) to achieve this. Inline createBOOTMFS target. Use already built GENERIC kernel modules to augment mfsfd's /stand/modules. GC doMODULES as such. Assorted fixes: Get rid of the "afterdistribute" target by moving the single use of it from sys/Makefile to etc/Makefile's "distribute". Makefile.inc1: apparently "etc" no longer needs to be last for "distribute" to succeed. gnu/usr.bin/perl/library/Makefile.inc: do not override the "install" and "distribute" targets, do it the "canonical" way. release/scripts/{man,cat}pages-make.sh: make sure Perl manpages and catpages appear in the right dists. Note that because Perl does not respect the MANBUILDCAT (and NOMAN), this results in a loss of /usr/share/perl/man/cat* empty directories. This will be fixed soon. Turn MAKE_KERBEROS4 into a plain boolean variable (if it is set it means "make KerberosIV"), as documented in the make.conf(5) manpage. Most of the userland makefiles did not test it for "YES" anyway. XXX Should specialized kerberized libpam versions be included into the krb4 and krb5 dists? (libpam.a would be incorrect anyway if both krb4 and krb5 dists were choosen.) Make sure "games" dist is made before "catpages", otherwise games catpages settle in the wrong dist. Fast build machine provided by: Igor Kucherenko <kivvy@sunbay.com>
* Build the catpages distribution in a more natural way.ru2002-04-241-1/+2
|
* The chrooted environment isn't nearly pristine, so resetru2002-04-241-0/+1
| | | | MAKEOBJDIRPREFIX to the canonical /usr/obj while there.
* Change the name of the 'bin' distribution to 'base'.obrien2002-04-231-16/+16
| | | | | | | This is done since it contains much more than /bin, and also gets in the way when making a combined install+fixit CD. OK'ed by: jkh
* Do not spam initial ${CHROOTDIR} world with Texinfo and HTML docs.ru2002-04-231-2/+3
| | | | | | For rerelease, run "make -DNOCLEAN world" instead of simple and insufficient in some cases "make all install". This is especially true for cross-arch "make release"s which we don't (yet) support.
* Set hint.acpi.0.disable to 1 in /boot/loader.rc of {boot,kern}.flp,matusita2002-04-091-0/+1
| | | | | | | | | | | | | since we have no ACPI feature in the installation kernel at this time. Without having this, we'll see ACPI no autoload failed -- no such file or directory message at boot time, and it makes some confusion to the users. We can backout this change if installation kernel has ACPI feature. PR: 36911 (partly)
* Fix recent fixit.flp flood:matusita2002-04-021-5/+4
| | | | | | | | | | | - don't make device files since we are in the DEVFS era. (for the last resort, fixit.flp still has /dev/MAKEDEV.) - increase FIXITINODE size to 10 times (40000). After this change, we have 42kbytes of free space, and 38 of free inodes (confirmed with 5.0-CURRENT-20020327-JPSNAP). Since 4-stable doesn't have DEVFS, we can't MFC this (except FIXITINODE).
* Make it easier to specify a custom kernel configuration for the bootmurray2002-03-311-1/+1
| | | | | | | | floppies. PR: misc/36032 Submitted by: David Yeske <dyeske@yahoo.com> MFC after: 1 week
* Bump MFSSIZE to the value used by i386 and pc98. This larger MFSmurray2002-03-301-1/+1
| | | | | filesystem will still compress below the 1.44 megabyte threshold for the floppy image.
* Alpha does not support PCCARD installs, so we do not need the 58kmurray2002-03-291-0/+2
| | | | | | /etc/defaults/pccard.conf. Assume for now that only MACHINE_ARCH=="i386" wants to do PCCARD installs. We're still using too much space, but this is a big help.
* Teach sysinstall(8) how to read boot managers out of /bootru2002-03-281-0/+3
| | | | | | | | instead of hardcoding them into the binary. This replaces the work-around in usr.sbin/sysinstall/Makefile,v 1.121. Suggested by: jhb MFC in: 1 week
* Remove all traces of write_mfs_in_kernel from the base system releasejhb2002-03-261-3/+0
| | | | | | area. Requested by: joe
* Remind developers to update release(7) if they make substantialmurray2002-03-171-0/+2
| | | | changes to this file.
* Supply -DNO_WERROR to the kernel build during release.peter2002-02-251-3/+3
|
* Typo fix: missing ;.matusita2002-02-251-1/+1
| | | | | Pointed out by: Manfred Antar <null@pozo.com> Pointy hat to: matusita
* Mkdir ${CHROOTDIR}/usr/ports/distfiles if RELEASEDISTFILES is not set.matusita2002-02-121-0/+2
| | | | | | | | | | | | | We ensure that 'ports.tgz' tarball should have ports/distfiles directory. At first, ${CHROOTDIR}/usr/ports is empty (rm -rf ports), then extract ports files from CVS repository. Then if RELEASEDISTFILES is defined, ${CHROOTDIR}/usr/ports/distfiles directory is created by cp(1). However, if you don't specify RELEASEDISTFILES, there is no chance to create ${CHROOTDIR}/usr/ports/distfiles directory. Submitted by: {ushi,tora}.jp.FreeBSD.org MFC after: 5 days
* Change variable name from DOCDISTFILES to RELEASEDISTFILES. Respectmatusita2002-02-031-4/+9
| | | | | | | | | | | | | | | | | | DOCDISTFILES if defined. No impact should happen with this change. DOCDISTFILES is introduced by rev. 1.541, to point the directory that contains the distfiles for ports/textproc/docproj. It's good, but we also build ports/sysutils/mkisofs during the release (if MAKE_ISOS is defined). It is natural that cdrtools tarball is prefetched, then copy it under ${CHROOTDIR}/usr/ports/distfiles. As a result, DOCDISTFILES variable is somewhat abused for non-doc tarballs; *DOC*DISTFILES is no longger appropriate name for that. PR: 16843 PR: 34194 Submitted by: murray MFC after: 6 days
* In revision 1.351, All files/directories in ${CHROOTDIR}/usr/ports/distfilesmatusita2002-01-311-2/+2
| | | | | | | | | | | | | | | | are removed, because ports.tgz includes distfiles by accident. However, removing files/directories is *not* mandatory. The only requirement is "ports.tgz doesn't include distfiles/* but distfiles directory itself". If this is correct, the right way is to set an option to tar(1), not to include these files. This commit is based on PR: 34194, but a little bit of modification is made by me (original patch doesn't include 'distfiles' directory). PR: 34194 Reviewed by: Adrian Steinmann <ast@marabu.ch> (PR submitter) MFC after: 9 days
* MFS 1.536.2.52 (partial) and 1.536.2.70: kgzip loader if i386 (only).matusita2002-01-201-0/+4
| | | | | | | | | | 5.0-CURRENT-20020121-JPSNAP was failed to build since kern.flp has no space. There is already a hack to kgzip loader, and it makes: -r-xr-xr-x 1 root wheel 163840 Jan 21 07:40 loader* -r-xr-xr-x 1 root wheel 90121 Jan 21 08:06 loader.kgz* 73719 bytes of free spaces to us.
* Include /dev/xpt0 into the list of devices to go onto the boot floppy, sojoerg2002-01-171-1/+1
| | | | | | camcontrol can get a handle to initiate a rescan or reset. MFC after: 1 week
* Modify the release-building process so the srelease distributionbmah2001-12-281-14/+15
| | | | | | | | | | | | | | | | | doesn't get spammed by RELNOTESng files. Previously, we built the RELNOTESng files "in place" and then populated the media (e.g. floppy, cdrom, ftp) areas from the build directories. However, the distributions got rolled after the RELNOTESng build, and thus picked up the rendered RELNOTESng files. Now, we install the RELNOTESng documents to R/stage/release.doc, then clean out the original directories in src/release/doc. We use the renditions in the staging area to populate the media areas. PR: 33141 MFC after: 3 days (plus re approval)
* At least I'm consistent. Back out the last accidental rev to this file onbmah2001-12-271-15/+14
| | | | | | | HEAD too. Noticed by: ben Another pointy hat to: bmah
* New release notes found while trying to catch-up RELENG_4 to reality:bmah2001-12-271-14/+15
| | | | whois(1) -c, pkg_delete -r, rc.conf(5) support for IPFilter state tables.
* set TMPDIR to /tmpgreen2001-12-181-0/+1
|
* Set a BOOTABLE variable to "-b" if MACHINE is not pc98, and use it fornyan2001-11-251-6/+9
| | | | | | mkisoimages.sh instead of "-b" directly. MFC after: 1 week
* PC98 boxes cannot boot from CD-ROM.nyan2001-11-241-0/+2
|
* Search ${MACHINE}/drivers.conf instead of ${MACHINE_ARCH}/drivers.conf.nyan2001-11-231-3/+3
| | | | The previous commit is not completely.
* Use a separate drivers.conf between i386 and pc98.nyan2001-11-221-2/+2
|
* Switch to using a standard /boot directory including the GENERIC kerneljhb2001-11-221-10/+9
| | | | | | | | | on CD's 1 and 2. Create a simple /boot/loader.conf on each CD that loads /boot/mfsroot.gz as a mfs_root image. The mfsroot moved from /mfsroot.gz to /boot/mfsroot.gz so that all of the boot stuff is in /boot. This allows a full kernel to be used when installing from CD on all architectures that support CD booting. Note that on x86, this requires using /boot/cdboot as a no-emulation boot image instead of /floppies/boot.flp.
* Increase the size of a mfsroot floppy for pc98 to 4320.nyan2001-11-211-2/+2
|
* Bump the mfsroot up from 2880 to 3200 for Alpha so it fits again. Usejhb2001-11-201-2/+2
| | | | | a label of auto instead of the fixed size minimum2 so that the bump in size actually has an effect.
* Use modules-depend instead of kernel-depend for doing the depend stagejhb2001-11-191-1/+1
| | | | in doMODULES.
* Split the mfsroot out from the kernel for the 2.88 boot floppy and thejhb2001-11-191-21/+11
| | | | | | | | | Alpha CD. This makes it easier to customize ISO's locally by being able to replace either the mfsroot or the kernel w/o having to do both. It also allows us to switch to using the full GENERIC kernel when booting from CD on the Alpha and on x86 when using cdboot. We don't do this yet, however. Tested on: x86, alpha
* Add a comment that the chroot area cannot reside on a "nodev"-mountedbmah2001-11-171-0/+4
| | | | | | | filesystem. PR: 12712 Submitted by: Sergei Laskavy <laskavy@Berkeley.Gambit.Msk.SU>
* Make CD-ROM distributions at the pc98 release target.nyan2001-10-291-5/+3
| | | | MFC after: 3 days
OpenPOWER on IntegriCloud