...are available at:
http://ex.seabright.co.nz/build/gcc-linaro-4.5+bzr99315/
I've also finished reference builds of FSF GCC 4.4.4, 4.5.0, and
4.5.1. According to the GCC testsuite, there are no regressions
between the Linaro and FSF branches and in some ways we're a bit
better:
On x86_64 for F
Wookey wrote on 08/02/2010 10:40:23 PM:
> Hope that's not considered rude, Ulrich. (great bit of work capturing
> all that good stuff - thank you).
No problem, that's fine with me. Thanks!
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand | Phone: +49-7031/16-3
Andrew Stubbs wrote:
> I suggest teaching the kernel to rewrite that path when it finds a
> non-existent interpreter. Presumably the kernel can "know" what
> multiarch corresponds to the traditional ABI for any given ELF flags.
The problem with this is that is this brings namespace policy into
t
On 02/08/10 20:16, Ulrich Weigand wrote:
> Now this point is where the suggestion to use something like a bind mount
> on startup comes in. That way, there would be no violation of the
> multiarch rules, because /lib/ld.so.1 would not be part of any package,
> and in fact not even part of any file
Results are available here:
http://ex.seabright.co.nz/build/gcc-linaro-4.5-99310/
Colourised versions of the build logs are available at:
http://ex.seabright.co.nz/helpers/testlog/gcc-linaro-4.5-99310/logs/i686-lucid-cbuild1-scorpius/gcc-test.txt
http://ex.seabright.co.nz/helpers/testlog/gcc
