public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-348] add glibc-stdint.h to vax and lm32 linux target (PR target/105525)
Date: Sat, 29 Apr 2023 16:58:05 +0000 (GMT)	[thread overview]
Message-ID: <20230429165805.19C1A3858C50@sourceware.org> (raw)

https://gcc.gnu.org/g:83c78cb0d78fffa8791f64ba36146d17c00c1b23

commit r14-348-g83c78cb0d78fffa8791f64ba36146d17c00c1b23
Author: Mikael Pettersson <mikpelinux@gmail.com>
Date:   Sat Apr 29 10:56:54 2023 -0600

    add glibc-stdint.h to vax and lm32 linux target (PR target/105525)
    
    PR target/105525 is a build regression for the vax and lm32 linux
    targets present in gcc-12/13/head, where the builds fail due to
    unsatisfied references to __INTPTR_TYPE__ and __UINTPTR_TYPE__,
    caused by these two targets failing to provide glibc-stdint.h.
    
    Fixed thusly, tested by building crosses, which now succeeds.
    
    Ok for trunk? (Note I don't have commit rights.)
    
            PR target/105525
    gcc/
            * config.gcc (vax-*-linux*): Add glibc-stdint.h.
            (lm32-*-uclinux*): Likewise.

Diff:
---
 gcc/config.gcc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/config.gcc b/gcc/config.gcc
index 6fd1594480a..671c7e3b018 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -2287,7 +2287,7 @@ lm32-*-rtems*)
 	tmake_file="${tmake_file} lm32/t-rtems"
          ;;
 lm32-*-uclinux*)
-        tm_file="elfos.h ${tm_file} gnu-user.h linux.h lm32/uclinux-elf.h"
+        tm_file="elfos.h ${tm_file} gnu-user.h linux.h glibc-stdint.h lm32/uclinux-elf.h"
 	tmake_file="${tmake_file} lm32/t-lm32"
         ;;
 m32r-*-elf*)
@@ -3488,7 +3488,7 @@ v850*-*-*)
 	use_gcc_stdint=wrap
 	;;
 vax-*-linux*)
-	tm_file="${tm_file} elfos.h gnu-user.h linux.h vax/elf.h vax/linux.h"
+	tm_file="${tm_file} elfos.h gnu-user.h linux.h glibc-stdint.h vax/elf.h vax/linux.h"
 	extra_options="${extra_options} vax/elf.opt"
 	;;
 vax-*-netbsdelf*)

                 reply	other threads:[~2023-04-29 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230429165805.19C1A3858C50@sourceware.org \
    --to=law@gcc.gnu.org \
    --cc=gcc-cvs@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).