headers
Matthias Scheler | 4 Apr 2005 19:54
Picon

Status of NetBSD-current vax


	Hello,

cross building NetBSD-current vax on a NetBSD 2.0.2 system fails like this:

#   compile  identd/identd.o
/scratch/tron/toolsdir/bin/vax--netbsdelf-gcc -O2  -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wno-traditional -Wno-uninitialized
-Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -std=c99  -Werror  
-I/src/NetBSD-current/src/sys/dist/ipf -DWITH_IPF -DWITH_PF  -nostdinc -isystem
/scratch/tron/destdir/usr/include  -c    /src/NetBSD-current/src/libexec/identd/identd.c
cc1: unknown C standard `c99'

*** Failed target:  identd.o

Is this a known issue?

	Kind regards

P.S. Please copy replies to me because I'm not subscribed to this list.

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/
Permalink | Reply | 4 comments |
headers
Michael L. Hitch | 5 Apr 2005 04:17
Picon

Re: Status of NetBSD-current vax

On Mon, 4 Apr 2005, Matthias Scheler wrote:

> cross building NetBSD-current vax on a NetBSD 2.0.2 system fails like this:
>
> #   compile  identd/identd.o
> /scratch/tron/toolsdir/bin/vax--netbsdelf-gcc -O2  -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wno-traditional -Wno-uninitialized
-Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -std=c99  -Werror  
-I/src/NetBSD-current/src/sys/dist/ipf -DWITH_IPF -DWITH_PF  -nostdinc -isystem
/scratch/tron/destdir/usr/include  -c    /src/NetBSD-current/src/libexec/identd/identd.c
> cc1: unknown C standard `c99'
>
> *** Failed target:  identd.o
>
> Is this a known issue?

  I'm not sure if it's a "known" issue, but it appears to be due to WARNS
being set to 4 in the Makefile, which adds the -std=c99 option - which I
would presume is not supported by GCC 2.95 used on the vax.

--
Michael L. Hitch			mhitch <at> NetBSD.org
Permalink | Reply | 3 comments |
headers
Matthias Scheler | 5 Apr 2005 11:22
Picon

Re: Status of NetBSD-current vax

On Mon, Apr 04, 2005 at 08:17:30PM -0600, Michael L. Hitch wrote:
> > cross building NetBSD-current vax on a NetBSD 2.0.2 system fails like this:
> >
> > #   compile  identd/identd.o
> > /scratch/tron/toolsdir/bin/vax--netbsdelf-gcc -O2  -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wno-traditional -Wno-uninitialized
-Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -std=c99  -Werror  
-I/src/NetBSD-current/src/sys/dist/ipf -DWITH_IPF -DWITH_PF  -nostdinc -isystem
/scratch/tron/destdir/usr/include  -c    /src/NetBSD-current/src/libexec/identd/identd.c
> > cc1: unknown C standard `c99'
> >
> > *** Failed target:  identd.o
> >
> > Is this a known issue?
> 
>   I'm not sure if it's a "known" issue, but it appears to be due to WARNS
> being set to 4 in the Makefile, which adds the -std=c99 option - which I
> would presume is not supported by GCC 2.95 used on the vax.

Ah, that's where the flag comes from. I'll try this patch later:

Index: bsd.sys.mk
===================================================================
RCS file: /cvsroot/src/share/mk/bsd.sys.mk,v
retrieving revision 1.115
diff -u -r1.115 bsd.sys.mk
--- bsd.sys.mk  20 Feb 2005 01:31:44 -0000      1.115
+++ bsd.sys.mk  5 Apr 2005 09:22:23 -0000
 <at>  <at>  -26,7 +26,7  <at>  <at> 
 .if ${WARNS} > 2
(Continue reading)

Permalink | Reply | 2 comments |
headers
James Chacon | 5 Apr 2005 18:17
Picon

Re: Status of NetBSD-current vax

On Tue, Apr 05, 2005 at 10:22:59AM +0100, Matthias Scheler wrote:
> On Mon, Apr 04, 2005 at 08:17:30PM -0600, Michael L. Hitch wrote:
> > > cross building NetBSD-current vax on a NetBSD 2.0.2 system fails like this:
> > >
> > > #   compile  identd/identd.o
> > > /scratch/tron/toolsdir/bin/vax--netbsdelf-gcc -O2  -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wno-traditional -Wno-uninitialized
-Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -std=c99  -Werror  
-I/src/NetBSD-current/src/sys/dist/ipf -DWITH_IPF -DWITH_PF  -nostdinc -isystem
/scratch/tron/destdir/usr/include  -c    /src/NetBSD-current/src/libexec/identd/identd.c
> > > cc1: unknown C standard `c99'
> > >
> > > *** Failed target:  identd.o
> > >
> > > Is this a known issue?
> > 
> >   I'm not sure if it's a "known" issue, but it appears to be due to WARNS
> > being set to 4 in the Makefile, which adds the -std=c99 option - which I
> > would presume is not supported by GCC 2.95 used on the vax.
> 
> Ah, that's where the flag comes from. I'll try this patch later:

No...The identd Makefile should be patched to just use WARNS=3

*nothing* else in the tree currently uses WARNS=4 and special casing the
.mk file just means it has to be found later if/when vax updates it's gcc.

If it's gonna be special cased, do it in the identd Makefile.

James
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matthias Scheler | 5 Apr 2005 18:55
Picon

Re: Status of NetBSD-current vax

On Tue, Apr 05, 2005 at 11:17:09AM -0500, James Chacon wrote:
> > Ah, that's where the flag comes from. I'll try this patch later:
> 
> No...The identd Makefile should be patched to just use WARNS=3

That will fix the current problem. But as soon as the next program is
compiled with "WARNS=4" the problem will occur again.

> *nothing* else in the tree currently uses WARNS=4 and special casing the
> .mk file just means it has to be found later if/when vax updates it's gcc.

Yes, but that is *one* single place no matter how many programs will
use "WARNS=4" in future. And I have documented this work arround
in "src/doc/HACKS" at the same place where all the other vax specific
gcc hacks are listed.

> If it's gonna be special cased, do it in the identd Makefile.

I'm sorry but I think that's completely the wrong approach.

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/
Permalink | Reply | 0 comments |
headers
andreas | 7 Apr 2005 16:44
Picon
Favicon

netbooot/boot broken?


Hello,

I'm trying to boot netbsd on a VAXstation 2000 over the network.
I read the install and netboot pages and followed the instructions
but got stuck.

The vax sends a mop request, loads the file from the mopd, and then
just repeats this after a few seconds.

Since there was not a single additional packet on the network besides
the repeating requests & file-loads I suspected the boot-file to be
the problem. I used this one (and the versions from netbsd 1.6 / 1.62):

   ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/vax/installation/netboot/boot

The file utility claims this to be an ELF binary, which I found rather 
odd. Feeding the vax a similar(?) binary (which is not ELF) from openbsd 
leads to its execution and I see RARP & RPC requests on the wire:

   ftp://ftp.openbsd.org/pub/OpenBSD/3.6/vax/boot.mop

Am I being very stupid and using the wrong file? Did somebody use the 
first mentioned (netbsd 2.0) boot-file and it executed properly?

Any hints welcome!

TIA,
andreas
(Continue reading)

Permalink | Reply | 2 comments |
headers
John Tate | 7 Apr 2005 17:23
Picon

Installation Help

Hey,

I am pretty new to the VAX hardware, but I am pretty good with Linux
and BSD (I run a OpenBSD machine for my main server) and I have got my
hands on a VAXStation 3100 M38, which is alien hardware to me. I have
set it up so I can talk to it via serial port, however it gives me
some weird bootloader 'KA42B' I don't even understand (references?).
Nonetheless I was hopeing someone would be able to help me install
NetBSD on it via the floppy drive it has. If I figure out how to boot
it and then do an install across NFS or just FTP straight from the net
I should be right, right?

Yours,
John Tate
--

-- 
John "Rockstar" Tate
Mobile: 0413 348 815 (Yep, old number, but I have a new phone)

Do you want a badass email that has fully customisable filters, an
awesome spam block, an easy to use interface that totally kicks arse?
AND MORE (see www.gmail.com)
If you like the sound of this ask me, a gmailer for an invite.
This endorsement messege was written by John Tate, who recieves no
money from Google Corp for bearing it on his signitaure.

http://kintarowins.deviantart.com/
Permalink | Reply | 5 comments |
headers
Georg Schwarz | 7 Apr 2005 17:43
Picon
Favicon

Re: Installation Help

> I am pretty new to the VAX hardware, but I am pretty good with Linux
> and BSD (I run a OpenBSD machine for my main server) and I have got my
> hands on a VAXStation 3100 M38, which is alien hardware to me. I have
> set it up so I can talk to it via serial port, however it gives me
> some weird bootloader 'KA42B' I don't even understand (references?).
> Nonetheless I was hopeing someone would be able to help me install
> NetBSD on it via the floppy drive it has. If I figure out how to boot
> it and then do an install across NFS or just FTP straight from the net
> I should be right, right?

At least this worked for me a couple of years back (using local monitor
and keyboard, not serial console).
I remeber however that it was quite difficult top find a working floppy
image. I think newer releases no longer feature an image that fits on a
floppy disk, although the docs still claim so.
As an alternative, you might prepare a suitable SCSI disk elsewhere
(preferably some other NetBSD system), extract the essential Vax binary
tarfiles and put the correct bootloader onto it. That should boot.
This is how I recently installed NetBSD 2.0 to my vax, using a DECstation
to prepare the SCSI disk.

--

-- 
Georg Schwarz    http://home.pages.de/~schwarz/
 georg.schwarz <at> freenet.de  +49 178 8545053
Permalink | Reply | 0 comments |
headers
Johnny Billquist | 7 Apr 2005 18:00
Picon
Picon

Re: netbooot/boot broken?

On Thu, 7 Apr 2005 andreas <at> bunten.de wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hello,
>
> I'm trying to boot netbsd on a VAXstation 2000 over the network.
> I read the install and netboot pages and followed the instructions
> but got stuck.
>
> The vax sends a mop request, loads the file from the mopd, and then
> just repeats this after a few seconds.
>
> Since there was not a single additional packet on the network besides
> the repeating requests & file-loads I suspected the boot-file to be
> the problem. I used this one (and the versions from netbsd 1.6 / 1.62):
>
>   ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/vax/installation/netboot/boot
>
> The file utility claims this to be an ELF binary, which I found rather odd.
> Feeding the vax a similar(?) binary (which is not ELF) from openbsd leads to
> its execution and I see RARP & RPC requests on the wire:
>
>   ftp://ftp.openbsd.org/pub/OpenBSD/3.6/vax/boot.mop
>
> Am I being very stupid and using the wrong file? Did somebody use the first
> mentioned (netbsd 2.0) boot-file and it executed properly?

I think the problem is that the MOP loader don't really feed ELF images
correctly across the net, and thus you're not getting a good boot image to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Johnny Billquist | 7 Apr 2005 18:03
Picon
Picon

Re: Installation Help

On Fri, 8 Apr 2005, John Tate wrote:

> Hey,
>
> I am pretty new to the VAX hardware, but I am pretty good with Linux
> and BSD (I run a OpenBSD machine for my main server) and I have got my
> hands on a VAXStation 3100 M38, which is alien hardware to me.

Okay...

> I have
> set it up so I can talk to it via serial port, however it gives me
> some weird bootloader 'KA42B' I don't even understand (references?).

KA42B is actually an identification of the CPU you have. You should get
some additional stuff printed out, and you should be able to abort the
booting at that point to get the "chevron" prompt where you can do some
things.

> Nonetheless I was hopeing someone would be able to help me install
> NetBSD on it via the floppy drive it has. If I figure out how to boot
> it and then do an install across NFS or just FTP straight from the net
> I should be right, right?

I think the floppy install isn't working. The best bet is network booting,
but I seem to remember some problems with that as well. I have an "old"
version of the boot program still around because of this, so that I can do
the netboot.

	Johnny
(Continue reading)

Permalink | Reply | 2 comments |

Gmane