On śro, 2011-06-01 at 10:36 +0100, Neil Williams wrote: > On Wed, 01 Jun 2011 11:21:54 +0200 > Marcin Juszkiewicz <[email protected]> wrote:
> > My packages does not require hacking to get cross compiler installed. > > To be fair, the Emdebian ones don't either - but everyone using any > toolchain is going to need libc6-armel-cross and that is where the > problems start. libc6*-armel-cross are provided too. But anything beyond is not. > > Simple "apt-get install gcc-arm-linux-gnueabi" is enough. > > apt-get install g++-arm-linux-gnueabi > probably better.... > ;-) gcc, g++, gfortran, gobjc, gobjc++ is what I provide > > OK, installing extra libraries requires use of dpkg-cross but same > > situation is with current Emdebian ones. > > That's my point. It's not so much the toolchain build that is the > issue, it's the reliance on -cross packages, hence the need to get this > sorted via Multi-Arch. The problem is that we will rather not get cross build dependencies during next 6 months and this is required to have really easy cross compiler packages (gcc-*-armel-cross ones from my toolchain + proper binutils will be enough). Without it we still need to bootstrap cross compiler if want to build on buildd. Once we will get multi-arch headers I will work on getting cross compiler to use them as this will allow users to "easily" install target arch libraries/headers. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1306923429.26188.43.camel@localhost
