[Pkg-alsa-devel] Bug#516585: RFH: alsa-lib

Andreas Metzler ametzler at downhill.at.eu.org
Sun Feb 22 18:49:12 UTC 2009

On 2009-02-22 Elimar Riesebieter <riesebie at lxtec.de> wrote:
> * Andreas Metzler [090222 17:42 +0100]
>> On 2009-02-22 Elimar Riesebieter <riesebie at lxtec.de> wrote:
>>> I want to prepare alsa-lib 1.0.19 for upload. Building alsa-lib on i386 and
>>> amd64 gives:
>>> ...
>>> checking for strip... strip
>>> checking for cross-compiler... i486-i486-pc-linux-gnu-gcc
>>> checking for i486-linux-gnu-gcc... i486-i486-pc-linux-gnu-gcc
>>> checking for C compiler default output file name...
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details.

>> I am not sure, but I think (see
>> /usr/share/doc/autotools-dev/README.Debian.gz) you are invoking
>> ./configure the wrong way. This makes it build successfully for me:

>> -----------------------
>> --- debian/rules        (Revision 2165)
>> +++ debian/rules        (Arbeitskopie)
>> -                   --host=$(DEB_HOST_GNU_TYPE) \
>> +                   --build $(DEB_BUILD_GNU_TYPE) \
>> -----------------------

> Yes, but in that case:
> ....
> checking whether we are cross compiling... no
> ....

> This is what we don't want.

Afaiui multilib and cross-compiling work differently and you wanted
multilib, not cross compiling. But my understanding of this area is
almost non-existing. If you wanted to cross compile for amd64 on
i386 you would set 

--build i486-linux-gnu --host x86_64-linux-gnu

and this would cause ./configure to use amd64-pc-linux-gnu-gcc as

> Second: Why does it build on ppc ?

No idea. :-(

cu and- not getting the point of 64bit alsa on i486 anyway. - reas
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

More information about the Pkg-alsa-devel mailing list