c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Neal Gompa <ngompa13@gmail.com>, Florian Weimer <fweimer@redhat.com>
Cc: oS-fctry <factory@lists.opensuse.org>, c-std-porting@lists.linux.dev
Subject: Re: More C errors by default in GCC 14 (implicit function declarations etc.)
Date: Thu, 20 Apr 2023 15:42:08 +0200	[thread overview]
Message-ID: <c74c68ac-ba2f-6dab-b03a-6ea0c6ec26e5@bernhard-voelker.de> (raw)
In-Reply-To: <CAEg-Je_nFsuWPCDzr-ooKU5NdjhyJBd56=1qmC7Dd8W_mqMMVA@mail.gmail.com>

On 4/18/23 15:19, Neal Gompa wrote:
>> Do you think OpenSUSE could cope with a transition in GCC 14?
> openSUSE does rebuilds of the whole distribution on a fairly regular
> basis, as reverse dependencies of updated packages get rebuilt
> automatically.

One aspect is that upstream developers are using distros like Fedora and OpenSUSE,
so the first step is to provide GCC14 as alternative GCC version there.
With that, upstream developers have a chance to fix those issues ... upstream.

To put it the other way round:
I don't see that too many packages would get or should be fixed as downstream patches only.
Yet the downstream build environments are of great help as well.

Have a nice day,

      parent reply	other threads:[~2023-04-20 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 12:36 More C errors by default in GCC 14 (implicit function declarations etc.) Florian Weimer
2023-04-18 13:19 ` Neal Gompa
2023-04-18 13:42   ` Jan Engelhardt
2023-04-18 13:55     ` Neal Gompa
2023-04-18 14:37       ` Sam James
2023-04-26 13:16         ` Neal Gompa
2023-04-20 13:42   ` Bernhard Voelker [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c74c68ac-ba2f-6dab-b03a-6ea0c6ec26e5@bernhard-voelker.de \
    --to=mail@bernhard-voelker.de \
    --cc=c-std-porting@lists.linux.dev \
    --cc=factory@lists.opensuse.org \
    --cc=fweimer@redhat.com \
    --cc=ngompa13@gmail.com \


* 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 NNTP newsgroup(s).