Mike Frysinger wrote:
> On Wednesday 21 October 2009 07:34:18 Michael Haubenwallner wrote:
>> Mike Frysinger wrote:
>>> On Tuesday 20 October 2009 09:06:29 Michael Haubenwallner wrote:
As I'm building the toolchain myself too, I configure it with the
32bit host triplet on each platform,
On Wednesday 21 October 2009 07:34:18 Michael Haubenwallner wrote:
> Mike Frysinger wrote:
> > On Tuesday 20 October 2009 09:06:29 Michael Haubenwallner wrote:
> >> As I'm building the toolchain myself too, I configure it with the
> >> 32bit host triplet on each platform, usually disabling multilib
Mike Frysinger wrote:
> On Tuesday 20 October 2009 09:06:29 Michael Haubenwallner wrote:
>> As I'm building the toolchain myself too, I configure it with the
>> 32bit host triplet on each platform, usually disabling multilib.
>
> this doesnt make any sense to me
What exactly doesn't make sense t
On Tuesday 20 October 2009 09:06:29 Michael Haubenwallner wrote:
> As I'm building the toolchain myself too, I configure it with the
> 32bit host triplet on each platform, usually disabling multilib.
this doesnt make any sense to me
> This simply works for ppc-aix, hppa-hpux, ia64-hpux, sparc-sol
Michael Haubenwallner schrieb:
> Isn't the intention of multilib to have a new (64bit) system
> be compatible with the corresponding old (32bit) system?
>
> Please comment, thank you!
> /haubi/
If you have a 64bit system, the default should be 64bit, both for libs and for
binaries. The
additiona
Hi devs,
while there is the appreciated multiple ABI portage support going on,
a thought on the intentions of the multilib profiles.
Some background:
I do have to support building an older, but still maintained large
application software, that simply does not work when built as 64bit.
As it does
