[alsa-devel] Alsa-lib 32-bit on 64-bit machine
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
At Tue, 21 Oct 2014 19:12:21 +0100, Alan Horstmann wrote:
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
On Wednesday 22 October 2014 08:03, you wrote:
At Tue, 21 Oct 2014 19:12:21 +0100,
Alan Horstmann wrote:
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
At Wed, 22 Oct 2014 08:59:13 +0100, Alan Horstmann wrote:
On Wednesday 22 October 2014 08:03, you wrote:
At Tue, 21 Oct 2014 19:12:21 +0100,
Alan Horstmann wrote:
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...
Takashi
participants (2)
-
Alan Horstmann -
Takashi Iwai