Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Compilation errors
Date: Fri, 01 Apr 2022 14:01:03 +0200	[thread overview]
Message-ID: <3410190.V25eIC5XRa@leap> (raw)
In-Reply-To: <20220401121357.09ae33d7@elisabeth>

On venerdì 1 aprile 2022 12:13:57 CEST Stefano Brivio wrote:
> Hi Fabio,
> 
> On Fri, 01 Apr 2022 11:35:13 +0200
> "Fabio M. De Francesco" <fmdefrancesco@gmail.com> wrote:
> >
> > [...]
> > 
> > Can someone help me to understand what is happening and how to fix this issue?
> > Could it depend on a configuration option that, unintentionally enabled, make 
> > the build fail whenever "case label does not reduce to an integer constant" is 
> > hit? If so, which option?
> 
> Those would be warnings, but kernel builds switched to -Werror by
> default a while ago, see commit 3fe617ccafd6 ("Enable '-Werror' by
> default for all kernel builds") -- meaning that all warnings are
> treated as errors. You can disable CONFIG_WERROR:
> 
> 	scripts/config -d WERROR
> 
> to double check. 

Hi Stefano,

Thanks for your prompt reply!

I know that the kernel has switched to -Werror by default. I use a largely 
customized .config and I can confirm you that CONFIG_WERROR is _not_ enabled:

xp4ns3@leap> grep CONFIG_WERROR .config
# CONFIG_WERROR is not set

>
> [...]
>
> As to why it started happening for you recently: maybe you just
> switched to gcc 11 and a newer version of clang? Can you try with
> gcc 10 if you have it still installed?

I had it not anymore installed, so I had to re-install gcc v10. With it
I ran "make clean && CC=gcc-10 make -j12" but it still triggers the same 
errors and the build still fails.

The last output line, just before exit, is:

make: *** [Makefile:1838: drivers] Error 2

Furthermore, I want to make you notice that I have no errors when I 
build Torvald's tree with gcc v11. In fact, I rebuilt it now again and 
got no failures.

Why is this issue showing only with staging-testing? I cannot yet see 
any reasonable explanation.

Any other ideas? If I'm not able to figure out what's happening, I won't
be able to contribute to staging anymore. Greg (reasonably) requires that
all the changes get built before sending patches, therefore, this issue
is a blocker. I'm losing the chance to be selected for the Outreachy
internship.

Since I have more or less 100 patches already in Torvald's tree, can I
be exempted from working on those 10 required patches for staging? 
Otherwise I could simply send 10 clean-up patches that I can confidently
send without trying to compile them. Or I can send patches for Torvald's
tree. I really don't know what to do.

As said above: any more ideas? 

Regards,

Fabio
 
> 
> -- 
> Stefano
> 




  reply	other threads:[~2022-04-01 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01   ` Fabio M. De Francesco [this message]
2022-04-01 12:57     ` Stefano Brivio
2022-04-01 13:07       ` Fabio M. De Francesco
2022-04-01 16:09         ` Alison Schofield
2022-04-01 17:58           ` Fabio M. De Francesco
2022-04-01 14:39       ` Fabio M. De Francesco

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=3410190.V25eIC5XRa@leap \
    --to=fmdefrancesco@gmail.com \
    --cc=outreachy@lists.linux.dev \
    --cc=sbrivio@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox