Subject: Re: toolchain on current
To: emanuel stiebler <emu@ecubics.com>
From: Brian Chase <vaxzilla@jarai.org>
List: port-vax
Date: 12/26/2003 16:40:08
On Fri, 26 Dec 2003, emanuel stiebler wrote:

> Still trying to compile current on vax.
>
> Now I'm stuck at:
>
> #   compile  libiberty/argv.o
> /usr/tools/bin/vax--netbsdelf-gcc -O2  -Werror    -DHAVE_CONFIG_H
> -I/usr/src/gnu/lib/libiberty -I/usr/src/gnu/dist/binutils/include
> -nostdinc -isystem /usr/dest/usr/include -c
> /usr/src/gnu/dist/toolchain/libiberty/argv.c -o argv.o.tmp
> /usr/src/gnu/dist/toolchain/libiberty/argv.c: In function `buildargv':
> /usr/src/gnu/dist/toolchain/libiberty/argv.c:208: argument `input'
> doesn't match prototype
> /usr/src/gnu/dist/binutils/include/libiberty.h:54: prototype declaration
>
> *** Failed target:  argv.o
> *** Failed command: /usr/tools/bin/vax--netbsdelf-gcc -O2 -Werror
> -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libiberty
> -I/usr/src/gnu/dist/binutils/include -nostdinc -isystem
> /usr/dest/usr/include -c /usr/src/gnu/dist/toolchain/libiberty/argv.c -o
> argv.o.tmp
> *** Error code 1
>
>
> Ideas ?

I've not run into that one just yet, but then the "-current" I'm working
with is about a week and a half old at this point.  If you've not
already done so, my suggestion would be to run a cvs update to see if
there's any newer revision of that argv.c file which might be fixed.

As a matter of curiosity, are you compiling the -current sources with
a 1.6.1 install?  I'm using a cross-compiled -current which has been
working alright for me though there's still something wrong with the
pic(1) program that causes it to crash.

-brian.