public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112959] install.tex needs updates on FreeBSD
Date: Sun, 12 May 2024 14:41:22 +0000 [thread overview]
Message-ID: <bug-112959-4-UodOl8e0kK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112959-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112959
Gerald Pfeifer <gerald at pfeifer dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thierry at FreeBSD dot org
--- Comment #11 from Gerald Pfeifer <gerald at pfeifer dot com> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #6)
> What's there looks good to me.
Cool, thank you. I cherry picked the changes I made to the GCC 14
branch, so they should be in the GCC 14.2 release.
> However, one issue mentioned in PR target/112959 is missing, namely the
> problem of getting a working Ada bootstrap compiler. I have no idea if
> gnat12 has been fixed since and is now able to build Ada on trunk/the
> gcc-14 branch. Otherwise, the old GNAT 6.4.1 worked for me, but this
> isn't easy to find.
Looking at the lang/gnat12 and now lang/gcc13 ports and recent changes
including ones like
commit 7d359e6b779d96d82f383e3aeee8259057b16df0
Author: Thierry Thomas <thierry@FreeBSD.org>
Date: Wed Dec 13 22:41:20 2023 +0100
lang/gnat12: bootstrap from previous assets by default
All assets have been built, and it is now possible to bootstrap without
lang/gcc6-aux!
(which was a few days after this report was filed) I am hopefully it would
work. However, I cannot guarantee.
I am temped to mark this report as RESOLVED based on my changes.
Thierry, what is your take, in particular related to building GNAT as it
comes as part of upstream GCC?
next prev parent reply other threads:[~2024-05-12 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 10:47 [Bug target/112959] New: " ro at gcc dot gnu.org
2023-12-11 10:47 ` [Bug target/112959] " ro at gcc dot gnu.org
2023-12-11 11:39 ` rguenth at gcc dot gnu.org
2024-04-28 13:03 ` cvs-commit at gcc dot gnu.org
2024-05-01 14:24 ` cvs-commit at gcc dot gnu.org
2024-05-01 22:48 ` cvs-commit at gcc dot gnu.org
2024-05-01 22:54 ` gerald at pfeifer dot com
2024-05-06 9:27 ` gerald at pfeifer dot com
2024-05-06 11:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07 7:43 ` rguenth at gcc dot gnu.org
2024-05-12 13:28 ` cvs-commit at gcc dot gnu.org
2024-05-12 13:30 ` cvs-commit at gcc dot gnu.org
2024-05-12 13:32 ` cvs-commit at gcc dot gnu.org
2024-05-12 14:41 ` gerald at pfeifer dot com [this message]
2024-05-12 14:53 ` thierry at FreeBSD dot org
2024-05-13 8:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-13 10:30 ` gerald at pfeifer 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-112959-4-UodOl8e0kK@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).