From: Ben Collins <bcollins@debian.org>
To: Shanti Katta <katta@csee.wvu.edu>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Compiling packages from source on Ultrasparc
Date: Sun, 17 Nov 2002 20:23:02 -0500 [thread overview]
Message-ID: <20021118012302.GD544@phunnypharm.org> (raw)
In-Reply-To: <1037581211.30240.17.camel@indus.csee.wvu.edu>
On Sun, Nov 17, 2002 at 08:00:11PM -0500, Shanti Katta wrote:
> Hi,
> I understand that userland is 32-bit on Ultrasparc. I am trying to
> compile user-mode-linux on Ultrasparc, and I guess I need to compile it
> in 32-bit mode for it to run as a normal user-level process. UML make
> use of certain files in asm-{base-arch} during compilation. Now, to
> compile uml in 32-bit mode, I did not include any flags in
> makefiles(like -m64, -mcpu=ultrasparc) that would include 64-bit
> specific asm code.
> My question is that, what difference does it make when I compile UML, in
> a sparc32 shell, as compared to the above process without executing the
> sparc32 shell. I understand that if compiled in sparc32 shell, it
> recognizes the host-arch as "sparc" instead of "sparc64". But other than
> that, does it make any other difference? I am also not sure, which is
> the right method for compiling UML.
> Any pointers will be appreciated.
To compile it as a 32bit app, use the sparc32 wrapper to be safe, or
pass sparc as the target arch for UML.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2002-11-18 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 1:00 Compiling packages from source on Ultrasparc Shanti Katta
2002-11-18 1:23 ` Ben Collins [this message]
2002-11-18 5:33 ` David S. Miller
2002-11-18 17:09 ` Shanti Katta
2002-11-18 19:41 ` David S. Miller
2002-11-18 23:37 ` Shanti Katta
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=20021118012302.GD544@phunnypharm.org \
--to=bcollins@debian.org \
--cc=katta@csee.wvu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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