From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: lib: Fix static linking of libasound
Date: Mon, 03 Jan 2011 10:50:54 +0000 [thread overview]
Message-ID: <ifs9me$v2o$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1101020041250.28150@eeebox2.perex-int.cz>
'Twas brillig, and Jaroslav Kysela at 01/01/11 23:42 did gyre and gimble:
> On Sat, 1 Jan 2011, Daniel Chen wrote:
>
>> On Sat, Jan 1, 2011 at 10:07 AM, Jaroslav Kysela <perex@perex.cz> wrote:
>>> Is any reason to ignore this configure settings mentined in the INSTALL file
>>> for the static library build?
>>>
>>> ./configure --enable-shared=no --enable-static=yes
>>>
>>> It's mainly libtool issue and having static hacks in the dynamic library
>>> does not make much sense.
>>
>> According to Samuel in the Debian bug report, "when both static &
>> dynamic linking is enabled, automake gets it wrong and uses only the
>> dynamic objects."
>>
>> Is the best course of action here to do a two-pass build, one with
>> "--enable-shared=no --enable-static=yes" and another with
>> "--enable-shared=yes --enable-static=no", simply copying the desired
>> libasound.a from the second pass?
>
> Yes, I believe, it's the right way to compile both types of library
> binaries.
Shouldn't the argument then be one that is mutually exclusive then?
e.g. --build-type=[shared||static]
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2011-01-03 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 21:46 [PATCH] ALSA: lib: Fix static linking of libasound Daniel Chen
2011-01-01 15:07 ` Jaroslav Kysela
2011-01-01 17:41 ` Daniel Chen
2011-01-01 23:42 ` Jaroslav Kysela
2011-01-03 10:50 ` Colin Guthrie [this message]
2011-01-03 17:03 ` Why is snd_pcm_hw_params_set_format() not setting the format at all? Philip Chu
2011-01-03 17:08 ` Jaroslav Kysela
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='ifs9me$v2o$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.org \
/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.