From: Sachin Sant <sachinp@linux.ibm.com>
To: Michael Ellerman <mpe@linux.ibm.com>
Cc: Tasmiya Nalatwad <tasmiya@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [netdev] Build failure on powerpc
Date: Thu, 29 Feb 2024 19:00:56 +0530 [thread overview]
Message-ID: <916F09F9-FC10-4248-BE64-9E01AA264CBA@linux.ibm.com> (raw)
In-Reply-To: <875xy8103a.fsf@mail.lhotse>
> On 29-Feb-2024, at 7:52 AM, Michael Ellerman <mpe@linux.ibm.com> wrote:
>
> Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com> writes:
>> Greetings,
>>
>> [netdev] Build failure on powerpc
>> latest netdev 6.8.0-rc5-auto-g1ce7d306ea63 fails to build on powerpc
>> below traces
>
> Please include the defconfig you're building, and the toolchain
> versions, in reports like this.
>
> I wasn't able to reproduce this failure here.
I believe this is tied to gcc version.
Build failure is seen while using gcc-8.5.x but not with gcc-11.4.x
— Sachin
WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@linux.ibm.com>
To: Michael Ellerman <mpe@linux.ibm.com>
Cc: Tasmiya Nalatwad <tasmiya@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [netdev] Build failure on powerpc
Date: Thu, 29 Feb 2024 19:00:56 +0530 [thread overview]
Message-ID: <916F09F9-FC10-4248-BE64-9E01AA264CBA@linux.ibm.com> (raw)
In-Reply-To: <875xy8103a.fsf@mail.lhotse>
> On 29-Feb-2024, at 7:52 AM, Michael Ellerman <mpe@linux.ibm.com> wrote:
>
> Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com> writes:
>> Greetings,
>>
>> [netdev] Build failure on powerpc
>> latest netdev 6.8.0-rc5-auto-g1ce7d306ea63 fails to build on powerpc
>> below traces
>
> Please include the defconfig you're building, and the toolchain
> versions, in reports like this.
>
> I wasn't able to reproduce this failure here.
I believe this is tied to gcc version.
Build failure is seen while using gcc-8.5.x but not with gcc-11.4.x
— Sachin
next prev parent reply other threads:[~2024-02-29 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 11:44 [netdev] Build failure on powerpc Tasmiya Nalatwad
2024-02-28 11:44 ` Tasmiya Nalatwad
2024-02-29 2:22 ` Michael Ellerman
2024-02-29 13:30 ` Sachin Sant [this message]
2024-02-29 13:30 ` Sachin Sant
2024-02-29 23:45 ` Michael Ellerman
2024-02-29 23:45 ` Michael Ellerman
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=916F09F9-FC10-4248-BE64-9E01AA264CBA@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@linux.ibm.com \
--cc=tasmiya@linux.ibm.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.