From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libphidget: needs dynamic library support
Date: Tue, 02 Sep 2014 13:51:56 -0300 [thread overview]
Message-ID: <5405F5AC.7030208@zacarias.com.ar> (raw)
In-Reply-To: <alpine.DEB.2.02.1409021930440.5899@tavas.tkos.co.il>
On 09/02/2014 01:32 PM, Jonathan Ben Avraham wrote:
> Hi Gustavo,
> Thanks for the fix.
> What should I have known or tested to find this myself at the time that
> I added the package?
>
> - yba
Hi Jonathan.
Usually when i add a new package i have a couple of prebuilt external
toolchains to test against with just the basic toolchain options:
* Lowest possible version of linux headers for latest git buildroot, to
find minimal requirements (rarely needed).
* Static & Dynamic
* Uclibc barebones (no rpc/wchar/lfs/ipv6)
* C++ and not.
There's no bulletproof formula to get all the options right, rather a
set of hints to look at.
For example extensive use of mbstowcs/mblen/wctomb functions in the
source usually indicates it needs wchar support (unless it's conditional).
Non-conditional usage of in6* / IN6* for IPv6.
RPC functions (pmap_* xdr_*) for RPC.
Mandatory usage of dlopen, creation of shared libraries (plugins) or
linking to libdl is usually a good hint that static-only isn't an option.
And so on.
In the end the autobuilders were doing their job, there are many
combinations that can slip under the radar: missing X syscall in some
architecture, some assembly optimization that doesn't consider
architecture variants which needs disabling and so on (example: can't
handle ARM thumb-only mode).
Regards.
prev parent reply other threads:[~2014-09-02 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 0:16 [Buildroot] [PATCH] libphidget: needs dynamic library support Gustavo Zacarias
2014-09-02 7:38 ` Peter Korsgaard
2014-09-02 16:32 ` Jonathan Ben Avraham
2014-09-02 16:51 ` Gustavo Zacarias [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=5405F5AC.7030208@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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