public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: Chris Packham via Libc-help <libc-help@sourceware.org>
Subject: Does glibc require a MMU?
Date: Sat, 23 Sep 2023 12:10:37 +1200	[thread overview]
Message-ID: <CAFOYHZA+0LK0QRgHMN=fUnsc4fAmV1fU7KBe336wvW-qmpc+mA@mail.gmail.com> (raw)

Hi,

I'm looking at tidying some things up in crosstool-ng. Currently we
don't allow selecting GLIBC if the architecture doesn't support a MMU.
A user pointed out that that means that we can't build a
m68k-linux-gnu toolchain but per the GLIBC README that configuration
is supported.

I think the specific case of m68k is a bit subtle because there are
MMU-less variants. So while the architecture clearly allows for a MMU
not all variants of the CPU will have one. I probably will set the
flag to say m68k supports a MMU but I'm wondering if more generally I
should just allow glibc to be selected regardless of MMU support.

Thanks,
Chris

             reply	other threads:[~2023-09-23  0:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23  0:10 Chris Packham [this message]
2023-09-23 15:57 ` Carlos O'Donell

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='CAFOYHZA+0LK0QRgHMN=fUnsc4fAmV1fU7KBe336wvW-qmpc+mA@mail.gmail.com' \
    --to=judge.packham@gmail.com \
    --cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).