public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Zimmermann via Libc-alpha <libc-alpha@sourceware.org>
Cc: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Subject: Re: building glibc 2.27 with gcc 12.2.0
Date: Fri, 17 Mar 2023 10:58:55 +0100	[thread overview]
Message-ID: <87wn3f66n4.fsf@igel.home> (raw)
In-Reply-To: <p9u0lejvka82.fsf@coriandre.loria.fr> (Paul Zimmermann via Libc-alpha's message of "Fri, 17 Mar 2023 10:17:49 +0100")

This has nothing to do with gcc, just configure with --without-selinux.  

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2023-03-17  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  9:17 Paul Zimmermann
2023-03-17  9:58 ` Andreas Schwab [this message]
2023-03-17 10:13   ` Paul Zimmermann

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=87wn3f66n4.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=libc-alpha@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).