public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/104006] [12 regression] power-ieee128 merge breaks Solaris build Date: Thu, 13 Jan 2022 16:39:59 +0000 [thread overview] Message-ID: <bug-104006-4-PTAjikFVQj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104006-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104006 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #52180|0 |1 is obsolete| | --- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 52181 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52181&action=edit gcc12-pr104006.patch Updated patch that should cure it. But reading the automake manual and the generated Makefile, I actually don't understand why you are getting any problems (except the gfortran.ver-sun). All these generated *.inc and *.h files are mentioned in BUILT_SOURCES, and e.g. the all: rule looks like: all: $(BUILT_SOURCES) config.h $(MAKE) $(AM_MAKEFLAGS) all-am so make all (and other goes like make check) should make sure all these *.inc and *.h generated files appear before running recursive make to build everything.
next prev parent reply other threads:[~2022-01-13 16:39 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-13 12:39 [Bug libfortran/104006] New: " ro at gcc dot gnu.org 2022-01-13 12:40 ` [Bug libfortran/104006] " ro at gcc dot gnu.org 2022-01-13 13:17 ` jakub at gcc dot gnu.org 2022-01-13 13:20 ` jakub at gcc dot gnu.org 2022-01-13 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 14:01 ` jakub at gcc dot gnu.org 2022-01-13 14:04 ` jakub at gcc dot gnu.org 2022-01-13 14:28 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 14:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 14:37 ` jakub at gcc dot gnu.org 2022-01-13 14:52 ` jakub at gcc dot gnu.org 2022-01-13 15:02 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 15:07 ` jakub at gcc dot gnu.org 2022-01-13 15:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 16:39 ` jakub at gcc dot gnu.org [this message] 2022-01-13 16:42 ` jakub at gcc dot gnu.org 2022-01-13 16:50 ` cvs-commit at gcc dot gnu.org 2022-01-13 17:26 ` jakub at gcc dot gnu.org 2022-01-13 18:32 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 18:39 ` jakub at gcc dot gnu.org 2022-01-13 21:26 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 21:27 ` ro at gcc dot gnu.org 2022-01-13 21:39 ` jakub at gcc dot gnu.org 2022-01-13 21:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-13 22:39 ` jakub at gcc dot gnu.org 2022-01-13 22:42 ` jakub at gcc dot gnu.org 2022-01-13 22:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-14 6:45 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-01-14 11:19 ` cvs-commit at gcc dot gnu.org 2022-01-15 12:22 ` jakub 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-104006-4-PTAjikFVQj@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).