From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/trinity: New package
Date: Thu, 9 Oct 2014 09:08:17 +0100 [thread overview]
Message-ID: <54364271.50001@imgtec.com> (raw)
In-Reply-To: <CAHXCMM+an7ijdVvZGnxTndxauwdhivNjjmC6-7mdD4TYFPL0xQ@mail.gmail.com>
Dear Samuel Martin,
On 10/08/2014 08:39 PM, Samuel Martin wrote:
> It looks like you can now bump the version to [1] and get rid of this
> uclibc stuff ;-)
>
> [1] https://github.com/kernelslacker/trinity/commit/1cc389fb22ca4a7447011a7a14bb526d44197255
>
> Regards,
the upstream maintainer and me are working together to fix the problems
with uClibc. That was the first problem and is now fixed. However, there
are more problems after that one, so this package is not yet ready to be
built for uClibc.
Regards,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-10-09 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 15:12 [Buildroot] [PATCH v3] package/trinity: New package Vicente Olivert Riera
2014-10-08 19:39 ` Samuel Martin
2014-10-09 8:08 ` Vicente Olivert Riera [this message]
2014-10-09 15:20 ` Vicente Olivert Riera
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=54364271.50001@imgtec.com \
--to=vincent.riera@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox