[LV] Now for another bit of noise , ok any noise ...

Jan-Benedict Glaw jbglaw at lug-owl.de
Tue Mar 10 14:55:07 CET 2009


On Tue, 2009-03-10 23:37:48 +1030, Kim Hawtin <kim.hawtin at adelaide.edu.au> wrote:
> Jan-Benedict Glaw wrote:
> > On Fri, 2009-03-06 10:53:48 +0100, Jan-Benedict Glaw <jbglaw at lug-owl.de> wrote:
> > > I'll send a build receipt and the current set of patches to the list
> > > soon.
> > 
> > Build receipt: You can try to use Maciej's Source RPMs
> > (ftp://ftp.linux-mips.org/pub/linux/mips/people/macro/SRPMS/, take the
> > newest vax-linux-* .src.rpm files and build them).
> > 
> > This is what I use:
> > 
> > Pull GCC Trunk from SVN/GIT, apply the pile of patches I just sent.
> > Pull Binutils HEAD from CVS.
> 
> I checked out all the CVS repo, where do we find the SVN/GIT repo?

...the repo for what exactly?

There is:

  * an official GCC SVN repository.
  * an unofficial GCC GIT repository.
  * an official Binutils CVS repository.

GNU libc isn't interesting for the moment, so what exactly are you
missing? "All the CVS repo" would probably mean Binutils. There is no
(read: no longer since they moved away from it) CVS repository for
GCC, but the SVN (and mirrored GIT) repository. These are documented
http://gcc.gnu.org/svn.html and
http://gcc.gnu.org/ml/gcc/2007-06/msg00001.html

> > make all-gcc
> 
> not sure about which resultant Makefile to use for this one?
> 
> "b-vax-dec-linux/Makefile" seems to be the only Makefile I can find with an "all-gcc" clause.
> 
> $ pwd
> /home/software/linux-vax/toolchain
> $ src/gcc/configure --target vax-linux --prefix ~/usr        --enable-languages=c         --disable-libc\
>          --disable-libmudflap         --disable-libssp        --disable-multilib         --disable-shared\
>           --enable-static         --with-system-zlib
> $ make -f b-vax-dec-linux/Makefile all-gcc

Don't supply a Makefile here. `configure' should have generated one in
the current directory (which officially shouldn't contain the sources,
but it'll probably work most of the time.)

> when I run that i get the following;
> 
> ...
> make  all-recursive
> make[2]: Entering directory `/home/software/linux-vax/toolchain/ld'
> Making all in po
> make[3]: Entering directory `/home/software/linux-vax/toolchain/ld/po'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/software/linux-vax/toolchain/ld/po'
> make[3]: Entering directory `/home/software/linux-vax/toolchain/ld'
> make[3]: Leaving directory `/home/software/linux-vax/toolchain/ld'
> make[2]: Leaving directory `/home/software/linux-vax/toolchain/ld'
> make[1]: Leaving directory `/home/software/linux-vax/toolchain/ld'
> /bin/sh: line 1: cd: ../src: No such file or directory
> make[1]: Entering directory `/home/software/linux-vax/toolchain/gcc'
> cd ../src/gcc && autoheader
> /bin/sh: line 1: autoheader: command not found
> make[1]: *** [../src/gcc/cstamp-h.in] Error 127
> make[1]: Leaving directory `/home/software/linux-vax/toolchain/gcc'
> make: *** [all-gcc] Error 2
> 
> # apt-get install autoconf2.13
> solves that problem, then ...
> 
> make[2]: Entering directory `/home/software/linux-vax/toolchain/gcc/ch'
> gcc -c -DCROSS_COMPILE -DIN_GCC   -g -O2     -I. -I.. -I../../src/gcc/ch -I../../src/gcc/ch/.. -I../../src/gcc/ch/../config -I../../src/gcc/ch/../../include 
> ../../src/gcc/ch/parse.c
> 
> 8<
> 
> gcc -c -DCROSS_COMPILE -DIN_GCC   -g -O2     -I. -I.. -I../../src/gcc/ch -I../../src/gcc/ch/.. -I../../src/gcc/ch/../config -I../../src/gcc/ch/../../include 
> ../../src/gcc/ch/loop.c
> ../../src/gcc/ch/loop.c:321:8: missing terminating " character
> ../../src/gcc/ch/loop.c:322:38: missing terminating " character
> make[2]: *** [loop.o] Error 1
> make[2]: Leaving directory `/home/software/linux-vax/toolchain/gcc/ch'
> make[1]: *** [cc1chill] Error 2
> make[1]: Leaving directory `/home/software/linux-vax/toolchain/gcc'
> make: *** [all-gcc] Error 2
> 
> > make install-gcc
> > 
> > 
> > I'd probably push my GCC repo somewhere, too...
> 
> praps I need to get your SVN/GIT updates also ?

You need:
  * Binutils from CVS. (http://sourceware.org/binutils/)
  * GCC from either SVN (http://gcc.gnu.org/svn.html) or GIT
    (http://gcc.gnu.org/ml/gcc/2007-06/msg00001.html)
  * The patches to GCC I posted to the list.

You should put the two source trees into one directory
(~you/vax-stuff/source/gcc and
~you/vax-stuff/source/src) and build within another
directory (rm -rf ~you/vax-stuff/build; mkdir -p
~you/vax-stuff/build/binutils ~you/vax-stuff/build/binutils) and build
only within there:

$ cd ~you/vax-stuff/build/binutils
$ ~you/vax-stuff/source/src/configure --target vax-linux ...
$ make all-binutils all-ld all-gas
$ make install-binutils install-ld install-gas
$ cd ~you/vax-stuff/build/gcc
$ ~you/vax-stiff/source/gcc/configure --target vax-linux ...
$ make all-gcc
$ make install-gcc

Do not forget to apply the patches before building, of course.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw at lug-owl.de              +49-172-7608481
Signature of:              Alles sollte so einfach wie möglich gemacht sein.
the second  :                          Aber nicht einfacher.  (Einstein)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lug-owl.de/pipermail/vax-linux/attachments/20090310/b2250e82/attachment.pgp>
-------------- next part --------------
_______________________________________________
Linux-Vax mailing list
Linux-Vax at mail.pergamentum.com
http://mail.pergamentum.com/mailman/listinfo/linux-vax


More information about the Vax-linux mailing list