From: Sergey Matyukevich <Sergey_Matyukevich@mentor.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] map_kernel_arch: x86 sub-architectures
Date: Wed, 17 Apr 2013 18:05:25 +0400 [thread overview]
Message-ID: <516EAC25.40109@mentor.com> (raw)
In-Reply-To: <CADkTA4Mrw50x2SXjwpug9QA-VgwpQZrAH6OpbU-F+SB2-G0uPw@mail.gmail.com>
Hello,
>> Suppose we build software for x86 targets on x86 build hosts. There are use-cases
>> when it is not enough to specify x86 as a kernel architecture. It is necessary
>
> What are the details of the use cases ? I've never run into this myself, and
> almost no parts of the kernel build infrastructure differentiates between
> x86 and x86_64 .. so I'm curious to know what is breaking.
So far we observed this problem in two cases:
- build systemtap modules for x86_32 target on x86_64 build hosts
- build virtualbox-guest modules for x86_32 target on x86_64 build hosts
Sergey
next prev parent reply other threads:[~2013-04-17 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 12:10 [PATCH] map_kernel_arch: x86 sub-architectures Sergey Matyukevich
2013-04-17 13:52 ` Bruce Ashfield
2013-04-17 14:05 ` Sergey Matyukevich [this message]
2013-04-17 14:24 ` Bruce Ashfield
2013-04-18 12:34 ` Sergey Matyukevich
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=516EAC25.40109@mentor.com \
--to=sergey_matyukevich@mentor.com \
--cc=bruce.ashfield@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox