minix/distrib/sets/lists/comp/ad.m68k.shl

# $NetBSD: ad.m68k.shl,v 1.9 2013/01/16 16:01:05 christos Exp $
./usr/lib/libm68k_pic.a				comp-c-piclib
Synchronize on NetBSD-CVS (2013/12/1 12:00:00 UTC) - Fix for possible unset uid/gid in toproto - Fix for default mtree style - Update libelf - Importing libexecinfo - Resynchronize GCC, mpc, gmp, mpfr - build.sh: Replace params with show-params. This has been done as the make target has been renamed in the same way, while a new target named params has been added. This new target generates a file containing all the parameters, instead of printing it on the console. - Update test48 with new etc/services (Fix by Ben Gras <ben@minix3.org) get getservbyport() out of the inner loop Change-Id: Ie6ad5226fa2621ff9f0dee8782ea48f9443d2091 2013-12-06 12:04:52 +01:00			`# $NetBSD: ad.m68k.shl,v 1.9 2013/01/16 16:01:05 christos Exp $`
Upgrading build system to new NetBSD revision The tested targets are the followgin ones: * tools * distribution * sets * release The remaining NetBSD targets have not been disabled nor tested at all. Try them at your own risk, they may reboot the earth. For all compliant Makefiles, objects and generated files are put in MAKEOBJDIR, which means you can now keep objects between two branch switching. Same for DESTDIR, please refer to build.sh options. Regarding new or modifications of Makefiles a few things: * Read share/mk/bsd.README * If you add a subdirectory, add a Makefile in it, and have it called by the parent through the SUBDIR variable. * Do not add arbitrary inclusion which crosses to another branch of the hierarchy; If you can't do without it, put a comment on why. If possible, do not use inclusion at all. * Use as much as possible the infrastructure, it is here to make life easier, do not fight it. Sets and package are now used to track files. We have one set called "minix", composed of one package called "minix-sys" 2012-09-12 09:37:05 +02:00			`./usr/lib/libm68k_pic.a comp-c-piclib`