Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] protobuf: fix build for some unsupported architectures
Date: Fri, 9 May 2014 08:11:43 +0300	[thread overview]
Message-ID: <20140509051143.GP3861@tarshish> (raw)
In-Reply-To: <87k39waqoh.fsf@dell.be.48ers.dk>

Hi Peter,

On Thu, May 08, 2014 at 11:47:26PM +0200, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> 
>  >> So it looks like we need to tweak the arch list a bit.
> 
>  > The generic internal atomic ops implementation (which is used to fix
>  > powerpc build) is using the gcc feature of "memory model aware atomic
>  > operations".  These were introduced in gcc 4.7, while the Sourcery
>  > toolchain is gcc 4.5. I don't see a straightforward way to depend on
>  > gcc version like we have for kernel headers. Any ideas?
> 
> Hmm, not really - No :/ So that makes the patch less interesting :/

OK. So we are only left with x86, ARM and MIPS.

BTW, how do we handle host architecture dependencies? This is applicable to 
http://autobuild.buildroot.net/results/20b/20b1d279b12176c0dcbaa8b5f170f6c8a55eb6da/ 
(PowerPC host).

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2014-05-09  5:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 13:06 [Buildroot] [PATCH v3] protobuf: fix build for some unsupported architectures Baruch Siach
2014-05-08 19:46 ` Peter Korsgaard
2014-05-08 20:48   ` Baruch Siach
2014-05-08 21:47     ` Peter Korsgaard
2014-05-09  5:11       ` Baruch Siach [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=20140509051143.GP3861@tarshish \
    --to=baruch@tkos.co.il \
    --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