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:
> > > > >
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
> >>>
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
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
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
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
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
> > >
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
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
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
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
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
12 matches
Mail list logo
