public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com> To: novaTopFlex <andrewkaymars@proton.me> Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>, gcc-help@gcc.gnu.org Subject: Re: GCC Installation breaks older header files Date: Tue, 21 May 2024 09:56:31 +0100 [thread overview] Message-ID: <Zkxhv8w9hmg4YTsE@zen.kayari.org> (raw) In-Reply-To: <05Kr2RdkO7jwPyf55LQdLnQ84SsdHhQpHAKsTKVbvSLVxemExLrfROS6Z6swnLayDxV7X460XVZeLNuRaldnY2UHMyLi_-Rsn2exUFUR3_Y=@proton.me> This mailing list is for automated mail from our bugzilla database, not for reporting bugs. It looks like you should be using the gcc-help mailing list anyway, not reporting a bug. I've CC'd that list. Please remove the gcc-bugs mailing list from the CC list when replying. On 20/05/24 20:48 +0000, novaTopFlex wrote: >For system information results as necessary: > >Result from uname -a: > >Linux ubuntu-macbookpro 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The system information is not very relevant, but you haven't even said what version of GCC you're using. >Also, there is no specific software or hardware being affected; this is a large-scale issue for developers needing to switch versions of the cross-compiler. > >Sent with [Proton Mail](https://proton.me/) secure email. > >On Monday, May 20th, 2024 at 4:45 PM, novaTopFlex <andrewkaymars@proton.me> wrote: > >> I am sorry to report that existing header files may have been broken by the installation of a newer version of GCC. I have continuously attempted to compile newer versions of GCC from source but my system continuously fails to compile the code. I am not sure if there is any recovery path to restore success for applications that had depended on these headers. Sorry for the interruption. Nobody can help you with such a vague description of the problem. What do you mean "broken"? Which header files? What happens? What command are you running, and what errors do you get? Where did you install the new GCC? Did you overwrite an old version, or install to a different location? How did you configure and build GCC? Maybe you just need to run the mkheaders script as documented at https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Fixed-Headers.html
prev parent reply other threads:[~2024-05-21 8:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-20 20:45 novaTopFlex 2024-05-20 20:48 ` novaTopFlex 2024-05-21 8:56 ` Jonathan Wakely [this message]
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=Zkxhv8w9hmg4YTsE@zen.kayari.org \ --to=jwakely@redhat.com \ --cc=andrewkaymars@proton.me \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-help@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).