From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC 5/6] libfslcodec: new package
Date: Thu, 20 Dec 2012 10:08:51 +0100 [thread overview]
Message-ID: <87a9t9ytss.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50D2CA07.1060503@mind.be> (Arnout Vandecappelle's message of "Thu, 20 Dec 2012 09:19:19 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> For packages like this one that install pre-built libraries, it
>> would be good to document somewhere or to auto-check (e.g. with
>> toolchain kconfig options vs. package kconfig options) the ABI
>> compatibility to make sure that there won't be any issue with the
>> toolchain used.
Arnout> I agree, but how?
I don't know the specifics of this package, but presumably it only works
with glibc and a specific soft/softfp/hard floating point mode? If so,
we could atleast catch some of these dependencies in Config.in.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-12-20 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 23:37 [Buildroot] [PATCH RFC 0/6] Freescale i.MX multimedia libraries Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 1/6] imx-lib: new package Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 2/6] libfslvpuwrap: " Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 3/6] firmware-imx: " Arnout Vandecappelle
2013-01-14 15:24 ` Peter Korsgaard
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 4/6] libfslparser: " Arnout Vandecappelle
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 5/6] libfslcodec: " Arnout Vandecappelle
2012-12-20 1:06 ` Benoît Thébaudeau
2012-12-20 8:19 ` Arnout Vandecappelle
2012-12-20 9:08 ` Peter Korsgaard [this message]
2012-12-20 10:34 ` Arnout Vandecappelle
2012-12-20 10:50 ` Peter Korsgaard
2012-12-19 23:37 ` [Buildroot] [PATCH RFC 6/6] gst-fsl-plugins: " Arnout Vandecappelle
2013-01-14 15:22 ` [Buildroot] [PATCH RFC 0/6] Freescale i.MX multimedia libraries Peter Korsgaard
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=87a9t9ytss.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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