All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Pidancet <julian.pidancet@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Introduce biarch DISTRO_FEATURE
Date: Thu, 10 Nov 2011 13:43:02 +0000	[thread overview]
Message-ID: <j9ghc8$ps7$1@dough.gmane.org> (raw)
In-Reply-To: <1320784166.10843.109.camel@ted>

On 11/08/11 20:29, Richard Purdie wrote:
> 
> I'm left wondering how useful the resulting compiler is to most users.
> In most cases a user would expect full libc support and hence this is
> likely to confuse them. I do appreciate people do have usecases for a
> compiler that can handle the other bit format though.
> 

Standard linux distros out there like debian or gentoo already ship a
biarch gcc per default. It wouldn't seem odd to me if OE had an option
to enable the generation of a biarch compiler.

> I think my biggest worry is the "--enable-targets=all" option which may
> or may not enable things we might not want enabled. I've not had a
> chance to go and look at gcc and convince myself that piece is safe. The
> other pieces looked less worrying.
> 

In the patch, the --enable-targets=all is only active in the x86 case. I
did not find any other way of enabling both -m32 and -m64 switches in gcc.

I've been successfully using this patch to generate a complete x86 32bit
distro with a 64bit Xen hypervisor (I believe the result would have been
the same if I tried to compile a 64bit linux kernel). I did not have any
issues with it so far.

Cheers,

-- 
Julian




  reply	other threads:[~2011-11-10 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  1:18 [PATCH] Introduce biarch DISTRO_FEATURE Julian Pidancet
2011-10-26  2:09 ` McClintock Matthew-B29882
2011-11-07 23:14   ` Julian Pidancet
2011-11-08 19:50     ` McClintock Matthew-B29882
2011-11-08 20:29     ` Richard Purdie
2011-11-10 13:43       ` Julian Pidancet [this message]
2011-11-18 20:39         ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='j9ghc8$ps7$1@dough.gmane.org' \
    --to=julian.pidancet@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.