Re: how to properly enable multilib builds?

2011-08-30 Thread Christian Robottom Reis
Matthias, does the solution below work for you? On Tue, Aug 23, 2011 at 03:03:03PM +0100, Andrew Stubbs wrote: > On 22/08/11 11:33, Matthias Klose wrote: > >the current gcc-4.6 packages build for both softfp and hard, so that the > >armel > >and (not yet existing) armhf packages can be installed

Re: how to properly enable multilib builds?

2011-08-23 Thread Andrew Stubbs
On 22/08/11 11:33, Matthias Klose wrote: the current gcc-4.6 packages build for both softfp and hard, so that the armel and (not yet existing) armhf packages can be installed together in the system. To enable multilib, I currently use the rather complicated arm-multilib.diff, which works, but doe

Re: how to properly enable multilib builds?

2011-08-23 Thread Andrew Stubbs
On 22/08/11 11:33, Matthias Klose wrote: If I understand the code correctly, this comes from the hard setting of MULTILIB_DEFAULTS in the arm target. If you look at mips, you see #ifndef MULTILIB_DEFAULTS #define MULTILIB_DEFAULTS \ { MULTILIB_ENDIAN_DEFAULT, MULTILIB_ISA_DEFAULT, MULTILIB_

how to properly enable multilib builds?

2011-08-22 Thread Matthias Klose
Hi, the current gcc-4.6 packages build for both softfp and hard, so that the armel and (not yet existing) armhf packages can be installed together in the system. To enable multilib, I currently use the rather complicated arm-multilib.diff, which works, but doesn't seem to be correct. With the much