public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/99264] latest glibc release breaks Ada build on Linux Date: Fri, 05 Mar 2021 11:47:58 +0000 [thread overview] Message-ID: <bug-99264-4-fMldc0Gu0y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99264 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Eric Botcazou <ebotcazou@gcc.gnu.org>: https://gcc.gnu.org/g:331763de7d4850702a0f67298f36017c73cdb103 commit r11-7523-g331763de7d4850702a0f67298f36017c73cdb103 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Fri Mar 5 12:45:41 2021 +0100 Fix build breakage with latest glibc release gcc/ada/ PR ada/99264 * init.c (__gnat_alternate_sta) [Linux]: Remove preprocessor test on MINSIGSTKSZ and bump size to 32KB. * libgnarl/s-osinte__linux.ads (Alternate_Stack_Size): Bump to 32KB.
next prev parent reply other threads:[~2021-03-05 11:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-25 10:02 [Bug ada/99264] New: Ada doesn't build against latest glibc jakub at gcc dot gnu.org 2021-02-25 10:03 ` [Bug ada/99264] " jakub at gcc dot gnu.org 2021-02-25 10:07 ` rguenth at gcc dot gnu.org 2021-02-25 10:08 ` fw at gcc dot gnu.org 2021-02-25 10:10 ` fw at gcc dot gnu.org 2021-02-25 11:27 ` ebotcazou at gcc dot gnu.org 2021-02-25 11:40 ` fw at gcc dot gnu.org 2021-02-27 8:55 ` [Bug ada/99264] latest glibc release breaks Ada buildr on Linux ebotcazou at gcc dot gnu.org 2021-03-05 11:47 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-05 11:53 ` [Bug ada/99264] latest glibc release breaks Ada build " cvs-commit at gcc dot gnu.org 2021-03-05 11:54 ` cvs-commit at gcc dot gnu.org 2021-03-05 11:56 ` ebotcazou at gcc dot gnu.org
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=bug-99264-4-fMldc0Gu0y@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).