From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] elfutils and the perf userspace tool
Date: Wed, 05 Dec 2012 01:00:56 +0200 [thread overview]
Message-ID: <50BE80A8.1050801@petroprogram.com> (raw)
In-Reply-To: <50BE7E8E.5000201@petroprogram.com>
5.12.2012 0:51, Stefan Fr?berg kirjoitti:
> 5.12.2012 0:34, Thomas Petazzoni kirjoitti:
>> Dear Stefan Fr?berg,
>>
>> On Wed, 05 Dec 2012 00:23:07 +0200, Stefan Fr?berg wrote:
>>
>>>> Don't reinvent the wheel:
>>>>
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/elfutils/elfutils/uclibc-support.patch
>>>>
>>>> And possibly other patches in:
>>>>
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/elfutils/elfutils
>>>>
>>>> Thomas
>>> So why those are not in buildroot yet ?
>> Because you forgot to submit a patch? :-)
>>
>> Thomas
> Nah, I have too much work while testing working of latest firefox 16.0.1
> for buildroot right now and trying
> to push patches upstream.
>
> And I let all the honor for that elfutils work to go for Boldan.
>
> But I did some quick checking of those patches and all those are for
> older than 0.155 that Boldan is trying to compile
> and that uclibc-support.patch needs some tuning to be applied cleanly
> for 0.155 version and there is no mention
> of obstack() function problem being fixed (if using uClibc) in any of them.
>
> Maybe it can be fixed without using gnulib (witch provides obstack
> implementation similar to glibc) and using some
> standard comforming function(s) but I could not find any.
>
> Regards
> Stefan
>
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
And now I just noticed this line from that uclibc-support.patch:
|"Upstream-Status: Inappropriate [uclibc specific]"
How nice. Like I said earlier. The makers of this elfutils software are
really lifting the middle finger in terms of portability.
:P
I wonder if Ulrich Drepper was (still is?) in head of this .........
|
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121205/5759b72c/attachment.html>
next prev parent reply other threads:[~2012-12-04 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 22:20 [Buildroot] elfutils and the perf userspace tool Bogdan Radulescu
2012-12-04 5:33 ` Bryan Hundven
2012-12-04 8:13 ` Bogdan Radulescu
2012-12-04 19:21 ` Stefan Fröberg
2012-12-04 19:42 ` Thomas Petazzoni
2012-12-04 22:23 ` Stefan Fröberg
2012-12-04 22:29 ` Stefan Fröberg
2012-12-04 22:34 ` Thomas Petazzoni
2012-12-04 22:51 ` Stefan Fröberg
2012-12-04 23:00 ` Stefan Fröberg [this message]
2012-12-05 15:07 ` Bogdan Radulescu
2012-12-05 15:31 ` Thomas Petazzoni
2012-12-06 16:10 ` Bogdan Radulescu
2012-12-06 16:11 ` Thomas Petazzoni
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=50BE80A8.1050801@petroprogram.com \
--to=stefan.froberg@petroprogram.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