Subject: Re: Makeing a release complains that `work' size of 1478656 is larger
To: Luke Mewburn <lukem@wasabisystems.com>
From: Audun Arnesen Nordal <audun@stud.cs.uit.no>
List: current-users
Date: 10/23/2002 19:36:11
On Fri, 18 Oct 2002, Luke Mewburn wrote:
> On Thu, Oct 17, 2002 at 07:47:01PM +0100, wleeson@indigo.ie wrote:
> | Hi,
> | I did a build to make a release distribution so I could try out
> | current on another machine and got the following warning
> |
> | Creating image into ramdisk-tiny.fs...
> | rm -f ramdisk-tiny.fs ramdisk-tiny.fs.tmp
> | /usr/src/tools/obj/tools.NetBSD-1.6I-i386/bin/nbmakefs -t ffs -B le -s 1440k -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 1478656 is larger than the maxsize of 1474560.
> | *** Error code 1
>
> I fixed this problem "yesterday" (my `yesterday' :-).
> Try updating your sources and trying again.
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
without?
Regards
--
Audun Nordal