All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] conf/machine: Add x86_64 machine.
Date: Mon, 21 Dec 2009 10:06:08 +0100	[thread overview]
Message-ID: <hgndpv$i9t$1@ger.gmane.org> (raw)
In-Reply-To: <19c1b8a90912201813i54c9e5d9r6e1545a3a9106f74@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21-12-09 03:13, Khem Raj wrote:
> On Sun, Dec 20, 2009 at 11:04 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
>>> On Thu, 2009-12-17 at 12:07 -0800, Khem Raj wrote:
>>>>
>>>> * This is not supporting multilib
>>>> * Only 64-bit userspace can be built.
>>>>
>>>> --- /dev/null
>>>> +++ b/conf/machine/include/tune-x86_64.inc
>>>> @@ -0,0 +1,4 @@
>>>> +TARGET_CC_ARCH = "-mtune=generic"
>>>> +BASE_PACKAGE_ARCH = "x86_64"
>>>> +FEED_ARCH = "x86_64"
>>>> +PACKAGE_EXTRA_ARCHS += "x86 i386 i486 i586 i686"
>>
>> NAK! Don't use underscores in machine names since it's what bitbake is using
>> to mark overrides. I fell into that trap twice already :(
>>
>> Also, please explain to me what you plan to do with 'FEED_ARCH'.
> 
> I was thinking of using amd64 but ARCH has to be
> x86_64 at least for gcc so I think we can not avoid
> it. may be we should make bitbake ignore certain
> overrides like x86_64 if thats possible at all.

We re-write arch already for kernel recipes, so why can't we do the same
for gcc?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLLzqAMkyGM64RGpERAtuHAJ9YxU54qCR7lAiUbjkxRqBi7ISycACeOkMG
yrR9wiUNLhHC4im/yz7j92s=
=Lk4J
-----END PGP SIGNATURE-----




  reply	other threads:[~2009-12-21  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 20:07 [PATCH] conf/machine: Add x86_64 machine Khem Raj
2009-12-17 20:22 ` Phil Blundell
2009-12-17 20:30   ` Khem Raj
2009-12-18  9:41   ` Marcin Juszkiewicz
2009-12-20 19:04   ` Koen Kooi
2009-12-21  2:13     ` Khem Raj
2009-12-21  9:06       ` Koen Kooi [this message]
2009-12-21 17:42         ` Khem Raj
2009-12-21 18:33       ` Phil Blundell
2009-12-17 21:11 ` Philip Balister
2009-12-17 21:25   ` Khem Raj
2009-12-18 14:07 ` Paul Menzel

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='hgndpv$i9t$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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.