On Mon, 18 Dec 2006 20:56:07 +0100
"Hector Oron" <hector.oron@gmail.com> wrote:
> Hello Neil,
>
> Sorry, but i have been very busy lately and I had also some trouble
> with my connectivity to the net.
>
> This is a guess, i believe gcc-4.1-arm-linux-gnu depends on
> gcc-4.1-base (it should depend on gcc-4.1-arm-base).
No, that's not it. I worked around the problem last night and only now
have I had time yet to check the full reasons. To identify the problem,
I allowed apt to remove the amd64 emdebian unstable toolchain and then
installed the toolchain packages I built locally using emchain. Running
apt-get upgrade now shows which packages are actually wrong in the
repository:
libgcc1-arm-cross libstdc++6-4.1-dbg-arm-cross libstdc++6-arm-cross
The packages that do depend on gcc-4.1-base instead of
gcc-4.1-arm-linux-gnu-base are/were:
pool/main/g/gcc-4.1/libgcc1-arm-cross_4.1.1-20_all.deb
pool/main/g/gcc-4.1/libstdc++6-4.1-dbg-arm-cross_4.1.1-20_all.deb
pool/main/g/gcc-4.1/libstdc++6-arm-cross_4.1.1-20_all.deb
I've removed the offending files and replaced them with the *-19_*
versions from testing. Everything is fine now, at least AFAICT at this
end.
I'm going to try a build of *-21_* in due course. This should ensure
that no *-20_* files remain (these seem to be the focus of problems -
not surprising when *-20_* FTBFS on arm) as well as replacing all
*-19_* files in our unstable dist, leaving 19 for testing.
> I have just realize that we have gcc-4.1-arm-linux-gnu-base. I believe
> we should have gcc-4.1-base-arm-linux. Am I right?
No, -arm-linux-gnu-base is correct, for whatever reason.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/