On Tue, Mar 04, 2025 at 11:44:18AM +, Daniel P. Berrangé wrote:
> The QEMU community is discussing possible use of -gsplit-dwarf as a default
> option for QEMU's build system:
>
> https://lists.nongnu.org/archive/html/qemu-devel/2025-03/msg00424.html
>
> This option causes debug symbols to b
On Tue, Feb 11, 2025 at 08:04:58PM -0700, Orion Poplawski wrote:
> https://www.x.org/releases/X11R7.7/doc/libXt/intrinsics.html
>
> Describes:
>
> typedef struct _XtActionsRec {
> String string;
> XtActionProc proc;
> } XtActionsRec, *XtActionList;
>
> being initialized with:
>
>
> XtActionsRe
On Wed, Jan 29, 2025 at 02:38:45AM +, Sérgio Basto wrote:
> Applied , thank you .
>
> libphonenumber [1] doesn't build on rawhide because treats this warning
> as errors
>
> abseil-cpp-20240722.1 also have one header that emit this king of
> warning.
>
> in absl/hash/internal/hash.h line 3
On Mon, Jan 27, 2025 at 07:31:35PM +, Sérgio Basto via devel wrote:
> I just want check, if I'm thinking correctly before submitting a fix in
> gtest package
>
> The problem is on Rawhide I have this warning that make other packages
> fail to build [1]
>
> gtest source [2] source get __cplu
On Thu, Jan 23, 2025 at 08:16:25AM +0100, Florian Weimer wrote:
> * Jakub Jelinek:
>
> > On Wed, Jan 22, 2025 at 04:57:40PM -0700, Jerry James wrote:
> >> On Wed, Jan 22, 2025 at 4:43 PM Chuck Anderson wrote:
> >> > It looks like most (all?) perl XS pack
On Wed, Jan 22, 2025 at 04:57:40PM -0700, Jerry James wrote:
> On Wed, Jan 22, 2025 at 4:43 PM Chuck Anderson wrote:
> > It looks like most (all?) perl XS packages ('C' implementations of Perl
> > functions) are FTBFS with GCC 15. I'm trying to fix perl-Term-ReadLine-Gnu
> > to be C23-compatibl
On Wed, Jan 15, 2025 at 12:53:29PM -0700, Justin Forbes wrote:
> On Wed, Jan 15, 2025 at 11:51 AM Miro Hrončok wrote:
> >
> > On 15. 01. 25 17:15, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Wed, Jan 15, 2025 at 05:06:47PM +0100, Karolina Surma wrote:
> > >> Hi,
> > >>
> > >> My Python 3.14 builds
On Wed, Jan 15, 2025 at 06:02:49PM +0100, Karolina Surma wrote:
> thank you for clarifications and additional resources.
>
> On 1/15/25 17:23, Jakub Jelinek wrote:
> > On Wed, Jan 15, 2025 at 05:06:47PM +0100, Karolina Surma wrote:
> >
> > David Malcolm has perfo
On Wed, Jan 15, 2025 at 05:37:26PM +0100, Iñaki Ucar wrote:
> I was actually planning to keep it until the next R release, which is in
> April. Would that be a problem?
Well, it would be good if somebody told upstream before that release if
there are problems on the R side.
Jakub
--
___
On Wed, Jan 15, 2025 at 05:29:38PM +0100, Iñaki Ucar wrote:
> I thought we had more time for this. R fails to build too, and the mismatch
> between Fedora and R releases always makes this kind of change inconvenient
> for us packagers.
I wish the mass rebuild was a week or week and half later like
On Wed, Jan 15, 2025 at 05:06:47PM +0100, Karolina Surma wrote:
> My Python 3.14 builds have started pulling gcc 15 in Fedora Rawhide (no
> side-tag). Is this intentional?
If you mean that rawhide now uses gcc 15, then yes (not building 3.14 is of
course not on purpose, but it might be that it is
On Tue, Jan 14, 2025 at 12:33:55PM +, Sérgio Basto wrote:
> On Mon, 2025-01-13 at 11:45 +0100, Jakub Jelinek wrote:
> > Hi!
> >
> > With the Fedora 42 mass rebuild approaching, I've built gcc 15
> > snapshot
> > (and annobin/libtool) in the
> >
On Tue, Jan 14, 2025 at 12:43:51PM +0100, Björn Persson wrote:
> Björn Persson wrote:
> > There seems to be a regression on S390x:
> >
> > gprconfig --batch -o /dev/null --validate
> > raised SYSTEM.OBJECT_READER.FORMAT_ERROR :
> > System.Object_Reader.ELF64_Ops.Initialize: unrecognized architect
On Mon, Jan 13, 2025 at 12:10:45PM +0100, Jakub Jelinek wrote:
> > Third, this choice would be "permanent", i.e. it would be done once at
> > package installation time. If the user tries to boot the same image
> > on different hardware, it might fail. This is inferior
On Mon, Jan 13, 2025 at 09:11:35AM +, Zbigniew Jędrzejewski-Szmek wrote:
> First, this would require setting up the infrastructure to build and
> store and distribute multiple builds of a single version of a
> package. This is something that Fedora currently doesn't do, so it'd
> require change
Hi!
With the Fedora 42 mass rebuild approaching, I've built gcc 15 snapshot
(and annobin/libtool) in the
f42-build-side-103300
side-tag.
Feel free to do scratch builds against this side-tag if you want
to test whether something builds fine with GCC 15 (David Malcolm has
performed a mass prebuil
On Thu, Oct 31, 2024 at 07:14:08PM +0100, Kilian Hanich via devel wrote:
> While we are at it, please don't mix -O2 and -O3 while compiling the
> same program.
>
> This can break things and is really not fun to debug (and that's also
> the reason why a lot of buildsystems don't support that).
It
On Thu, Oct 31, 2024 at 07:47:22PM +0200, drago01 wrote:
> > > Isn't instruction cache footprint already part of "performance" i.e if
> > > performance is improved it shouldn't matter and vice versa, or what am I
> > > missing?
> >
> > That is not how compilers work, ...
> >
>
> That's not what I
On Thu, Oct 31, 2024 at 12:12:30PM +, Richard W.M. Jones wrote:
> On Thu, Oct 31, 2024 at 12:36:28PM +0100, Jakub Jelinek wrote:
> > On Thu, Oct 31, 2024 at 11:26:23AM +, Peter Robinson wrote:
> > > I seem to remember firefox uses LTO+PGO for speed ups/
> > >
On Thu, Oct 31, 2024 at 07:28:35AM -0400, Neal Gompa wrote:
> SUSE has the benefit of their build system taking care of automatic
> rebuilds and simple build loops for them. This allows them to have a
> much more hands-off approach than we do, and gives their packagers
> significantly more breathin
On Thu, Oct 31, 2024 at 11:26:23AM +, Peter Robinson wrote:
> I seem to remember firefox uses LTO+PGO for speed ups/
>
> I wonder if we could provide some rpm macros and packaging guidelines
> to assist packagers in this process to make things more straight
> forward and less error prone? Is s
On Thu, Oct 31, 2024 at 10:57:02AM +, Peter Robinson wrote:
> On Thu, 31 Oct 2024 at 07:32, Jakub Jelinek wrote:
> >
> > On Wed, Oct 30, 2024 at 10:46:01PM -0400, Neal Gompa wrote:
> > > I know the idea of moving to -O3 has been briefly mentioned before in
> &g
On Thu, Oct 31, 2024 at 10:15:03AM +0200, drago01 wrote:
> On Thursday, October 31, 2024, Jakub Jelinek wrote:
>
> > On Wed, Oct 30, 2024 at 10:46:01PM -0400, Neal Gompa wrote:
> > > I know the idea of moving to -O3 has been briefly mentioned before in
> > > other
On Wed, Oct 30, 2024 at 10:46:01PM -0400, Neal Gompa wrote:
> I know the idea of moving to -O3 has been briefly mentioned before in
> other contexts when we've discussed uplifting the flags, but it looks
> like Ubuntu is moving to -O3 for Ubuntu 25.04[1]. Is there a reason
> why we shouldn't consid
On Wed, Jun 12, 2024 at 05:35:24PM +0100, Daniel P. Berrangé wrote:
> It isn't as simple as changing the CFLAGS. QEMU used to check for
> the CPU feature at startup, set a flag, and then later use that flag
> to choose different codepaths, but this logic was removed. Avoiding
> the flag check in ho
On Tue, Apr 02, 2024 at 12:33:04PM +0530, Samyak Jain wrote:
> Today, 2024-04-02, is an important day on the Fedora Linux 40 schedule
> [1], with significant cut-offs.
>
> Today we have the Final Freeze [2] which starts at 14:00 UTC. This means
> that only packages that fix accepted blocker or fre
On Mon, Apr 01, 2024 at 01:36:48PM -0400, Peter Jones wrote:
> Unrelated to the idea that some packages are special in this way, it's
> probably worth writing some static analysis tools we could put into
> rpm-inspect to detect when (a) a binary grows new public keys it didn't
> have before, and (b
On Sun, Feb 25, 2024 at 08:41:38PM +0100, Antonio T. sagitter wrote:
> libdv is currently failing in i686 architectures, it could be dropped.
Ugh, why?
The bug is not from upstream, but from the downstream libdv-pic.patch
patch, and is on i686 only because those changes are in i686 specific code.
On Wed, Feb 21, 2024 at 11:34:37AM -0500, Steven A. Falco wrote:
> I am getting an error "template-id not allowed for constructor in C++20" but
> according to the Copr log [0], the compiler is being given -std=c++17:
It is a warning, but you've asked for all warnings to be errors, right?
As docum
On Sat, Feb 17, 2024 at 10:03:39PM +0100, Sergio Pascual wrote:
> Hello, currently python-scikit-learn fails to build in f40 and rawhide
> https://bugzilla.redhat.com/show_bug.cgi?id=2261602
>
> The problem is a series of incompatible pointer conversions that
> appear in cython generated C code.
>
On Thu, Feb 15, 2024 at 12:57:21PM +0100, Florian Weimer wrote:
> For the first issue, please try this GHC patch (only compile-tested with
> the stage 0 compiler build this point):
>
> diff --git a/compiler/GHC/HsToCore/Foreign/C.hs
> b/compiler/GHC/HsToCore/Foreign/C.hs
> index 2164ded112..8beaa
On Thu, Feb 15, 2024 at 11:13:08AM +, Richard W.M. Jones wrote:
> We noticed that some ghc-* packages FTBFS with Modern C failures eg
> these two picked at random:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113534568
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113534
On Tue, Feb 06, 2024 at 01:50:14PM +0100, Jakub Jelinek wrote:
> On Tue, Feb 06, 2024 at 12:38:31PM +, Richard W.M. Jones wrote:
> > Not sure if it helps but it seems these source files implement the
> > plugin:
> >
> > https://github.com/AFLplusplus/AFLplusplus/
On Tue, Feb 06, 2024 at 12:38:31PM +, Richard W.M. Jones wrote:
> Not sure if it helps but it seems these source files implement the
> plugin:
>
> https://github.com/AFLplusplus/AFLplusplus/blob/stable/instrumentation/afl-gcc-cmplog-pass.so.cc
> https://github.com/AFLplusplus/AFLplusplus/blob/
On Tue, Feb 06, 2024 at 11:54:23AM +, Richard W.M. Jones wrote:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113035034
> https://bugzilla.redhat.com/show_bug.cgi?id=2262539
>
> The new AFL++ (American Fuzzy Lop, a fuzzing tool) in Rawhide appears
> to be building a GCC plugin, con
On Fri, Jan 26, 2024 at 10:59:55AM -0500, Yaakov Selkowitz wrote:
> On Fri, 2024-01-26 at 15:45 +, Sérgio Basto wrote:
> > Hi,
> >
> > MLT failed to build [2] with [1] , what do you suggest ?
> >
> > Best regards,
> >
> > [1]
> > builddir/build/BUILD/mlt-7.22.0/src/modules/gdk/pixops.c: In
On Sun, Jan 21, 2024 at 12:23:27PM +0100, Julian Sikorski wrote:
> asio started failing to build with gcc-14 [1]. The error is:
Seems (thanks Patrick for reducing and analyzing it) it is
a GCC bug, https://gcc.gnu.org/PR113544
Hopefully it will be fixed soon.
Jakub
--
___
On Sat, Jan 20, 2024 at 02:27:58PM +0100, Julian Sikorski wrote:
> AusweisApp2-2.0.3 build failed on rawhide/x86_64 with unsupported reloc 43
> errors [1]. Other architectures have built fine, similarly to released
> branches. Is this a problem with rawhide ld.gold?
I thought reloc 43 (aka R_X86_6
On Tue, Jan 16, 2024 at 03:32:14PM -0800, Aleksei Bavshin wrote:
> On Tue, Jan 16, 2024 at 3:07 PM Richard Shaw wrote:
> >
> > I'm working on getting a new dependency of one of my packages into Fedora:
> >
> > https://github.com/socketio/socket.io-client-cpp/releases
> >
> > After doing successful
On Tue, Jan 16, 2024 at 01:21:19PM +0100, Björn Persson wrote:
> Jakub Jelinek wrote:
> > The f40-build-side-81394 side-tag contains new
> > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be
> > tagged into rawhide shortly before the mass rebuild.
> >
>
On Mon, Jan 15, 2024 at 09:33:34PM +, Richard W.M. Jones wrote:
> On Mon, Jan 15, 2024 at 02:01:06PM +0100, Jakub Jelinek wrote:
> > Hi!
> >
> > The f40-build-side-81394 side-tag contains new
> > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be
>
On Mon, Jan 15, 2024 at 01:15:12PM +, Sérgio Basto wrote:
> On Mon, 2024-01-15 at 14:01 +0100, Jakub Jelinek wrote:
> > The f40-build-side-81394 side-tag contains new
> > gcc, annobin, libtool and redhat-rpm-config for f40, meant to be
> > tagged into rawhide shortly be
Hi!
The f40-build-side-81394 side-tag contains new
gcc, annobin, libtool and redhat-rpm-config for f40, meant to be
tagged into rawhide shortly before the mass rebuild.
If there is anything you'd like to rebuild against it before the mass
rebuild (such as packages depending on Ada which like ever
On Tue, Dec 05, 2023 at 04:38:55AM +0100, Kevin Kofler via devel wrote:
> Florian Weimer wrote:
> > The final patches for GCC 14 are currently under upstream review and
> > should land very soon. Earlier, I had received feedback that the larger
> > community desires just one transition, so we end
On Tue, Jul 25, 2023 at 12:40:15PM +0200, Florian Weimer wrote:
> * Samyak Jain:
>
> > - GNU Toolchain Update (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2)
>
> This change has not yet been voted on by Fesco, so it's largely not
> included in the rebuild: gcc was still using a 13.1 version, glib
On Wed, May 10, 2023 at 12:09:10AM +0200, Björn Persson wrote:
> Florian Weimer wrote:
> > I am going to explore a way to land -Werror=implicit-int
> > -Werror=implicit-function-declaration among the default compiler flags.
> > There's a bit of an issue because the C++ front end warns on
> > those
On Tue, Apr 04, 2023 at 07:37:59AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Apr 02, 2023 at 09:54:04PM +0200, Dan Čermák wrote:
> > The only benchmark that *I* am aware of is this one done by Martin
> > Jambor: https://jamborm.github.io/spec-2022-07-29-levels/
>
> This is very … underwh
On Thu, Feb 23, 2023 at 01:11:13PM +, Jonathan Wakely wrote:
> On Thu, 23 Feb 2023 at 13:03, Richard W.M. Jones wrote:
> > Do you know anything about what's happening with Ceph?
>
> No idea, sorry.
Ceph is likely #2169364 aka https://gcc.gnu.org/PR108773 , still unresolved
GCC bug.
J
On Tue, Jan 24, 2023 at 02:01:39PM -0600, Richard Shaw wrote:
> On Tue, Jan 24, 2023 at 7:20 AM Richard Shaw wrote:
>
> > hobbes1069 (9):
> > cqrlog - Fails for some weird lazbuild issue I don't understand
> > flnet - Spec conditional oops. Fixed.
> > flrig - Needed cstdint. Fixed
> > freecad - N
On Tue, Jan 24, 2023 at 10:00:47AM +0300, Vascom wrote:
> I have some packages failed.
> One of them libtins. Problem is that:
>
> error: 'uint32_t' is not a member of 'std';
>
> Is it normal? Is it GCC 13 change?
See
https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
Some libstdc++ h
On Wed, Jan 18, 2023 at 03:01:19PM +0100, Florian Weimer wrote:
> > On Wed, 2023-01-18 at 07:22 +0100, Florian Weimer wrote:
>
> >> If the unwind information is incomplete, this …
> >>
> >> > 7) signal handler unwinds the calling thread however it wants (and can
> >> > sleep and take page faults
On Tue, Jan 17, 2023 at 03:24:16PM +0100, Björn Persson wrote:
> Jakub Jelinek wrote:
> > On Tue, Jan 17, 2023 at 01:24:45PM +0100, Miro Hrončok wrote:
> > > Hello. GCC was updated to 13 in rawhide while the Fedora change was still
> > > being voted about by FESCo.
&
On Tue, Jan 17, 2023 at 01:24:45PM +0100, Miro Hrončok wrote:
> Hello. GCC was updated to 13 in rawhide while the Fedora change was still
> being voted about by FESCo.
>
> Apparently, the following packages now don't install:
There is a mass rebuild tomorrow. The Ada soname changes every year
an
On Mon, Jan 16, 2023 at 09:36:39PM -0700, Orion Poplawski wrote:
> elaborated-type-specifier for a scoped enum must not use the 'class' keyword
>33 | enum class EndiannessType : std::uint8_t
> | ^
The actual bug is shown in later errors.
> 'int32_t' is not a member of 'std'; did
On Mon, Jan 16, 2023 at 08:42:32PM +0100, Miro Hrončok wrote:
> On 16. 01. 23 20:30, Siddhesh Poyarekar wrote:
> > If it is for distribution packages then I reckon the flags should be
> > as close as possible for the mere reason of consistency within the
> > distribution.
>
> Nope, the individual
On Thu, Jan 12, 2023 at 06:29:10PM -0500, Siddhesh Poyarekar wrote:
> On Thu, Jan 12, 2023 at 12:41 PM Jakub Jelinek wrote:
> > > I've filed a ccache bug. It looks like ccache is moving the compiler
> > > arguments around, causing one of the -U_FORTIFY_SOURCE to
On Wed, Jan 11, 2023 at 06:44:22PM -0500, Siddhesh Poyarekar wrote:
> On Wed, Jan 11, 2023 at 4:43 PM Siddhesh Poyarekar
> wrote:
> > On Wed, Jan 11, 2023 at 4:37 PM Siddhesh Poyarekar
> > wrote:
> > >
> > > On Wed, Jan 11, 2023 at 3:05 PM Michel Alexandre Salim
> > > wrote:
> > > > Just `mock
On Tue, Dec 20, 2022 at 01:49:00PM +0100, Jakub Jelinek wrote:
> On Tue, Dec 20, 2022 at 12:12:42PM +, Daniel P. Berrangé wrote:
> > For KVM AMD SEV-SNP virtualization we're trying to get SVSM guest
> > firmware built on Fedora.
> >
> > https://github.com/
On Tue, Dec 20, 2022 at 12:12:42PM +, Daniel P. Berrangé wrote:
> For KVM AMD SEV-SNP virtualization we're trying to get SVSM guest
> firmware built on Fedora.
>
> https://github.com/svsm-vtpm/linux-svsm
>
> It builds successfully on Ubuntu 22.04 (gcc 11.3.0) which is what upstream
> uses a
On Tue, Dec 06, 2022 at 05:46:11PM -, Andrii Nakryiko wrote:
> Now, about prologues/epilogues. What percentage of useful workload is spent
> in those? Tiny fraction of a percent at best? Even if we don't get accurate
> stack trace in such cases it doesn't matter in the grand scheme of things.
On Tue, Dec 06, 2022 at 08:13:51AM -0500, Neal Gompa wrote:
> "may improve" is proven to be "does improve significantly". We had
That is nonsense. Even with -fno-omit-frame-pointers, you can't rely
on frame pointers, they are not accurate in function prologues and epilogues
and they are total gar
On Tue, Dec 06, 2022 at 11:13:38AM +0100, Vitaly Zaitsev via devel wrote:
> On 05/12/2022 20:58, Ben Cotton wrote:
> > Replace the current `_FORTIFY_SOURCE=2` with `_FORTIFY_SOURCE=3` to
> > improve mitigation of security issues arising from buffer overflows in
> > packages in Fedora.
>
> AFAIK, _
On Wed, Oct 26, 2022 at 07:06:43AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > == User Experience ==
> > User experience does not change.
>
> "The new default for C standard is -c99. Users who want to use
> an older standard need to specify something like -c89." (???)
It is -std=c89/-std=gnu89
On Sun, Aug 21, 2022 at 09:51:42AM -0700, John Reiser wrote:
> > it's clear there's a documentation problem [with DT_GNU_HASH]
> Partly due to lack of documentation, already I have seen "abuses"
So what is
https://akkadia.org/drepper/dsohowto.pdf
https://sourceware.org/legacy-ml/binutils/2006-10/m
On Sun, Aug 21, 2022 at 12:05:11PM +0200, Jan Drögehoff wrote:
> > It's Epic's fault. They must update their anti-cheat to use the modern
> > API.
>
> More reports have come out claiming this also affects the game Shovel
> Knight[2] and the open source library libstrangle[3], there is the non 0
>
On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> If you use i686 packages for something now, please respond to this thread.
I use {glibc{,-devel,-static},{gmp,mpfr,libmpc}{,-devel}}.i686 for
development and testing of GCC, even in Fedora packages I'd strongly prefer
to keep the -m
On Wed, Mar 02, 2022 at 04:26:11PM -0500, Ken Dreyer wrote:
> Some of the Ceph developers were investigating mold, since Ceph takes
> so long to build. Linking time is a problem for us with Ceph. But I
> don't know if those interested Ceph developers have done benchmarks
> yet.
>
> And the lack of
On Wed, Mar 02, 2022 at 01:29:00PM -0500, Ben Beasley wrote:
> In RPM packaging, of course, everything is built from scratch, usually with
> LTO, and a package that takes a minute to link probably takes an hour to
> build. While any work that can be saved in an RPM build is helpful, I think
> the g
On Thu, Feb 17, 2022 at 07:49:45PM +0100, Peter Lemenkov wrote:
> Hello,
> I've got a very suspiciously looking compilation issues while building
> PSPP package. All other arches are good except for ppc64le. Just grep
> for "error:" in the log attached.
>
> * https://koji.fedoraproject.org/koji/ta
On Tue, Feb 01, 2022 at 02:55:14PM +0100, Thomas Haller wrote:
> > > Apparently it was annobin (although it passed the test done during
> > > gcc.spec
> > > testing, apparently it was incompatible again).
> > > Florian has rebuilt it, so please just retry.
>
>
> Hi,
>
> after a few days, it seem
On Sun, Jan 30, 2022 at 08:00:48AM -0600, Richard Shaw wrote:
> /builddir/build/BUILD/OpenCOLLADA-1.6.68/Externals/MathMLSolver/src/MathMLEvaluatorVisitor.cpp:1:
> /builddir/build/BUILD/OpenCOLLADA-1.6.68/Externals/MathMLSolver/include/MathMLError.h:
> In destructor 'virtual MathML::Error::~Error()
On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> One of my packages, stable for a long time, is now getting exotic
> errors in rawhide such as
>
> -D_FORTIFY_SOURCE not defined
> -D_GLIBCXX_ASSERTIONS not defined
>
> Yesterday I saw (somewhere in here) that those errors are fixed in
On Thu, Jan 27, 2022 at 02:01:40PM +0100, František Šumšal wrote:
> Looks like the culprit is:
>
> In file included from common/mptPathString.cpp:13:
> ./src/mpt/uuid/uuid.hpp: In constructor 'constexpr
> mpt::mpt_libopenmpt::UUID::UUID()':
> ./src/mpt/uuid/uuid.hpp:195:17: error: 'goto' is not a
On Thu, Jan 27, 2022 at 10:32:22AM +0100, Thomas Haller wrote:
> On Wed, 2022-01-26 at 23:57 +0100, Jakub Jelinek wrote:
> > A new gcc with most importantly the https://gcc.gnu.org/PR104172
> > bug (that caused a lot of ppc64le failures) fixed and various other
> > fixes (e
Hi!
A new gcc with most importantly the https://gcc.gnu.org/PR104172
bug (that caused a lot of ppc64le failures) fixed and various other
fixes (e.g. std::basic_string(std::nullptr_t) = deleted only done
for C++23 etc.) is now in rawhide.
Can rel-eng please retry all FTBS builds that failed on ppc
On Wed, Jan 26, 2022 at 01:36:43PM +0100, Jakub Jelinek wrote:
> On Wed, Jan 26, 2022 at 01:29:37PM +0100, Dan Horák wrote:
> > > > **Compilation error from a dependency header:**
> > > >
> > > > dependency “boost”: “# error "Never use directly; in
On Wed, Jan 26, 2022 at 01:29:37PM +0100, Dan Horák wrote:
> > > **Compilation error from a dependency header:**
> > >
> > > dependency “boost”: “# error "Never use directly; include
> > > instead."”, via
> > > boost/multiprecision/cpp_int/intel_intrinsics.hpp
> >
> > This is weird.
> > bmiin
On Mon, Jan 17, 2022 at 09:00:13AM -0500, Ben Beasley wrote:
> **Internal compiler or debugger error:**
>
> abseil-cpp: “internal compiler error: tree code 'template_type_parm' is not
> supported in LTO streams”
Dunno, would need to reproduce.
> debugbreak: %check uses gdb, which now crashes (“(
On Mon, Jan 24, 2022 at 09:15:42PM +0100, Dan Horák wrote:
> > Perhaps we could merge today and then do another pass of failed builds
> > into f36-rebuild tag and merge that back on thursday or something?
> > Can we easily identify those builds that failed due to these ppc64le
> > issues?
>
> it s
On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote:
> On 24/01/2022 19:06, Kevin Fenzi wrote:
> > This seems kind of high, so we are going to resubmit all the failed
> > builds in a short second round to reduce the chance of transitory issues
> > causing the build failures.
>
On Mon, Jan 24, 2022 at 07:15:19AM -0500, Kaleb Keithley wrote:
> On Sat, Jan 22, 2022 at 2:28 PM Kaleb Keithley wrote:
>
> >
> >> The long double change is an ABI change, so this is kind of expected.
> >> Mass rebuild unfortunately doesn't go according to the dependency graph
> >> (and
> >> unfo
On Mon, Jan 24, 2022 at 11:55:39AM +0100, Fabio Valentini wrote:
> Have the command line arguments that are accepted by gcc?
>
> The test suite of the "cc" crate (used for compiling and linking to C
> code within Rust projects) started failing with GCC 12 with this
> error:
>
> gcc: error: un
On Sun, Jan 23, 2022 at 11:39:58AM +0100, Vitaly Zaitsev via devel wrote:
> On 14/01/2022 15:31, Jakub Jelinek wrote:
> > gcc 12 snapshot has landed as the system compiler into rawhide today.
>
> Another ICE on ppc64le with all packages contains catch2 library
On Sat, Jan 22, 2022 at 09:56:24AM -0500, Kaleb Keithley wrote:
> I know you want FTBFS bugs now for gcc-12 issues, but let me run this by
> you first and I will open a BZ if necessary.
>
> For ceph I've hacked up a fix for all the other gcc-12isms in ceph and now
> it fails to build on ppc64le[1]
On Sat, Jan 22, 2022 at 12:01:51PM -, Martin Gansser wrote:
> gcc-12 breaks build [1] with vdr-live with ppc64le on rawhide
>
> g++ -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches
> -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> -Wp,-D_GLIBCXX_ASSERTIONS
On Sat, Jan 22, 2022 at 11:51:37AM +, Jonathan Wakely wrote:
> IIRC it wasn't that simple. The necessary entropy was *not* coming
> from uninitialized bytes. There were other sources of *real* entropy,
> but the Debian patch caused *none* of it to be added to the pool
> (except for the PID). Ze
On Fri, Jan 21, 2022 at 07:10:53PM +0100, Miro Hrončok wrote:
> On 21. 01. 22 19:07, Jakub Jelinek wrote:
> > On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
> > > On 21. 01. 22 17:55, Jakub Jelinek wrote:
> > > > In all cases, if it is some compiler er
On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
> On 21. 01. 22 17:55, Jakub Jelinek wrote:
> > In all cases, if it is some compiler error or internal compiler error,
> > preprocessed source + gcc command line would be highly appreciated,
> > having us to t
On Fri, Jan 21, 2022 at 06:42:23PM +0100, Dan Horák wrote:
> > >
> > > Also note that libmpc failed to build on ppc64le only:
> > > https://koji.fedoraproject.org/koji/taskinfo?taskID=81535783
> >
> > one test core-dumps, I will try a local build to see what's in the core
>
> Error for mpc_pow_l
Hi!
There have been way too many mails recently in the
gcc-12.0.0-0.4.fc36 in rawhide thread and separate threads,
so for those which we haven't responded to yet or new issues,
can I ask you to track it in bugzilla instead of mailing list?
For issues where you suspect it is a bug on a package sid
On Thu, Jan 20, 2022 at 07:50:58AM -0500, Kaleb Keithley wrote:
> I thought I'd solved all my gcc-12-isms in ceph by running --scratch
> --arch-override=x86_64 builds, so I tried a full build and ran into this on
> aarch64. :-(
>
> In file included from /usr/include/boost/integer.hpp:20,
>
On Fri, Jan 21, 2022 at 09:15:04AM +, Richard W.M. Jones wrote:
>
> honggfuzz fails to build in Rawhide with:
>
> + hfuzz_cc/hfuzz-gcc hello.c -o hello
> gcc: error: unrecognized argument in option
> '-fsanitize-coverage=trace-pc,trace-cmp'
> gcc: note: valid arguments to '-fsanitize-c
On Fri, Jan 21, 2022 at 09:08:35AM +, Richard W.M. Jones wrote:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81468000
>
> This seems like a compiler bug or a bug in the standard switches being
> added by RPM on ppc64le. SLOF itself does not appear to add or adjust
> the -mtune fla
On Thu, Jan 20, 2022 at 02:31:52PM +, Richard W.M. Jones wrote:
> On Thu, Jan 20, 2022 at 02:30:24PM +, Richard W.M. Jones wrote:
> >
> > The qemu bug led to this optimizer mis-compilation bug which seems
> > very serious:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103721
> >
>
On Thu, Jan 20, 2022 at 01:32:26PM +, Jonathan Wakely wrote:
> On Thu, 20 Jan 2022 at 13:05, Jonathan Wakely wrote:
> >
> > On Thu, 20 Jan 2022 at 12:54, Kaleb Keithley wrote:
> > >
> > >
> > > I thought I'd solved all my gcc-12-isms in ceph by running --scratch
> > > --arch-override=x86_64
On Wed, Jan 19, 2022 at 07:27:44AM +0100, Remi Collet wrote:
> Le 14/01/2022 à 15:31, Jakub Jelinek a écrit :
> > gcc 12 snapshot has landed as the system compiler into rawhide today.
>
> PHP is now FTBFS on s390x only
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81
On Tue, Jan 18, 2022 at 03:13:22PM +, Sérgio Basto wrote:
> On Mon, 2022-01-17 at 14:36 +, Sérgio Basto wrote:
> > On Mon, 2022-01-17 at 15:10 +0100, Vitaly Zaitsev via devel wrote:
> > > On 17/01/2022 15:00, Ben Beasley wrote:
> > > > dependency “json”: https://github.com/nlohmann/json/iss
On Tue, Jan 18, 2022 at 07:22:00PM +0100, Florian Weimer wrote:
> >> On aarch64 I actually got a slightly different error message:
> >>
> >> ld: criu/pie/restorer.o: in function `lsm_set_label':
> >> /drone/src/criu/pie/restorer.c:174: undefined reference to `strlen'
> >>
> >> L
On Tue, Jan 18, 2022 at 07:08:00PM +0100, Adrian Reber wrote:
> On Tue, Jan 18, 2022 at 05:56:45PM +0100, Jakub Jelinek wrote:
> > On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
> > > > If there are bugs on the compiler side, please let me know immediately,
On Tue, Jan 18, 2022 at 05:40:31PM +0100, Adrian Reber wrote:
> > If there are bugs on the compiler side, please let me know immediately,
> > so that those bugs can be fixed before the mass rebuild next week.
>
> Not sure if it is a bug, CRIU no longer works with GCC 12.
>
> CRIU creates somethin
1 - 100 of 503 matches
Mail list logo
