Subject: Re: Makeing a release complains that `work' size of 1478656 is larger
To: Audun Arnesen Nordal <email@example.com>
From: Frederick Bruckman <firstname.lastname@example.org>
Date: 10/23/2002 14:15:20
On Wed, 23 Oct 2002, Audun Arnesen Nordal wrote:
> Hm... I updated with sources from today, but I still get
> rm -f ramdisk-tiny.fs ramdisk-tiny.fs.tmp
> /usr/obj/tools/tools.NetBSD-1.6I-i386/bin/nbmakefs -t ffs -B le -s 1452k
> -F work.spec -N /usr/src/etc -o bsize=4096,fsize=512 -o
> optimization=space,minfree=0,nsectors=1,ntracks=128 -f 10 -f 14
> ramdisk-tiny.fs.tmp work && mv -f ramdisk-tiny.fs.tmp ramdisk-tiny.fs
> nbmakefs: `work' size of 1495040 is larger than the maxsize of 1486848.
> Could this be because my use of cpuflags (-march=pentiumpro) results in
> larger object files?
> Is there a workaround for building a platform
> optimized distribution to a DESTDIR, and perhaps have the floppies built
You could "./build.sh" with optimizations, but no "-R", followed by
".build.sh -u -R <somewhere>", with no optimizations. Typically,
everything gets relinked the second time through, but not rebuilt,
except, of course, for the kernels and floppies, which weren't built
at all on the first round, so that should do what you want.