* x86_64 builds
@ 2004-06-07 21:26 Florian Bomers
2004-06-08 16:11 ` Takashi Iwai
0 siblings, 1 reply; 2+ messages in thread
From: Florian Bomers @ 2004-06-07 21:26 UTC (permalink / raw)
To: alsa-devel
Hi,
when trying to compile ALSA drivers 1.0.5a on SLES 8.1 with
kernel 2.4.19, the configure script always detected "k8" so
gcc was called with "-march=athlon". This resulted in module
binding problems, and I could not find a way to explicitly
compile for x86_64. I hacked configure.in so the check
#elif defined(CONFIG_X86_64)
fprintf(file, "x86_64");
comes right at the beginning of the long list of #elif's. On
AMD64, both CONFIG_MK8 and CONFIG_X86_64 are defined, so
without the hack the configure script would always assume k8.
I think it makes sense to modify configure.in so that it
compiles for 64-bit by default, or, at least, add a
configure parameter to explicitly choose 64-bit.
Florian
--
Florian Bomers
----------------------------------------------
Java Sound Sun Microsystems, Inc.
http://java.sun.com/products/java-media/sound/
----------------------------------------------
Please quote this email in your reply. Thanks!
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: x86_64 builds
2004-06-07 21:26 x86_64 builds Florian Bomers
@ 2004-06-08 16:11 ` Takashi Iwai
0 siblings, 0 replies; 2+ messages in thread
From: Takashi Iwai @ 2004-06-08 16:11 UTC (permalink / raw)
To: Florian Bomers; +Cc: alsa-devel
At Mon, 07 Jun 2004 14:26:19 -0700,
Florian Bomers wrote:
>
> Hi,
>
> when trying to compile ALSA drivers 1.0.5a on SLES 8.1 with
> kernel 2.4.19, the configure script always detected "k8" so
> gcc was called with "-march=athlon". This resulted in module
> binding problems, and I could not find a way to explicitly
> compile for x86_64. I hacked configure.in so the check
>
> #elif defined(CONFIG_X86_64)
> fprintf(file, "x86_64");
>
> comes right at the beginning of the long list of #elif's. On
> AMD64, both CONFIG_MK8 and CONFIG_X86_64 are defined, so
> without the hack the configure script would always assume k8.
>
> I think it makes sense to modify configure.in so that it
> compiles for 64-bit by default, or, at least, add a
> configure parameter to explicitly choose 64-bit.
Right. I'll fix this on CVS.
thanks,
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-06-08 16:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-07 21:26 x86_64 builds Florian Bomers
2004-06-08 16:11 ` Takashi Iwai
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.