From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libsvdrp: Add libsvdrp hg.
Date: Tue, 30 Mar 2010 14:13:24 +0200 [thread overview]
Message-ID: <1269951204.4103.40.camel@mattotaupa> (raw)
In-Reply-To: <1269790930.8018.55.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
Am Sonntag, den 28.03.2010, 17:42 +0200 schrieb Paul Menzel:
> Am Sonntag, den 28.03.2010, 17:28 +0200 schrieb Koen Kooi:
> > On 28-03-10 16:49, Paul Menzel wrote:
> > > 1. Build tested with GCC 4.4.3 and Binutils 2.20.1 for `MACHINE = "beagleboard"`.
> >
> > Does it work for a more common combination of 4.3.3 and 2.18.x?
>
> Sorry, I did not test that. I will try to do that tomorrow.
I built it successfully with 4.3.3 and 2.18.50. Please add that to the
commit message and commit.
Thanks,
Paul
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2010-03-30 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 14:49 [PATCH] libsvdrp: Add libsvdrp hg Paul Menzel
2010-03-28 15:03 ` Paul Menzel
2010-03-28 15:28 ` Koen Kooi
2010-03-28 15:42 ` Paul Menzel
2010-03-30 12:13 ` Paul Menzel [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=1269951204.4103.40.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).