On Mon, Apr 21, 2008 at 02:59:36AM +0200, Mathias Behrle wrote: > x86_64 still not properly detected
This drives me nuts. :-) > I can confirm, that ARCH obviously still isn't correctly detected > (identically > to msg #76 cases 2 and 3). Well, it would be more obivous to us if you'd send some more info. The problem is usually that the system for some reason tries to build a i386 module with amd64 kernel sources. In case 2 ARCH is initialized, in case 3 it is not. > Additonally > ARCH=x86_64 m-a a-i isn't working for me. No surprise here since ARCH now defaults to `uname -m`, see history of this bug report. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
