From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: fix sparc64 compile, set the correct instruction-set
Date: Tue, 3 Nov 2015 22:25:32 +0100 [thread overview]
Message-ID: <20151103212531.GI21428@waldemar-brodkorb.de> (raw)
In-Reply-To: <20151103220543.06ed88e9@free-electrons.com>
Hi,
Thomas Petazzoni wrote,
> Dear Waldemar Brodkorb,
>
> On Tue, 3 Nov 2015 22:03:14 +0100, Waldemar Brodkorb wrote:
>
> > +ifeq ($(BR2_sparc64),y)
> > +BOOST_OPTS += architecture=sparc instruction-set=ultrasparc
> > +endif
>
> We're not setting architecture= nor instruction-set= for any other
> architecture. Should we do so ?
>
> Should the instruction-set be set to BR2_GCC_TARGET_TUNE ?
You mean BR2_GCC_TARGET_CPU? No, because leon3 is not set in boost.
To do minimal damage to other architectures, I would just
set it for sparc/sparc64. The boost architecture does not always
match the buildroot architecture name. (f.e. ppc is power)
I think 0003-Remove-bogus-c3-cpu-varant-for-SPARC.patch could be
removed, when a correct setting is used for sparc32.
best regards
Waldemar
next prev parent reply other threads:[~2015-11-03 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 21:03 [Buildroot] [PATCH] boost: fix sparc64 compile, set the correct instruction-set Waldemar Brodkorb
2015-11-03 21:05 ` Thomas Petazzoni
2015-11-03 21:25 ` Waldemar Brodkorb [this message]
2015-11-08 14:02 ` Thomas Petazzoni
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=20151103212531.GI21428@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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