I've added the -Wno-format option in the relevant build makefile. Do a "cvs update" in eros/src/build/lib/make to get the change.
In regard to the earlier thread of discussion about log space exhaustion, the change to the kernel source is incorrect. The desired change is the one that grows the size of the log in the volume description file.
Be advised, however, that the image constructed in sysimage/ probably doesn't work.
Jonathan S. Shapiro, Ph. D.
Research Staff Member
IBM T.J. Watson Research Center
Phone: +1 914 784 7085 (Tieline: 863)
Fax: +1 914 784 6576
Guido Witmond <email@example.com>@eros-os.org on 02/16/2000 06:20:18 PM
Sent by: firstname.lastname@example.org
To: Eyal Lotem <email@example.com>
Subject: Re: Compilation of the EROS source with some gcc versions
On Sat, Feb 05, 2000 at 08:02:38PM +0000, Eyal Lotem wrote:
> It seems that the compilation process enables a flag (or maybe it is
> sometimes enabled by default) to treat warnings as errors.. This fact,
> along with the fact that some gcc versions treat mistyped arguments to
> printf as warnings is a problem.
> at least under this setting I had to go through some trouble to fix it,
> the simplest solution seems to be casting the arguments to printf.
I tried that myself, lots of work to no use, as the correct formatting specifier depends on the choice of either 'unsigned int' or 'unsigned long' for the uint32_t typedef in ~/eros/src/base/sys/eros/i486/target.h:104 To get rid of these errors I added the
options to the GCCWARN and GPLUSWARN variables in
Regards, Guido Witmond.
--- Let's make Linux history too.