Alsa-lib 32-bit on 64-bit machine

[Alan Horstmann]

Hi,

I've tried to find info or examples of this on the web, but to no avail.

What is the recommended way to build Alsa-lib on a 64-bit machine to create
the additional alternative 32-bit libraries for compatibility with 32-bit
applications?

The original distro (in this case a Suse Enterprise) has them, but standard
'./configure make install' only builds the 64-bit variants. I only succeeded
by explicitly adding CFLAGS, and wondered if it should work using configure
options, or another way? I'm also not sure exactly which flags should be set
with that method (m32, march=i686 others?). Does anyone know how it is done
in the Suse builds?

Thanks,

Alan

[Takashi Iwai]

At Tue, 21 Oct 2014 19:12:21 +0100,

Post by Alan Horstmann
Hi,
I've tried to find info or examples of this on the web, but to no avail.
What is the recommended way to build Alsa-lib on a 64-bit machine to create
the additional alternative 32-bit libraries for compatibility with 32-bit
applications?
The original distro (in this case a Suse Enterprise) has them, but standard
'./configure make install' only builds the 64-bit variants. I only succeeded
by explicitly adding CFLAGS, and wondered if it should work using configure
options, or another way? I'm also not sure exactly which flags should be set
with that method (m32, march=i686 others?). Does anyone know how it is done
in the Suse builds?

I don't know of any other than passing CFLAGS and LDFLAGS.


Takashi

[Alan Horstmann]

Post by Takashi Iwai
At Tue, 21 Oct 2014 19:12:21 +0100,

Post by Alan Horstmann
I've tried to find info or examples of this on the web, but to no avail.
What is the recommended way to build Alsa-lib on a 64-bit machine to
create the additional alternative 32-bit libraries for compatibility with
32-bit applications?
The original distro (in this case a Suse Enterprise) has them, but
standard './configure make install' only builds the 64-bit variants. I
only succeeded by explicitly adding CFLAGS, and wondered if it should
work using configure options, or another way? I'm also not sure exactly
which flags should be set with that method (m32, march=i686 others?).
Does anyone know how it is done in the Suse builds?

I don't know of any other than passing CFLAGS and LDFLAGS.

OK, thanks; what is the purpose/use of '--target=' or '--build=' configure
options?

Regards

Alan

[Takashi Iwai]

At Wed, 22 Oct 2014 08:59:13 +0100,

Post by Alan Horstmann

Post by Takashi Iwai
At Tue, 21 Oct 2014 19:12:21 +0100,

Post by Alan Horstmann
I've tried to find info or examples of this on the web, but to no avail.
What is the recommended way to build Alsa-lib on a 64-bit machine to
create the additional alternative 32-bit libraries for compatibility with
32-bit applications?
The original distro (in this case a Suse Enterprise) has them, but
standard './configure make install' only builds the 64-bit variants. I
only succeeded by explicitly adding CFLAGS, and wondered if it should
work using configure options, or another way? I'm also not sure exactly
which flags should be set with that method (m32, march=i686 others?).
Does anyone know how it is done in the Suse builds?

I don't know of any other than passing CFLAGS and LDFLAGS.

OK, thanks; what is the purpose/use of '--target=' or '--build=' configure
options?

Ask Google :)

http://stackoverflow.com/questions/5139403/whats-the-difference-of-configure-option-build-host-and-target


Takashi