From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perf: new package
Date: Fri, 04 Jan 2013 16:01:52 +0200 [thread overview]
Message-ID: <50E6E0D0.10302@petroprogram.com> (raw)
In-Reply-To: <20130104002214.7a112fdf@skate>
Hi Thomas
4.1.2013 1:22, Thomas Petazzoni kirjoitti:
> Dear Stefan Fr?berg,
>
> On Thu, 03 Jan 2013 17:24:36 +0200, Stefan Fr?berg wrote:
>
>> Here is an elfutils 0.155 (which contains libelf) for buildroot that I
>> posted some time ago.
>> Patch #4 is missing from that list because it was too big to submit to
>> this list.
>>
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063855.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063856.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063864.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063858.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063857.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063859.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063861.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063860.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063863.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063862.html
>> http://lists.busybox.net/pipermail/buildroot/2012-December/063865.html
> I've started having a real look at this, and started refactoring your
> patch series.
>
> Could you point me to the missing PATCH #4, so that I can see your
> entire series? At least send it by private e-mail to me, so that we
> don't get limited by the list.
I can do that but I have to warn you that it's huge (1.5 MB).
Only one of the grub patches in buildroot is bigger (1.6 MB).
It's because uClibc is missing obstack_printf functionality and almost
half of it goes
to implementing it by gnulib portability library
(https://www.gnu.org/software/gnulib/)
Another half goes to enabling fts interface (because it's not enabled by
default in buildroot).
Ofcourse enabling it buy default in buildroot or even better, giving
user a choice of enabling it
in buildroot will help cutting size of that patch.
Anyway, I try to send it to you privately.
And also within few hours I will be kicking my old
crappy server online again, upload that patch there and submit link to
that patch for
everybody to work on.
Regards
Stefan
> Thanks,
>
> Thomas
next prev parent reply other threads:[~2013-01-04 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 15:07 [Buildroot] [PATCH] perf: new package Thomas Petazzoni
2013-01-03 15:24 ` Stefan Fröberg
2013-01-03 15:48 ` Stefan Fröberg
2013-01-03 23:22 ` Thomas Petazzoni
2013-01-04 14:01 ` Stefan Fröberg [this message]
2013-01-04 14:25 ` Stefan Fröberg
2013-01-04 14:27 ` Thomas Petazzoni
2013-01-04 6:05 ` Kaiwan Billimoria
2013-01-04 8:22 ` 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=50E6E0D0.10302@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