Thanks Neil.
Now, gcc-3.4-s390 and gcc-4.1-s390 are done for i386 and building for amd64.
Emdebian toolchain status is:
* gcc-3.4 have been built for
+ Succesful arches: arm mips mipsel powerpc sparc ia64 alpha m68k hppa s390
* gcc-4.1 have been built for
+ Succesful arches: arm mips mipsel powerpc sparc ia64 alpha m68k s390
- Failure arches: hppa
* Compiling amd64 -> x86 cross compiler is known that fails.
----
hppa/gcc-4.1/error.log
/bin/sh ../libtool --tag CXX --tag disable-shared --mode=compile
/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/./gcc/xgcc
-shared-libgcc
-B/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/./gcc
-nostdinc++
-L/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/src
-L/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/src/.libs
-B/usr/hppa-linux-gnu/bin/ -B/usr/hppa-linux-gnu/lib/ -isystem
/usr/hppa-linux-gnu/include -isystem /usr/hppa-linux-gnu/sys-include
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/src/libstdc++-v3/../gcc
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/include
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/src/libstdc++-v3/libsupc++
-g -O2 -D_GNU_SOURCE -fno-implicit-templates -prefer-pic -Wall
-Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-ffunction-sections -fdata-sections -c -o eh_throw.lo
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc
/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/./gcc/xgcc
-shared-libgcc
-B/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/./gcc
-nostdinc++
-L/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/src
-L/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/src/.libs
-B/usr/hppa-linux-gnu/bin/ -B/usr/hppa-linux-gnu/lib/ -isystem
/usr/hppa-linux-gnu/include -isystem /usr/hppa-linux-gnu/sys-include
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/src/libstdc++-v3/../gcc
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/include/hppa-linux-gnu
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/include
-I/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/src/libstdc++-v3/libsupc++
-g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wextra
-Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-ffunction-sections -fdata-sections -c
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc -fPIC -DPIC -o
eh_throw.o
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc: In function 'void
__cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*))':
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:78: error:
unrecognizable insn:
(insn 28 27 29 0 ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:66
(set (reg:DI 105)
(plus:DI (reg:DI 106)
(const_int -5376 [0xffffffffffffeb00]))) -1 (nil)
(expr_list:REG_EQUAL (const_int 5138137972254386944 [0x474e5543432b2b00])
(nil)))
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:78: internal
compiler error: in extract_insn, at recog.c:2084
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
Preprocessed source stored into /tmp/cc9ThNgm.out file, please attach
this to your bugreport.
make[6]: *** [eh_throw.lo] Error 1
make[6]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3/libsupc++'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build/hppa-linux-gnu/libstdc++-v3'
make[3]: *** [all-target-libstdc++-v3] Error 2
make[3]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21/build'
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Error 1
make[1]: Leaving directory
`/home/zumbi/svn/tools/buildcross/trunk/hppa/gcc-4.1-4.1.1-21'
make: *** [stamps/05-build-stamp] Error 2
------
2007/1/13, Neil Williams <[EMAIL PROTECTED]>:
Zumbi's buildcross update has allowed the emdebian toolchains to be
updated. All previous versions in emdebian unstable have migrated to
testing and the new packages have been added to unstable. (When Etch is
released, packages in testing will migrate to stable.)
There is a new script (buildcross-install) in svn/tools/repo/trunk
which handles the inclusion of buildcross binaries into the repository
so future updates will be a lot easier. Getting this working has
required a new permanent directory on the server too -
foo/emdebian/sqlite/ which handles not just the sqlite databases but
also the local apt caches for the relevant architectures.
The presence of the sqlite directory is a hint at the second part of
this update, a new WWW interface to the emdebian repositories will be
available once the site updates.
Initially, only toolchain packages can be searched but the output is
generated from a live sqlite database that is updated by
buildcross-install so the data is always current. This is a big bonus
over packages.d.o which can take several days to complete the changes
resulting from a package upload.
Scripts exist to handle the target packages in the same manner but that
database is currently empty. (I've got a few problems to sort out in
the glibc cross-build before libc6 and tzdata can be uploaded as the
first packages). The target package database will be updated by using
the .changes file passed to dput, although this has been tested it has
not been activated just yet. Once finished, the database will be
updated as soon as a target package is uploaded. Search pages follow
the general layout of a Debian package page with slight differences.
Having live data does make for longer URL's but not impossibly long,
each query requires three pieces of data, the package name, the distro
(testing|unstable) and the architecture.
Scripts are documented and there are README files in relevant locations
- there are a number of outstanding issues and 'gotchas' so please take
time to read the README when going through the scripts. :-)
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
