All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Mohit Dhingra <mohitdhingras@gmail.com>
Subject: Re: Xen Source code build
Date: Mon, 2 Apr 2012 11:21:05 +0200	[thread overview]
Message-ID: <20120402092105.GA25886@aepfle.de> (raw)
In-Reply-To: <1333356972.25602.11.camel@zakaz.uk.xensource.com>

On Mon, Apr 02, Ian Campbell wrote:

> On Sun, 2012-04-01 at 06:34 +0100, Mohit Dhingra wrote:
> > Hello All,
> > 
> > I am a newbie to Linux and Xen. I tried compiling Xen Source code (I
> > want to make some changes and see how it works), but it failed on my
> > system as it couldn't find gnu-stubs32.h. Later, on looking at
> > Makefile, I figured out that for x86_64, it is not yet supported !! 

> WRT gnu-stubs32.h I suspect you are missing some -devel package or
> other. I don't know about how SuSE lays things out but you should locate
> the package containing this file and install it. Googling suggests that
> perhaps you meant gnu/stubs32.h? In which case you probably want to
> install glibc-devel.

Running configure and/or make in a 32bit shell is not needed.
"zypper in gcc-32bit glibc-devel-32bit" will install the required
packages to compile the 32bit parts in the firmware.

Olaf

  reply	other threads:[~2012-04-02  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01  5:34 Xen Source code build Mohit Dhingra
2012-04-02  8:56 ` Ian Campbell
2012-04-02  9:21   ` Olaf Hering [this message]
2012-04-07  6:25     ` Mohit Dhingra
2012-04-07  7:30       ` Ian Campbell

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=20120402092105.GA25886@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=mohitdhingras@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.