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 target/112762] [14 Regression] Cannot build crosscompilers for some uclinux targets since r14-5791-g24592abd68e6ef
Date: Wed, 06 Dec 2023 13:34:47 +0000	[thread overview]
Message-ID: <bug-112762-4-GIIvrbapt9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112762-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112762

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:e0eca4a55bd14d506708fb0396b31e7f7383160c

commit r14-6220-ge0eca4a55bd14d506708fb0396b31e7f7383160c
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Dec 5 13:39:49 2023 -0500

    build: unbreak bootstrap on uclinux targets [PR112762]

    Currently, cross-compiling with --target=c6x-uclinux (and several other)
    fails due to:

    ../../src/gcc/config/linux.h:221:45: error:
'linux_fortify_source_default_level' was not declared in this scope
     #define TARGET_FORTIFY_SOURCE_DEFAULT_LEVEL
linux_fortify_source_default_level

    In the PR Andrew mentions that another fix would be in config.gcc,
    but really, here I meant to use the target hook for glibc only, not
    uclibc.  This trivial patch fixes the build problem.  It means that
    -fhardened with uclibc will use -D_FORTIFY_SOURCE=2 and not =3.

            PR target/112762

    gcc/ChangeLog:

            * config/linux.h: Redefine TARGET_FORTIFY_SOURCE_DEFAULT_LEVEL for
            glibc only.

  parent reply	other threads:[~2023-12-06 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:33 [Bug target/112762] New: Cannot build crosscompilers for some uclinux targets fkastl at suse dot cz
2023-11-29 17:46 ` [Bug target/112762] [14 Regression] Cannot build crosscompilers for some uclinux targets since r14-5791-g24592abd68e6ef pinskia at gcc dot gnu.org
2023-11-29 17:54 ` pinskia at gcc dot gnu.org
2023-11-29 17:58 ` mpolacek at gcc dot gnu.org
2023-11-29 18:03 ` pinskia at gcc dot gnu.org
2023-11-29 19:00 ` joseph at codesourcery dot com
2023-12-06 13:34 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-06 13:37 ` mpolacek at gcc dot gnu.org
2023-12-06 13:37 ` mpolacek 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-112762-4-GIIvrbapt9@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: 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).