From: <ckim@etri.re.kr>
To: "'Valdis Klētnieks'" <valdis.kletnieks@vt.edu>
Cc: kernelnewbies@kernelnewbies.org
Subject: RE: toolchain name for building linux kernel?
Date: Thu, 19 Nov 2020 18:30:47 +0900 [thread overview]
Message-ID: <078801d6be56$a9b11cf0$fd1356d0$@etri.re.kr> (raw)
In-Reply-To: <074401d6bd6a$26c44bb0$744ce310$@etri.re.kr>
Hi Valdis, and all,
I tried it again, but I had error with aarch-linux-gnu- .
So I changed it with
export ARCH=arm64
export CROSS_COMPILE=aarch64-none-elf-
and then,
make defconfig
make vmlinux
and vmlinux was generated.
So the kernel was built with aarch64-non-elf- toolchain as I thought normal.
Maybe last time there was some mistake..
Thank you!
Chan Kim
> -----Original Message-----
> From: ckim@etri.re.kr <ckim@etri.re.kr>
> Sent: Wednesday, November 18, 2020 2:18 PM
> To: 'Valdis Klētnieks' <valdis.kletnieks@vt.edu>
> Cc: kernelnewbies@kernelnewbies.org
> Subject: RE: toolchain name for building linux kernel?
>
>
> Thanks for replying. Yes, at that time, it was sparc and this time it's
> aarch64. I'm building the kernel on x86_64 machine.
> So target is aarch64, host is x86_64.
> My question is about the end part (elf or linux).
> To build linux kernel, shouldn't it be elf? (using libraries for
baremetal,
> like newlib) And to build a application that'll run on linux, shouldn't it
> be linux?(using libraries for linux) Please see that last part of
> https://wiki.osdev.org/Target_Triplet.
> I wonder why the toolchain name that I built linux kernel ends with
-linux.
> Chan
>
> > -----Original Message-----
> > From: Valdis Kletnieks <valdis@vt.edu> On Behalf Of Valdis Kl?tnieks
> > Sent: Tuesday, November 17, 2020 3:31 PM
> > To: ckim@etri.re.kr
> > Cc: kernelnewbies@kernelnewbies.org
> > Subject: Re: toolchain name for building linux kernel?
> >
> > 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)
>
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-11-19 9: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
2020-11-18 5:17 ` ckim
2020-11-19 9:30 ` ckim [this message]
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='078801d6be56$a9b11cf0$fd1356d0$@etri.re.kr' \
--to=ckim@etri.re.kr \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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).