All of lore.kernel.org
 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 15:07:24 +0200	[thread overview]
Message-ID: <1943335.PIDvDuAF1L@leap> (raw)
In-Reply-To: <20220401145714.5a0d826f@elisabeth>

On venerdì 1 aprile 2022 14:57:14 CEST Stefano Brivio wrote:
> 
> Okay, then that's really an error.
> 
> It might simply be that the you're building some drivers on your
> staging tree that you're not building on the mainline tree.

Yes, this is why I've decided to use the .config that I have in Torvald's 
tree. They should only differ for the drivers/staging part and the suffix 
for vmlinuz.

Now it builds correctly with gcc11 :)

I must look carefully at the diff between the two files and figure out
what doesn't work.

However what really counts is that now I can go back to work with "staging".

Thanks for your time,

Fabio 




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

Thread overview: 13+ 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
2022-04-01 12:57     ` Stefano Brivio
2022-04-01 13:07       ` Fabio M. De Francesco [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-07-01 11:21 compilation errors Jean-Francois Moine
2008-02-05  2:59 Compilation errors Peter Teoh
1999-02-03 14:31 Richard Hartensveld
1999-02-03 17:12 ` Alex deVries
1999-02-03 20:43   ` Ulf Carlsson

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=1943335.PIDvDuAF1L@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 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.