From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] alsa-utils: needs dynamic library support
Date: Tue, 27 Jan 2015 15:28:01 +0200 [thread overview]
Message-ID: <20150127132801.GJ3148@tarshish> (raw)
In-Reply-To: <20150127135220.7832b906@free-electrons.com>
Hi Thomas,
On Tue, Jan 27, 2015 at 01:52:20PM +0100, Thomas Petazzoni wrote:
> On Tue, 27 Jan 2015 12:21:13 +0200, Baruch Siach wrote:
> > Fixes:
> > http://autobuild.buildroot.net/results/314/314dac9f5e62ae9beb598eb1b4cb35c0a7bfe792/
> > http://autobuild.buildroot.net/results/964/964e44f0c1653370600c7e8c647abda3f6380e34/
> > http://autobuild.buildroot.net/results/d72/d72f31bab907c7485d03db4597d01fd759277db4/
> > ...
> >
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > package/alsa-utils/Config.in | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
>
> I am not sure. alsa-utils hardcodes:
>
> ALSA_LIBS="$ALSA_LIBS -lasound -lm -ldl -lpthread"
>
> but in practice, alsa-lib does not necessarily depends on -ldl.
Indeed. Now I see that commit ffd7a00aef723 (alsa-lib: add patch to remove
hardcoded -ldl) intended to fix that exact same issue. Though it seems like we
need to AUTORECONF alsa-utils for this fix to take effect, isn't it?. Thomas
(DS)?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-01-27 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 10:21 [Buildroot] [PATCH] alsa-utils: needs dynamic library support Baruch Siach
2015-01-27 12:52 ` Thomas Petazzoni
2015-01-27 13:28 ` Baruch Siach [this message]
2015-01-27 16:05 ` 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=20150127132801.GJ3148@tarshish \
--to=baruch@tkos.co.il \
--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