From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Cc: Alex Gonzalez <alex.gonzalez@packetvision.com>,
debian-mips@lists.debian.org
Subject: Re: ABI incompatibility when building util-linux
Date: Thu, 24 Mar 2005 08:48:59 -0500 [thread overview]
Message-ID: <4242C54B.3010306@gentoo.org> (raw)
In-Reply-To: <20050324120109.GI8876@hattusa.textio>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Thiemo Seufer wrote:
>
> n32 means 64bit wide registers and 32bit address space. It runs only on
> a 64bit kernel.
>
A bit off topic, but it reminded me nonetheless. Anyone trying to build a new
version of procpcs (>3.4.2) under mips64 will likely need this patch.
Unsure what the reasoning behind this bit was in procps, but it assumes that
n32 is usable on a mips64 system (atleast, my understanding of the conditional
is that), and thus defines KLONG to long long on mips64, which breaks 'ps' on
these systems (you get a nice sigsev).
Thought it'd be useful to pass along.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world: small
hands do them because they must, while the eyes of the great are elsewhere."
--Elrond
[-- Attachment #2: procps-mips-n32_isnt_usable_on_mips64_yet.patch --]
[-- Type: text/plain, Size: 431 bytes --]
diff -Naurp procps-3.2.4.orig/proc/procps.h procps-3.2.4/proc/procps.h
--- procps-3.2.4.orig/proc/procps.h 2004-08-20 18:40:13 -0400
+++ procps-3.2.4/proc/procps.h 2005-02-28 10:38:05 -0500
@@ -31,7 +31,7 @@
//
// Unknown: PA-RISC and zSeries
//
-#if defined(k64test) || defined(_ABIN32)
+#if defined(k64test)
#define KLONG long long // not typedef; want "unsigned KLONG" to work
#define KLF "L"
#define STRTOUKL strtoull
next prev parent reply other threads:[~2005-03-24 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 11:25 ABI incompatibility when building util-linux Alex Gonzalez
2005-03-24 12:01 ` Thiemo Seufer
2005-03-24 13:48 ` Kumba [this message]
2005-03-24 14:52 ` Daniel Jacobowitz
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=4242C54B.3010306@gentoo.org \
--to=kumba@gentoo.org \
--cc=alex.gonzalez@packetvision.com \
--cc=debian-mips@lists.debian.org \
--cc=linux-mips@linux-mips.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