Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: I've a problem to compile i386 grub-emu
Date: Sun, 20 Jul 2008 12:24:55 +0200	[thread overview]
Message-ID: <87ej5okg3s.fsf@xs4all.nl> (raw)
In-Reply-To: <E8D3AE204CEE4BAE98085B1E23B584F3@fz> (Felix Zielcke's message of "Sun, 20 Jul 2008 12:08:48 +0200")

"Felix Zielcke" <fzielcke@z-51.de> writes:

> I have a x86_64 Kernel and want to have a 32bit grub-emu so modules are working.
> Even in a 32bit chroot running a shell with linux32 so uname -m reports i686 I can't get it to compile

You need to install ncurses and the -dev package.  Which distribution
do you use?

> Btw. make distclean didn't worked for my already used 64bit grub2 SVN directory I needed to do a clean checkout
>
>
> # ./configure --enable-grub-emu
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
>
> # make grub-emu
> cd . && autoheader
> echo timestamp > ./stamp-h.in
> gcc -Iutil -I./util -I. -Iinclude -I./include -Wall -W
> -DGRUB_LIBDIR=\"/usr/local/lib/`echo grub/i386-pc | sed 's,x,x,'`\" -g
> -O2 -DGRUB_UTIL=1  -MD -c -o grub_emu-util_console.o util/console.c
> util/console.c: In function 'grub_ncurses_putchar':

I wonder why this got through the autoconf test.

--
Marco




  reply	other threads:[~2008-07-20 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 10:08 I've a problem to compile i386 grub-emu Felix Zielcke
2008-07-20 10:24 ` Marco Gerards [this message]
2008-07-20 10:30   ` Felix Zielcke
2008-07-20 14:59   ` Felix Zielcke
2008-07-20 21:15     ` Pavel Roskin

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=87ej5okg3s.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox