From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-09-01
Date: Mon, 3 Sep 2012 09:17:06 +0200 [thread overview]
Message-ID: <20120903091706.47c0b600@skate> (raw)
In-Reply-To: <504319A8.5070903@relinux.de>
Le Sun, 02 Sep 2012 10:32:40 +0200,
Stephan Hoffmann <sho@relinux.de> a ?crit :
> I just started looking at this. The cause of the problem is that the
> tool chain lacks suppot for the "versionsort" routine.
>
> In uClinux there is a patch adding a versionsort to alsalib locally, but
> this doesn't seem to be a good solution to me, especially since I assume
> that most other toolchains have versionsort so that such a patch would
> breal other architectures.
The configure script can detect whether this function is provided by
the toolchain, and only if not provided, enable the internal version.
> There are also some other patches for alsa-lib that would be needed to
> support blackfin. How shall we handle such architecture dependent patches?
We don't like architecture specific patches. This one for example has
no reason to be architecture-specific, it just needs to be written
properly :-)
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-09-03 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 6:32 [Buildroot] [autobuild.buildroot.net] Build results for 2012-09-01 Thomas Petazzoni
2012-09-02 8:32 ` Stephan Hoffmann
2012-09-02 9:01 ` Samuel Martin
2012-09-03 10:08 ` Stephan Hoffmann
2012-09-03 7:17 ` Thomas Petazzoni [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=20120903091706.47c0b600@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox