From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ofono: bump to version 1.17
Date: Sat, 31 Oct 2015 21:45:51 +0100 [thread overview]
Message-ID: <20151031204550.GA25719@t61> (raw)
In-Reply-To: <20151031155550.0c2636b8@free-electrons.com>
Dear Thomas Petazzoni,
> However, their patch for the musl build is really crappy. Instead, they
> should add a configure.ac check for the backtrace related functionality
> and use the result of that check instead of testing __GLIBC__. If you
> have the courage to improve this and submit it upstream, it would be
> good.
I'll do it :-).
I suppose it's enough just to improve check for execinfo.h header and backtrace function.
Kind regards,
Petr
prev parent reply other threads:[~2015-10-31 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 18:49 [Buildroot] [PATCH 1/1] ofono: bump to version 1.17 Petr Vorel
2015-10-31 14:55 ` Thomas Petazzoni
2015-10-31 20:45 ` Petr Vorel [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=20151031204550.GA25719@t61 \
--to=petr.vorel@gmail.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.