On Tue, Mar 29, 2011 at 4:31 PM, Diane Holt holt.diane@gmail.com wrote:
Thanks, Michael, that's the sort of thing I was hoping for. And it almost worked :)
A great thing about Debian/Ubuntu is 'apt-get build-dep'. On recent systems at least you can run 'apt-get build-dep gcc-snapshot' and have all of the build dependencies downloaded and instaled.
The Dapper desktop VMWare appliance I got from Ubuntu didn't have these needed packages: bison, curl, flex, and texinfo. So I needed to install them.
Without curl, the downloads won't happen.
Without texinfo, makeinfo isn't found, which comes out looking like a warning, but it does fail the build.
Without bison and flex, you get a funky build failure for binutils -- it tries to link both sysinfo.o and syslex.o into sysinfo (which results in two main()'s being defined).
I needed to get and build tar-1.22, since your tar command uses -a, which the tar that comes with Dapper doesn't have. (Not sure when it was introduced, so I just went with the version that was on my lucid, since that one has it.)
There is no binutils_2.21.0.20110302.orig.tar.gz -- it's binutils_2.21.0.20110322.orig.tar.gz
There used to be on 02, but Natty marches on very quickly. I've changed the local version of my script to use binutils 2.21 from the FSF.
Needed to get and build gmp, mpfr, and mpc, and add --with-gmp, --with-mpfr, and --with-mpc to GCCFLAGS.
The build got pretty far, but eventually failed with:
make[4]: Entering directory `/home/ubuntu/work/build/gcc/libiberty/testsuite' make[4]: Nothing to be done for `install'. make[4]: Leaving directory `/home/ubuntu/work/build/gcc/libiberty/testsuite' make[3]: Leaving directory `/home/ubuntu/work/build/gcc/libiberty' /bin/sh: line 3: cd: arm-linux-gnueabi/libstdc++-v3: No such file or directory make[2]: *** [install-target-libstdc++-v3] Error 1 make[2]: Leaving directory `/home/ubuntu/work/build/gcc' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/ubuntu/work/build/gcc' make: *** [stamp/gcc-install] Error 2
Any idea what I need to do about that? (I tried adding --enable-languages=c,c++ but that didn't help.)
Not sure there. Could you capture the output from configure and send it through?
-- Michael