All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: can't compile r220 because of setjmp.S
Date: Sat, 16 May 2009 18:52:31 +0200	[thread overview]
Message-ID: <1242492751.3701.7.camel@fz.local> (raw)
In-Reply-To: <d7ead6de0905160934y78a897e6oe36fec51f942c371@mail.gmail.com>

Am Samstag, den 16.05.2009, 18:34 +0200 schrieb Vladimir 'phcoder'
Serbinenko:
> On Sat, May 16, 2009 at 6:23 PM, Felix Zielcke <fzielcke@z-51.de> wrote:
> > Hi list,
> >
> > r2220 on amd64 fails for me with:
> >
> > cc -Ilib/i386 -I/tmp/buildd/grub2-1.96+20090516/lib/i386 -I. -I./include -I/tmp/buildd/grub2-1.96+20090516/include -Wall -W -DASM_FILE=1   -MD -c -o setjmp_mod-lib_i386_setjmp.o /tmp/buildd/grub2-1.96+20090516/lib/i386/setjmp.S
> > setjmp.S: Assembler messages:
> > setjmp.S:33: Error: suffix or operands invalid for `pop'
> > setjmp.S:37: Error: suffix or operands invalid for `jmp'
> > setjmp.S:55: Error: suffix or operands invalid for `jmp'
> It tries to compile 32-bit version. You should say it to take 64-bit
> one. I have to go to eat now. When I come back if you haven't done it
> yet I'll do it

As said on IRC, it seems like the -m32 was missing there, even though it
should be set through the COMMON_CSFLAGS in i386-pc.rmk.
But that did the trick in i386.rmk:

-setjmp_mod_CFLAGS = $(COMMON_CFLAGS)
+setjmp_mod_ASFLAGS = $(COMMON_ASFLAGS)

-- 
Felix Zielcke




  reply	other threads:[~2009-05-16 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 16:23 can't compile r220 because of setjmp.S Felix Zielcke
2009-05-16 16:34 ` Vladimir 'phcoder' Serbinenko
2009-05-16 16:52   ` Felix Zielcke [this message]
2009-05-16 17:22     ` Felix Zielcke
2009-05-16 17:25       ` Javier Martín
2009-05-16 17:27         ` Vladimir 'phcoder' Serbinenko
2009-05-16 17:32           ` Felix Zielcke
2009-05-16 19:49             ` Bean

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=1242492751.3701.7.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.org \
    /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.