Date: Fri, 21 Nov 1997 18:49:44 -0500 (EST) Message-Id: <199711212349.SAA00757@delorie.com> From: DJ Delorie To: broeker AT physik DOT rwth-aachen DOT de CC: djgpp-workers AT delorie DOT com In-reply-to: (message from Hans-Bernhard Broeker on Fri, 21 Nov 1997 21:31:59 +0100 (MET)) Subject: Re: alpha-971114: Makefiles revisited Precedence: bulk > * Not all tools get made with the newly compiled libc.a, crt0.o and stub, > as can be seen with RCS 'ident' tool. Those are the ones that need to run on the build machine, which may not be MS-DOS at all. > * Due to a bug in the 'makemake' tool, you couldn't call the sub-makefiles > in libc, libm, and debug any more, after the corresponding library has > been built once. 'makemake' reads in the 'makefile.oh' files from all > subdirectories to get the list of objects to link into the lib and writes > that into a big 'makefile.oh' file, among others. The bug is that it will > read the big master makefile.oh file as well if called again. (fixed) Oops. I wonder why it works for me? > * A little problem that's a bit hard to find: you have to stubedit your > 'make' to more than the default (as of 2.01) 16 KB of transfer buffer > size. Otherwise, passing the 14 KB long list of filenames for the libc.a > 'ar' command line around will break, with no visible error message but > 'Error -1'. It should be using the other option - the one with @makefile.rf in it. > * It will unconditionally install all the files in '../bin', '../lib' > etc., relative to the 'src' directory where the build starts. This is the scheme I've been using all along. It's important to keep backups anyway. > * Building in a separate tree, outside of $DJDIR, would help to avoid the > aforementioned danger, but it doesn't work, at least not unless you're > willing to install a second copy of djdev202 and at gcc2721b in your build > tree as well. You have to install at least djcrx201.zip or at most djdev201.zip/gcc*b.zip to get the extra files you need. This has always been the case.