[alsa-devel] [PATCH] ALSA: lib: Fix static linking of libasound

Colin Guthrie gmane at colin.guthr.ie
Mon Jan 3 11:50:54 CET 2011

'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 at 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]



Colin Guthrie

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/]

More information about the Alsa-devel mailing list