All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Bomers <Florian.Bomers@Sun.COM>
To: alsa-devel@lists.sourceforge.net
Subject: x86_64 builds
Date: Mon, 07 Jun 2004 14:26:19 -0700	[thread overview]
Message-ID: <40C4DD7B.40809@sun.com> (raw)

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

             reply	other threads:[~2004-06-07 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 21:26 Florian Bomers [this message]
2004-06-08 16:11 ` x86_64 builds Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40C4DD7B.40809@sun.com \
    --to=florian.bomers@sun.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.