From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ltrace: update to current master
Date: Thu, 18 Jun 2015 14:15:24 +0200 [thread overview]
Message-ID: <5582B65C.2060705@imgtec.com> (raw)
In-Reply-To: <1635366.Gf85uioWz5@sagittea>
Dear J?r?me Pouiller,
On 17/06/15 14:01, J?r?me Pouiller wrote:
> Hello Vicente,
>
> On Wednesday 17 June 2015 12:37:12 Vicente Olivert Riera wrote:
>> Dear J?r?me Pouiller,
>>
>> any progress on this?
> We are waiting for upstream:
> http://lists.alioth.debian.org/pipermail/ltrace-devel/2015-June/001328.html
>
> I think Buildroot should provide this patch until upstream responds.
I agree. Do you want to write a Buildroot patch to do the version bump
plus adding that patch?
Regards,
--
vincent
>>
>> Regards,
>> --
>> vincent
>>
>> On 05/06/15 01:13, J?r?me Pouiller wrote:
>>> Hello Vicente,
>>>
>>> On Monday 25 May 2015 15:52:38 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.
>>>>
>>>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>>>> ---
>>>> .../{0002-arm-plt.patch => 0001-arm-plt.patch} | 0
>>>> package/ltrace/0001-events.patch | 47 -
>>>> package/ltrace/0003-PPC-fix-PPC32-build.patch | 31 -
>>>> .../ltrace/0004-xtensa-add-xtensa-support.patch | 1612 --------------------
>>>> package/ltrace/ltrace.mk | 2 +-
>>>> 5 files changed, 1 insertions(+), 1691 deletions(-)
>>>> rename package/ltrace/{0002-arm-plt.patch => 0001-arm-plt.patch} (100%)
>>>> delete mode 100644 package/ltrace/0001-events.patch
>>>> delete mode 100644 package/ltrace/0003-PPC-fix-PPC32-build.patch
>>>> delete mode 100644 package/ltrace/0004-xtensa-add-xtensa-support.patch
>>> [..]
>>>> diff --git a/package/ltrace/ltrace.mk b/package/ltrace/ltrace.mk
>>>> index 7f00ce3..8a78a2a 100644
>>>> --- a/package/ltrace/ltrace.mk
>>>> +++ b/package/ltrace/ltrace.mk
>>>> @@ -4,7 +4,7 @@
>>>> #
>>>> ################################################################################
>>>>
>>>> -LTRACE_VERSION = 0896ce554f80afdcba81d9754f6104f863dea803
>>>> +LTRACE_VERSION = be0c6870e08a3be43b3a0d210fb8dc7614b1e82f
>>> It seems this version has 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);
>>>
>>> I have just sent a patch to upstream.
>>>
>
prev parent reply other threads:[~2015-06-18 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 14:52 [Buildroot] [PATCH 1/2] ltrace: update to current master Vicente Olivert Riera
2015-05-25 14:52 ` [Buildroot] [PATCH 2/2] ltrace: enable for mips/mipsel Vicente Olivert Riera
2015-06-04 23:13 ` [Buildroot] [PATCH 1/2] ltrace: update to current master Jérôme Pouiller
2015-06-04 11:22 ` Vicente Olivert Riera
2015-06-17 10:37 ` Vicente Olivert Riera
2015-06-17 12:01 ` Jérôme Pouiller
2015-06-18 12:15 ` Vicente Olivert Riera [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=5582B65C.2060705@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