public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27945] build-many-glibcs.py doesn't configure GCC with --enable-initfini-array
Date: Fri, 05 Nov 2021 22:30:29 +0000	[thread overview]
Message-ID: <bug-27945-131-7hNjoaHpce@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27945-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27945

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a586fe9c80f7cf2c9a5a6ccdbc572e7b5ec816b8

commit a586fe9c80f7cf2c9a5a6ccdbc572e7b5ec816b8
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Jun 9 05:29:16 2021 -0700

    Configure GCC with --enable-initfini-array [BZ #27945]

    Starting from GCC 12, the .init_array and .fini_array sections are enabled
    unconditionally by

    commit 13a39886940331149173b25d6ebde0850668d8b9
    Author: H.J. Lu <hjl.tools@gmail.com>
    Date:   Tue Jun 8 16:09:24 2021 -0700

        Always enable DT_INIT_ARRAY/DT_FINI_ARRAY on Linux

    configure GCC with --enable-initfini-array to enable them when using GCC
    release branches.

    Fixes BZ #27945.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-11-05 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  1:00 [Bug build/27945] New: " hjl.tools at gmail dot com
2021-06-03 18:04 ` [Bug build/27945] " joseph at codesourcery dot com
2021-06-03 19:40 ` hjl.tools at gmail dot com
2021-06-04 14:18 ` fweimer at redhat dot com
2021-11-05 22:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-05 23:35 ` hjl.tools at gmail dot com

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-27945-131-7hNjoaHpce@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).