From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] ltrace: update to current master
Date: Sat, 4 Jul 2015 14:37:32 +0200 [thread overview]
Message-ID: <20150704143732.296a3e64@free-electrons.com> (raw)
In-Reply-To: <1435921524-31825-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 3 Jul 2015 13:05:23 +0200, Vicente Olivert Riera wrote:
> Lots of fixes have been made to ltrace, including the ones for fixing a
> build failure for MIPS architecture. Updating to current master will
> allow us to re-enable this package for MIPS and also remove some
> upstreamed patches.
>
> At the same time we add a patch made by J?r?me Pouiller to fix a bug
> introduced by 5ba9e10 ("Split type definitions from the bundled configs
> into their own files"). Two new configuration files are not installed.
> Therefore, ltrace fail with messages like :
>
> /usr/share/ltrace/libm.so.conf:333: error: unknown type around 'ldouble
> erfl(ldouble);
>
> That patch has been sent upstream.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> v1 -> v2: add J?r?me Pouiller's patch
Both applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-04 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 11:05 [Buildroot] [PATCH v2 1/2] ltrace: update to current master Vicente Olivert Riera
2015-07-03 11:05 ` [Buildroot] [PATCH v2 2/2] ltrace: enable for mips/mipsel Vicente Olivert Riera
2015-07-04 12:37 ` Thomas Petazzoni [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=20150704143732.296a3e64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox