netbsd-5, netbsd-5-1 x68k release builds failing
Jeff Rizzo <[email protected]> Mon, 10 Jan 2011 11:38:58 -0800
| Newsgroups | gmane.os.netbsd.ports.x68k |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------030500020800010905040303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi-
As part of normal release engineering activity, the netbsd-5 and
netbsd-5-1 branches had the latest BIND pulled up as a security fix.
However, since that pullup, x68k builds on those branches are failing
because the release floppies don't build:
Calculated size of `inst.fs.tmp': 1331200 bytes, 235 inodes
Extent size set to 4096
inst.fs.tmp: 1.3MB (2600 sectors) block size 4096, fragment size 512
using 1 cylinder groups of 1.27MB, 325 blks, 256 inodes.
super-block backups (for fsck -b #) at:
32,nbmakefs: Writing inode 14 (dir), bytes 0 + 512: No space left on device
Populating `inst.fs.tmp'
--- inst.fs ---
*** [inst.fs] Error code 1
1 error
nbmake: stopped in /home/builds/ab/netbsd-5-1/src/distrib/x68k/floppies/ramdisk
--- all-ramdisk ---
*** [all-ramdisk] Error code 2
1 error
nbmake: stopped in /home/builds/ab/netbsd-5-1/src/distrib/x68k/floppies
--- all-floppies ---
*** [all-floppies] Error code 2
1 error
Since x68k builds are NOT failing in -current, I assume this should be
relatively straightforward to deal with, but I don't know anything about
how the builds are put together. Can someone who knows please put
together a tested patch and submit it to pullup-5 at netbsd.org, so that
x68k can be fully supported?
Thanks
+j
--------------030500020800010905040303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi-<br>
<br>
As part of normal release engineering activity, the netbsd-5 and
netbsd-5-1 branches had the latest BIND pulled up as a security
fix. However, since that pullup, x68k builds on those branches are
failing because the release floppies don't build:<br>
<br>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Times; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
font-size: medium;">
<pre style="word-wrap: break-word; white-space: pre-wrap;">Calculated size of `inst.fs.tmp': 1331200 bytes, 235 inodes
Extent size set to 4096
inst.fs.tmp: 1.3MB (2600 sectors) block size 4096, fragment size 512
using 1 cylinder groups of 1.27MB, 325 blks, 256 inodes.
super-block backups (for fsck -b #) at:
32,nbmakefs: Writing inode 14 (dir), bytes 0 + 512: No space left on device
Populating `inst.fs.tmp'
--- inst.fs ---
*** [inst.fs] Error code 1
1 error
nbmake: stopped in /home/builds/ab/netbsd-5-1/src/distrib/x68k/floppies/ramdisk
--- all-ramdisk ---
*** [all-ramdisk] Error code 2
1 error
nbmake: stopped in /home/builds/ab/netbsd-5-1/src/distrib/x68k/floppies
--- all-floppies ---
*** [all-floppies] Error code 2
1 error</pre>
</span><br>
Since x68k builds are NOT failing in -current, I assume this should
be relatively straightforward to deal with, but I don't know
anything about how the builds are put together. Can someone who
knows please put together a tested patch and submit it to pullup-5
at netbsd.org, so that x68k can be fully supported?<br>
<br>
Thanks<br>
+j<br>
<br>
</body>
</html>
--------------030500020800010905040303--