From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v3] xtensa: add support for the Xtensa architecture
Date: Fri, 09 Nov 2012 16:50:21 -0800 [thread overview]
Message-ID: <509DA4CD.5000904@zankel.net> (raw)
In-Reply-To: <509DA1F4.7010009@mind.be>
HI Arnout,
On 11/09/2012 04:38 PM, Arnout Vandecappelle wrote:
> On 11/10/12 01:19, Chris Zankel wrote:
>> diff --git a/package/autoconf/Config.in b/package/autoconf/Config.in
>> index c304572..3622f3d 100644
>> --- a/package/autoconf/Config.in
>> +++ b/package/autoconf/Config.in
>> @@ -1,6 +1,7 @@
>> config BR2_PACKAGE_AUTOCONF
>> bool "autoconf"
>> - depends on !(BR2_avr32 || BR2_bfin || BR2_sh2 || BR2_sh2a || BR2_sh3 || BR2_sh3eb || BR2_sh64)
>> + depends on !(BR2_avr32 || BR2_bfin || BR2_sh2 || BR2_sh2a || BR2_sh3)
>> + depends on !(BR2_sh3eb || BR2_sh64 || BR2_xtensa)
>> select BR2_PACKAGE_PERL
>> help
>> Extensible program for developing configure scripts. These
> Actually, these dependencies can be removed again, because perl no longer
> depends on host-qemu. I'll post a patch removing them.
So, I guess that breaks my patch ;-)
> And anyway, host-qemu exists for xtensa, no?
Yes, there is a version of Qemu that was done my Max, but it might
require a different processor configuration than what's in the toolchain
by default.
-Chris
prev parent reply other threads:[~2012-11-10 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 0:19 [Buildroot] [PATCH 1/2 v3] xtensa: add support for the Xtensa architecture Chris Zankel
2012-11-10 0:38 ` Arnout Vandecappelle
2012-11-10 0:50 ` Chris Zankel [this message]
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=509DA4CD.5000904@zankel.net \
--to=chris@zankel.net \
--cc=buildroot@busybox.net \
/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