public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: ckim@etri.re.kr
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: toolchain name for building linux kernel?
Date: Tue, 17 Nov 2020 01:30:34 -0500	[thread overview]
Message-ID: <227797.1605594634@turing-police> (raw)
In-Reply-To: <06ca01d6bca3$ac434830$04c9d890$@etri.re.kr>


[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]

On Tue, 17 Nov 2020 14:37:00 +0900, ckim@etri.re.kr said:

> Some years ago, I used to use sparc-ab-elf- to build linux kernel.

That will probably build a kernel for the Sun SPARC architecture...

> Recently, I found a website that I should use aarch64-linux-gnu tool to
> build the kernel.
>
> I tried following it and it generated vmlinux file. (I can't find the web
> page link, but I'm sure I wrote that procedure down when I built vmlinux)

That vmlinux file will only be useful for a 64-bit ARM architecture.

What sort of machine are you going to run the newly built kernel on,
and what sort of machine are you using for the build?

(If you're building on the system you'll be booting it on, the distro's gcc and make
commands should be sufficient)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-11-17  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  5:37 toolchain name for building linux kernel? ckim
2020-11-17  6:30 ` Valdis Klētnieks [this message]
2020-11-18  5:17   ` ckim
2020-11-19  9:30     ` ckim

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=227797.1605594634@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=ckim@etri.re.kr \
    --cc=kernelnewbies@kernelnewbies.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