Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/trinity: New package
Date: Wed, 8 Oct 2014 11:01:45 +0100	[thread overview]
Message-ID: <54350B89.8020508@imgtec.com> (raw)
In-Reply-To: <87mw96evci.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On 10/08/2014 10:58 AM, Peter Korsgaard wrote:
>>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
>
> Hi,
>
>   >> execinfo.h is only available if uClibc is built with
>   >> UCLIBC_HAS_BACKTRACE=y (which it isn't by default).
>   >>
>   >> Perhaps the backtrace() stuff can get #ifdef'ed out if not available?
>
>   > It looks like a change to be made upstream. Maybe it needs to include
>   > a header check in the configure.sh script, then defining a macro if
>   > the header is present, and then modify the source code to take that
>   > macro into account to do things like "#ifdef USE_EXECINFO"...
>
>   > So, what do you propose by now for the Buildroot package? Disabling it
>   > for uClibc until upstream fixes that?
>
> Either that or submit a patch upstream.

Let's disable it by now. I don't have enough understanding of the inners 
of that package to be able to do that patch right now, so I will just 
send an email upstream requesting that fix.

I will send the new patch in a while.

Thanks.

-- 
Vincent

      reply	other threads:[~2014-10-08 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 11:21 [Buildroot] [PATCH] package/trinity: New package Vicente Olivert Riera
2014-10-07 22:11 ` Peter Korsgaard
2014-10-08  9:44   ` Vicente Olivert Riera
2014-10-08  9:58     ` Peter Korsgaard
2014-10-08 10:01       ` 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=54350B89.8020508@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