From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] backtrace patch and execinfo.h missing on uclibc
Date: Sun, 14 Feb 2010 11:44:40 +0100 [thread overview]
Message-ID: <20100214114440.10260f67@surf> (raw)
In-Reply-To: <9e4ade691002132326i3d3261afja3e4513ec7c07f07@mail.gmail.com>
On Sun, 14 Feb 2010 04:26:28 -0300
Sebasti?n Treu <sebastian.treu@gmail.com> wrote:
> I have read another threads about it without any success on solve my
> problem. I also ask in IRC and gently they told me about a patch. But
> without any more information, and I didn't continue asking to don't
> bother people there. I don't like to bother anywhere, but I can't
> manage to solve my problem.
Can you explain what your problem is ?
I.e: give your .config file, tell us about the error you're having, how
we can reproduce it, etc.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-02-14 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 7:26 [Buildroot] backtrace patch and execinfo.h missing on uclibc Sebastián Treu
2010-02-14 10:44 ` Thomas Petazzoni [this message]
2010-02-14 23:42 ` Sebastián Treu
2010-02-20 18:56 ` 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=20100214114440.10260f67@surf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.