Re: Fedora 32 aarch64 build failures on copr
On Fri, 2020-07-31 at 11:44 -0300, Augusto Caringi wrote:
> Hi,
>
> On Thu, Jul 30, 2020 at 12:47 PM Jeremy Linton wrote:
> > On 7/28/20 4:39 PM, Jeff Law wrote:
> > > On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
> > > > On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
> > > > > If this is a new failure (say in the last week), it could be an out
> > > > > of memory
> > > > > scenario. Try disabling LTO. The standard way to do that is
> > > > >
> > > > > %define _lto_cflags %{nil}
> > > > >
> > > > > In your %build stanza in the spec file.
> > > > >
> > > > > Heff
> > > >
> > > > I agree, it's almost certainly OOM because it says "fatal error:
> > > > Killed." I've never seen that happen for any reason other than OOM.
> > > I've seen it happen for a variety of reasons. Please test with LTO
> > > disabled and
> > > let me know if that helps.
> >
> > As a FYI: I had similar problems not long ago building a tensorflow.
> > Reducing the build parallelism in that case helped reduce the memory
> > footprint sufficiently that the build completed.
>
> I'm facing a similar problem building the bpftrace package...
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48268388
>
> But for me, it seems gcc is crashing with a simple cmake test program:
>
> CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:60 (message):
> The C compiler
> "/usr/bin/cc"
> is not able to compile a simple test program.
>
> /builddir/build/BUILD/bpftrace-0.11.0/CMakeFiles/CMakeTmp/testCCompiler.c:1:
> internal compiler error: Segmentation fault
>
> https://kojipkgs.fedoraproject.org//work/tasks/9180/48269180/build.log
annobin failure. From the log:
annobin:
/builddir/build/BUILD/bpftrace-0.11.0/CMakeFiles/CMakeTmp/testCCompiler.c:
AArch64: The annobin plugin is out of date with respect to gcc
Clearly Nick and Jakub need to be coordinating better to prevent these problems,
they come up far too regularly.
jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
Hi,
On Thu, Jul 30, 2020 at 12:47 PM Jeremy Linton wrote:
>
> On 7/28/20 4:39 PM, Jeff Law wrote:
> > On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
> >> On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
> >>> If this is a new failure (say in the last week), it could be an out
> >>> of memory
> >>> scenario. Try disabling LTO. The standard way to do that is
> >>>
> >>> %define _lto_cflags %{nil}
> >>>
> >>> In your %build stanza in the spec file.
> >>>
> >>> Heff
> >>
> >> I agree, it's almost certainly OOM because it says "fatal error:
> >> Killed." I've never seen that happen for any reason other than OOM.
> > I've seen it happen for a variety of reasons. Please test with LTO
> > disabled and
> > let me know if that helps.
>
> As a FYI: I had similar problems not long ago building a tensorflow.
> Reducing the build parallelism in that case helped reduce the memory
> footprint sufficiently that the build completed.
I'm facing a similar problem building the bpftrace package...
https://koji.fedoraproject.org/koji/taskinfo?taskID=48268388
But for me, it seems gcc is crashing with a simple cmake test program:
CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:60 (message):
The C compiler
"/usr/bin/cc"
is not able to compile a simple test program.
/builddir/build/BUILD/bpftrace-0.11.0/CMakeFiles/CMakeTmp/testCCompiler.c:1:
internal compiler error: Segmentation fault
https://kojipkgs.fedoraproject.org//work/tasks/9180/48269180/build.log
Thoughts?
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Augusto Mecking Caringi
Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On 7/28/20 4:39 PM, Jeff Law wrote:
On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
If this is a new failure (say in the last week), it could be an out
of memory
scenario. Try disabling LTO. The standard way to do that is
%define _lto_cflags %{nil}
In your %build stanza in the spec file.
Heff
I agree, it's almost certainly OOM because it says "fatal error:
Killed." I've never seen that happen for any reason other than OOM.
I've seen it happen for a variety of reasons. Please test with LTO disabled and
let me know if that helps.
As a FYI: I had similar problems not long ago building a tensorflow.
Reducing the build parallelism in that case helped reduce the memory
footprint sufficiently that the build completed.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On 7/29/20 6:09 PM, Jeff Law wrote:
On Wed, 2020-07-29 at 17:14 -0500, Brandon Nielsen wrote:
On 7/29/20 4:40 PM, Jeff Law wrote:
ACK. I don't see msp430-development-tools in the standard fedora repos. So
I'll
leave it to you to fix the package in whatever repo it lives in.
Also note, you may ultimately be better off getting msp430 added to the cross-
{binutils,gcc} packages rather than creating a new package.
Jeff
It's a work in progress[0].
As for cross-gcc and friends, the description notes those are for
building kernels only, is that not the case?
It shouldn't matter for cross-binutils and cross-gcc.
There's also some vanilla upstream / TI upstream compatibility weirdness
to consider...
That issue should be resolved by getting those patches upstreamed to the GCC
project. Your best contact point for that would be Jozef Lawrynowicz <
joze...@mittosystems.com>
Jeff
Great! I'll look into it, thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On Wed, 2020-07-29 at 17:14 -0500, Brandon Nielsen wrote:
> On 7/29/20 4:40 PM, Jeff Law wrote:
> > ACK. I don't see msp430-development-tools in the standard fedora repos.
> > So I'll
> > leave it to you to fix the package in whatever repo it lives in.
> >
> > Also note, you may ultimately be better off getting msp430 added to the
> > cross-
> > {binutils,gcc} packages rather than creating a new package.
> >
> > Jeff
>
> It's a work in progress[0].
>
> As for cross-gcc and friends, the description notes those are for
> building kernels only, is that not the case?
It shouldn't matter for cross-binutils and cross-gcc.
>
> There's also some vanilla upstream / TI upstream compatibility weirdness
> to consider...
That issue should be resolved by getting those patches upstreamed to the GCC
project. Your best contact point for that would be Jozef Lawrynowicz <
joze...@mittosystems.com>
Jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On 7/29/20 4:40 PM, Jeff Law wrote:
ACK. I don't see msp430-development-tools in the standard fedora repos. So
I'll
leave it to you to fix the package in whatever repo it lives in.
Also note, you may ultimately be better off getting msp430 added to the cross-
{binutils,gcc} packages rather than creating a new package.
Jeff
It's a work in progress[0].
As for cross-gcc and friends, the description notes those are for
building kernels only, is that not the case?
There's also some vanilla upstream / TI upstream compatibility weirdness
to consider...
[0] - https://bugzilla.redhat.com/show_bug.cgi?id=1350884
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On Wed, 2020-07-29 at 14:24 -0500, Brandon Nielsen wrote:
> On 7/28/20 4:39 PM, Jeff Law wrote:
> > On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
> > > On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
> > > > If this is a new failure (say in the last week), it could be an out
> > > > of memory
> > > > scenario. Try disabling LTO. The standard way to do that is
> > > >
> > > > %define _lto_cflags %{nil}
> > > >
> > > > In your %build stanza in the spec file.
> > > >
> > > > Heff
> > >
> > > I agree, it's almost certainly OOM because it says "fatal error:
> > > Killed." I've never seen that happen for any reason other than OOM.
> > I've seen it happen for a variety of reasons. Please test with LTO
> > disabled and
> > let me know if that helps.
> >
> > jeff
>
> Disabling LTO with '%define _lto_cflags %{nil}' fixed it.
ACK. I don't see msp430-development-tools in the standard fedora repos. So
I'll
leave it to you to fix the package in whatever repo it lives in.
Also note, you may ultimately be better off getting msp430 added to the cross-
{binutils,gcc} packages rather than creating a new package.
Jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On 7/28/20 4:39 PM, Jeff Law wrote:
On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
If this is a new failure (say in the last week), it could be an out
of memory
scenario. Try disabling LTO. The standard way to do that is
%define _lto_cflags %{nil}
In your %build stanza in the spec file.
Heff
I agree, it's almost certainly OOM because it says "fatal error:
Killed." I've never seen that happen for any reason other than OOM.
I've seen it happen for a variety of reasons. Please test with LTO disabled and
let me know if that helps.
jeff
Disabling LTO with '%define _lto_cflags %{nil}' fixed it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On Tue, 2020-07-28 at 15:29 -0500, Michael Catanzaro wrote:
> On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
> > If this is a new failure (say in the last week), it could be an out
> > of memory
> > scenario. Try disabling LTO. The standard way to do that is
> >
> > %define _lto_cflags %{nil}
> >
> > In your %build stanza in the spec file.
> >
> > Heff
>
> I agree, it's almost certainly OOM because it says "fatal error:
> Killed." I've never seen that happen for any reason other than OOM.
I've seen it happen for a variety of reasons. Please test with LTO disabled and
let me know if that helps.
jeff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On Tue, Jul 28, 2020 at 2:01 pm, Jeff Law wrote:
If this is a new failure (say in the last week), it could be an out
of memory
scenario. Try disabling LTO. The standard way to do that is
%define _lto_cflags %{nil}
In your %build stanza in the spec file.
Heff
I agree, it's almost certainly OOM because it says "fatal error:
Killed." I've never seen that happen for any reason other than OOM.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 aarch64 build failures on copr
On Tue, 2020-07-28 at 14:51 -0500, Brandon Nielsen wrote:
> I've been seeing build failures for Fedora 32[0][1][2], always the same
> failure: "xgcc: fatal error: Killed signal terminated program cc1plus"
>
> I can't find any more detail than that. These builds succeed locally
> with mock. The copr failures are reproducible so I'm sure I'm doing
> something wrong, but I can't figure out what. Any ideas?
>
> [0] -
> https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1577708/
> [1] -
> https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1565812/
> [2] -
> https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1565363/
If this is a new failure (say in the last week), it could be an out of memory
scenario. Try disabling LTO. The standard way to do that is
%define _lto_cflags %{nil}
In your %build stanza in the spec file.
Heff
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 aarch64 build failures on copr
I've been seeing build failures for Fedora 32[0][1][2], always the same failure: "xgcc: fatal error: Killed signal terminated program cc1plus" I can't find any more detail than that. These builds succeed locally with mock. The copr failures are reproducible so I'm sure I'm doing something wrong, but I can't figure out what. Any ideas? [0] - https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1577708/ [1] - https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1565812/ [2] - https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/build/1565363/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
