From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] erlang: use libatomic_ops if available
Date: Tue, 16 Dec 2014 13:45:51 +0100 [thread overview]
Message-ID: <20141216134551.75ca7975@free-electrons.com> (raw)
In-Reply-To: <8761dbkbr6.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Tue, 16 Dec 2014 13:41:33 +0100, Peter Korsgaard wrote:
> > Is this really what we want to do? In such cases, we normally always
> > force to use the "system" version of the library rather than the
> > built-in one. Why should Erlang be treated differently, especially if
> > using the "system" version of the library works fine?
>
> So in other words, make erlang select libatomic_ops? That sounds fine to
> me.
Yes, that's what I meant: make erlang select libatomic_ops.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-16 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 21:36 [Buildroot] [git commit] erlang: use libatomic_ops if available Peter Korsgaard
2014-12-16 12:26 ` Thomas Petazzoni
2014-12-16 12:41 ` Peter Korsgaard
2014-12-16 12:45 ` Thomas Petazzoni [this message]
2014-12-16 13:00 ` Frank Hunleth
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=20141216134551.75ca7975@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.