From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package: add gnupg
Date: Tue, 16 Oct 2012 21:04:15 +0200 [thread overview]
Message-ID: <87ipaatf0w.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20121016185610.36a03eff@skate> (Thomas Petazzoni's message of "Tue, 16 Oct 2012 18:56:10 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>> 3 files changed, 84 insertions(+), 0 deletions(-)
Thomas> This is causing the following build breakage on various platforms:
Thomas> http://autobuild.buildroot.org/results/07f97705dda6dfbeab8ce95d6cef5b016329c9ce/build-end.log
Yes - I noticed as well, just haven't found time to look closely at it
yet. The mpi stuff has cpu specific backends, so that's probably where
it goes wrong.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-10-16 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:20 [Buildroot] [git commit] package: add gnupg Peter Korsgaard
2012-10-16 16:56 ` Thomas Petazzoni
2012-10-16 19:04 ` Peter Korsgaard [this message]
2012-10-16 19:14 ` Arnout Vandecappelle
2012-10-16 19:24 ` Yann E. MORIN
2012-10-16 20:05 ` Thomas Petazzoni
2012-10-16 21:00 ` Peter Korsgaard
2012-10-16 21:03 ` Gustavo Zacarias
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=87ipaatf0w.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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