On Wed, Apr 16, 2008 at 11:27:34AM +0200, Daniel Baumann wrote: > you need to build it yourself, however, it gives a lot of warnings and > this is the last part where it breaks: > > {standard input}: Assembler messages: > {standard input}:191: Error: suffix or operands invalid for `pushf' > {standard input}:192: Error: suffix or operands invalid for `pop' > ...
Yes, this looks like the well known problem of mixing i386 and amd64 builds. It appears to me that the culprit is lme setting ARCH to i386 when doing a amd64 build on i386, well at least it appears to set it to this value, please correct me if I'm wrong. The virtualbox-ose Makefile, however, uses ARCH to learn about the arch it is supposed to build for. I haven't tried reproducing this in detail but assuming my assumption is right, what do we do? Is ARCH a reserved variable? Or is it just a design decision by lme? Or in other words, can we change the name of this variable? According to /usr/src/linux-headers-*/Makefile ARCH should be the target architecture: When performing cross compilation for other architectures ARCH shall be set # to the target architecture. (See arch/* for the possibilities). Isn't this amd64 in this case? 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]