Re: Couldn't build a release with this morning's sources md1 fixit floppy space problem.

eculp_at_encontacto.net wrote:
> Quoting eculp_at_encontacto.net:
>
>> I tried to build a release from this morning's sources and it seems 
>> that the fixit.flp needed more that the md alocated space.
>>
>> + [ x != x ]
>> + mdconfig -a -t vnode -f /R/stage/floppies/fixit.flp
>> + MDDEVICE=md1
>> + [ ! -c /dev/md1 ]
>> + trap umount /mnt; mdconfig -d -u md1 EXIT
>> + [ xbsdlabel != x ]
>> + bsdlabel -w -B -b /R/stage/trees/base/boot/boot md1 fd1440
>> + newfs -O1 -i 40000 -o space -m 0 /dev/md1c
>> /dev/md1c: 1.4MB (2880 sectors) block size 4096, fragment size 512
>>         using 2 cylinder groups of 1.22MB, 312 blks, 32 inodes.
>> super-block backups (for fsck -b #) at:
>>  32, 2528
>> + mount /dev/md1c /mnt
>> + [ -d /R/stage/fixitfd ]
>> + set -e
>> + cd /R/stage/fixitfd
>> + + findcpio . -print -dump
>>  /mnt
>> cpio: write error: No space left on device
>> + umount /mnt
>> + mdconfig -d -u md1
>> *** Error code 1
>>
>> Stop in /usr/src/release.
>> + umount /dev
>> *** Error code 1
>>
>> I'm going to give it another try with MAKE_FLOPPIES=false which will 
>> hopefully work.
>>
>> For future reference, it there a way to restart a broken make release?
>
> Maybe I could just have put a -DNO_CLEAN and MAKE_FLOPPIES=false after 
> the error and continued but i have my doubts.  Suggestions apreciated. 
>  Especially being so near yet so far.
>
>>
>> ed
How large is it? Could it be the possible quadratic gcc 4.2 bug?
-Garrett