linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
Date: Tue, 30 Mar 2021 15:40:37 +0200	[thread overview]
Message-ID: <YGMqVc+DyVyT9DtW@kroah.com> (raw)
In-Reply-To: <CAGgoGu5xT6sADCpj7J7tJMfsw1WU4BA=3YB8SGS-+kf+P4xyNw@mail.gmail.com>

On Tue, Mar 30, 2021 at 03:23:10PM +0200, Fawad Lateef wrote:
> So can I still use kernel-3.4 compiled with gcc-5.5, and boot full
> user-space with gcc-9.1?

Yes, of course.

> I was expecting it to be possible but might not work due to
> incompatibility? As I know that when I tried to compile buildroot-2019
> (with latest version of openssl and others) it needs kernel headers
> and then I likely can't use 3.4 kernel.

buildroot might be different, as that is how you are building your whole
system, but there is no dependency on the kernel and userspace to use
the same version of the compiler.  Otherwise everyone would have to
rebuild the world for every time they updated their kernel, this isn't
the BSDs :)

thanks,

greg k-h

  reply	other threads:[~2021-03-30 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28 20:20 Compiling kernel-3.4.xxx with gcc-9.x. Need some help Fawad Lateef
     [not found] ` <CAHp75VdT9XeOgY3Tt+wo5bSRh-qdTfcaHFf7uuXotL1FqqF_mA@mail.gmail.com>
2021-03-28 21:02   ` Fawad Lateef
2021-03-29  4:57 ` Greg KH
2021-03-29 19:20   ` Fawad Lateef
2021-03-29 19:35     ` Greg KH
2021-03-29 20:06     ` Arnd Bergmann
2021-03-30 13:23       ` Fawad Lateef
2021-03-30 13:40         ` Greg KH [this message]
2021-04-18 17:25           ` Fawad Lateef
2021-04-18 18:36             ` Willy Tarreau
2021-03-30 14:22         ` Arnd Bergmann

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=YGMqVc+DyVyT9DtW@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@kernel.org \
    --cc=fawadlateef@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).