d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2fbfa5f862
freebsd-dev/release/picobsd/custom/crunch1/Makefile

53 lines
1.2 KiB
Makefile
Raw Normal View History

Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
#
# $FreeBSD$
#
SRC?=/usr/src
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
COMMOBJ?= ${.OBJDIR}/../../common-obj
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
all: crunch
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
crunch1.conf: crunch.conf
@cat ${.ALLSRC} | sed -e "s@/usr/src@${SRC}@" > ${.TARGET}
crunch.mk: crunch1.conf crunch.inc
@crunchgen -h ${.CURDIR}/crunch.inc -m crunch.mk crunch1.conf
crunch1.mk: crunch.mk
@sed -e "s@make depend@make obj \&\& make depend@" \
Fix the obvious make and sed syntax errors lurking from my last "fix".
2000-07-31 11:00:01 +00:00
-e "s@/usr/obj/@${COMMOBJ}@" crunch.mk > ${.TARGET}
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
crunch: crunch1.mk
Fix the obvious make and sed syntax errors lurking from my last "fix".
2000-07-31 11:00:01 +00:00
@if [ ! -d build ]; then mkdir build; fi
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
@cp crunch1.c build/
@(cd build && env MAKEOBJDIRPREFIX=${COMMOBJ} \
${MAKE} -f ../crunch1.mk -DNOPAM all \
Drop support for -DRELEASE_BUILD_FIXIT and -DCRUNCHED_BINARY in ${CFLAGS}. The only supported method thus is -DRELEASE_CRUNCH.
2001-04-03 13:34:35 +00:00
"CFLAGS=${CFLAGS} -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT") #2>&1 >/dev/null
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
clean:
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
rm -rf build
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
rm -f *.o *.stub *.lo *_stub.c *.mk \
crunch.cache \
crunch.mk \
crunch.c \
crunch1* \
crunch \
.tmp_* \
*~ \
*.gz
install:
Install the crunched binaries into /sbin, not /stand. This was originally done to track down yet another case of lost init, and is not strictly necessary, but it seems more logical to have binaries in /sbin than in /stand. Previously /sbin and /bin were symlinks to /stand. Now /bin and /stand are symlinks to /sbin.
1999-12-20 02:10:16 +00:00
rm -f ${MFS_MOUNTPOINT}/sbin/*
Make a separate build directory in which to put all the generated objects, to simplify working with PicoBSD. Add the ability to put make instructions in crunch.inc to pass to the build process. Now explicitly make the objects in our own object tree, since we want to build the objects with our own defines, and allow this to occur in a common object tree for all PicoBSD builds, if required. This is controlled by the COMM_OBJ variable, for those who don't want this - setting it to /usr/obj again will just pick up the objects from your last make buildworld, as before.
2000-07-18 13:43:38 +00:00
cp build/crunch1 ${MFS_MOUNTPOINT}/sbin/crunch
Install the crunched binaries into /sbin, not /stand. This was originally done to track down yet another case of lost init, and is not strictly necessary, but it seems more logical to have binaries in /sbin than in /stand. Previously /sbin and /bin were symlinks to /stand. Now /bin and /stand are symlinks to /sbin.
1999-12-20 02:10:16 +00:00
chmod 555 ${MFS_MOUNTPOINT}/sbin/crunch
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
for i in `crunchgen -l crunch1.conf` ; \
do \
Install the crunched binaries into /sbin, not /stand. This was originally done to track down yet another case of lost init, and is not strictly necessary, but it seems more logical to have binaries in /sbin than in /stand. Previously /sbin and /bin were symlinks to /stand. Now /bin and /stand are symlinks to /sbin.
1999-12-20 02:10:16 +00:00
ln ${MFS_MOUNTPOINT}/sbin/crunch ${MFS_MOUNTPOINT}/sbin/$${i}; \
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
done
Install the crunched binaries into /sbin, not /stand. This was originally done to track down yet another case of lost init, and is not strictly necessary, but it seems more logical to have binaries in /sbin than in /stand. Previously /sbin and /bin were symlinks to /stand. Now /bin and /stand are symlinks to /sbin.
1999-12-20 02:10:16 +00:00
rm ${MFS_MOUNTPOINT}/sbin/crunch
Add 'custom' directory with significantly restructured build (now using make instead of custom scripts) and two floppies instead of one. The resultant floppy can do everything that the individual floppies (dial, net, install, isp, router) could do, modulo some bit rot that has occurred since PicoBSD last compiled. It also includes all the programs on the fixit floppy, which could thus also die. /bin currently contains the following files: -sh dump ln ns sps [ ed login ping stty badsect ex ls ps swapon cat expr mkdir pwd sync chgrp fdisk mknod pwd_mkdb sysctl chmod find more rdump syslogd chown fsck mount reboot tar chroot ftp mount_cd9660 restore telnet clri getty mount_msdos rlogin telnetd cp grep mount_nfs rm test date gunzip mount_std rmdir traceroute dd gzip msg route umount dev_mkdb hostname mt routed vi df ifconfig mv rrestore view dhclient inetd natd rsh vm dhclient-script init netstat sed w disklabel kget newfs sh zcat dmesg kill nfs sleep Structure is in place for using the same build for the other directories, but I'm no longer sure we need this. The current first floppy will run fine by itself, but the size of a compressed kernel has increased by nearly 50% since 3.2, and there's not much space for anything useful on the remainder of the floppy. The current method creates a larger mfs and can read as many floppies as the user can stand. The footprint appears to be round 14 MB.
1999-12-10 21:52:18 +00:00
# Install the MIB files
#cp mibs/*.txt ${MFS_MOUNTPOINT}/usr/local/share/snmp/mibs/
.include <bsd.prog.mk>
Reference in New Issue Copy Permalink