Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: gcc atomic instruction support for armv5te
Date: Mon, 15 Mar 2010 12:37:49 +0100	[thread overview]
Message-ID: <4B9E1C0D.5050806@dresearch.de> (raw)

As mentioned before i try to create a recipe for rsyslog.

Now i hit the next big problem. The last item at
http://www.rsyslog.com/doc-build_from_repo.html says that

"The availability of atomic instructions is vital for rsyslog"

The gcc version 4.3.3 which is used for armv5te by default
misses this. :(

Is there a newer gcc version with atomic instruction for armv5te
machines available/tested? I heard rumors that 4.4.3 shell
have it?

Steffen




             reply	other threads:[~2010-03-15 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 11:37 Steffen Sledz [this message]
2010-03-21  8:12 ` gcc atomic instruction support for armv5te Khem Raj
2010-03-22  7:48   ` Steffen Sledz
2010-03-22 17:53     ` Khem Raj

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=4B9E1C0D.5050806@dresearch.de \
    --to=sledz@dresearch.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox