Re: gcc-4.1 cross-build omission
Yes - i checked it out.
gcc-4.1-arm-linux-gnu depends on gcc-4.1-arm-linux-gnu-base, so my
guess was wrong.
libgcc1-arm-cross is set to right depency on gcc-4.1*-21*. Checked.
BTW, i started today to build all toolchains.
2006/12/18, Neil Williams <firstname.lastname@example.org>:
On Mon, 18 Dec 2006 20:56:07 +0100
"Hector Oron" <email@example.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
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
I've removed the offending files and replaced them with the *-19_*
versions from testing. Everything is fine now, at least AFAICT at this
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.