From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: "Fredrik Noring" <noring@nocrew.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jürgen Urban" <JuergenUrban@gmx.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI for the R5900
Date: Mon, 12 Nov 2018 23:56:38 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1811122327290.9637@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.21.1811091618230.27920@eddie.linux-mips.org>
On Fri, 9 Nov 2018, Maciej W. Rozycki wrote:
> > Some readelf results:
> >
> > mips64el/stretch
> >
> > Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
> > Class: ELF64
> > Flags: 0x80000007, noreorder, pic, cpic, mips64r2
>
> Hmm, that's weird -- what executable did you check? There may be some
> that are n64, or maybe they've switched (which I would applaud, FWIW). I
> remember seeing mostly n32, with minimal support for n64, but that was a
> while ago -- jessie or suchlike, I believe. Using MIPS64r2 as the base
> ISA also looks new to me, that used to be plain MIPS III, and some of
> Debian's MIPS build systems used to be either MIPS III (Lemote Loongson)
> or MIPS64r1 (Broadcom SiByte).
OK, I definitely got this confused. I did some checking and jessie
didn't even have a 64-bit MIPS port. I got their build systems right
though, and the kernel is 64-bit for systems that support it.
> > Any binaries that need qemu-mipsn32 or qemu-mipsn32el?
>
> I'd expect at least the n32 dynamic loader (along with libc and some
> other essential DSOs) to be present with MIPS64 Debian. Traditionally,
> under the FHS rules, it would be installed as /lib32/ld.so.1 (with the o32
> one as /lib/ld.so.1 and the n64 as /lib64/ld.so.1), but Debian uses their
> own multiarch filesystem layout standard, and offhand I don't remember
> what the paths are defined to there.
So with jessie you can install the `libc6-dev-mipsn32' package, which
will get you n32 glibc development libraries and will pull the
complementing n32 dynamic loader (at /lib32/ld.so.1 actually) and n32
glibc shared libraries as well.
Unfortunately multilib support files, such as the CRT files, seem to be
missing from GCC for n32 or I cannot find them. Otherwise you would be
able to compile and link n32 binaries just by calling `gcc -mabi=n32'.
Still the dynamic loader is directly runnable, as I noted above.
HTH,
Maciej
prev parent reply other threads:[~2018-11-13 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 18:42 [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI for the R5900 Fredrik Noring
2018-11-08 18:43 ` [Qemu-devel] [PATCH 1/2] " Fredrik Noring
2018-11-09 10:34 ` Laurent Vivier
2021-02-14 15:17 ` Philippe Mathieu-Daudé
2021-02-14 15:44 ` Bin Meng
2021-02-14 17:22 ` Laurent Vivier
2018-11-08 18:43 ` [Qemu-devel] [PATCH 2/2] tests/tcg/mips: Test user mode DMULT " Fredrik Noring
2018-11-09 10:55 ` [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI " Laurent Vivier
2018-11-09 14:14 ` Maciej W. Rozycki
2018-11-09 14:56 ` Laurent Vivier
2018-11-09 16:34 ` Maciej W. Rozycki
2018-11-12 23:56 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.1811122327290.9637@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=JuergenUrban@gmx.de \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=noring@nocrew.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).