From: Peter Korsgaard <peter@korsgaard.com>
To: John Lemonovich <lemonoje@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] error - machine `ARM-buildroot' not recognized for libpcap
Date: Mon, 19 Dec 2022 18:06:00 +0100 [thread overview]
Message-ID: <877cyniarr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABBCHifyTV7PV20P8krtmnRaRtwBrLDPuDBej37=AbUmgi-mNg@mail.gmail.com> (John Lemonovich's message of "Mon, 19 Dec 2022 11:31:34 -0500")
>>>>> "John" == John Lemonovich <lemonoje@gmail.com> writes:
Hello,
> Peter,
> Thank you for the reply! I'm not very familiar with the process so I'm
> relying on the Beginner's Guide and Intel FPGA documentation. I have built
> the rootfs successfully for my Arria10 device in the past using buildroot
> and busybox, but it's been several years since the last time.
> I am getting the upper case ARM from the Intel FPGA documentation - all
> through their guides it shows it as upper case: (see building the root
> filesystem tab of this link for example)
> https://www.rocketboards.org/foswiki/Documentation/EmbeddedLinuxBeginnerSGuide
> Nonetheless, the upper case is apparently incorrect, and I have tried to
> build with no ARCH specified, which, should default to just 'ARCH=arm',
> correct?
Yes, you should not define ARCH=<something> (or export it in your
environment) when you use Buildroot. The architecture is specified by
running make menuconfig.
> I am selecting external toolchain as
> :gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf
> My kernel is 5.4.13 from Linux-socfpga
> I just did a fresh checkout of 2022.02.7 , added a few networking
> utilities and options, selected external toolchain and prefix and now I get
> this error:
> Incorrect selection of kernel headers: expected 5.4.x, got 4.10.x
Your runtime kernel may be 5.4.13, but the Linaro toolchain you mention
above has been built against a 4.10.3 kernel:
cat gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/libc/usr/include/linux/version.h
#define LINUX_VERSION_CODE 264707
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
printf '0x%x\n' 264707
0x40a03
So you need to configure 'External toolchain kernel headers series' as
4.10.x (or alternatively use one of the newer preconfigured toolchains).
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-19 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:50 [Buildroot] error - machine `ARM-buildroot' not recognized for libpcap John Lemonovich
2022-12-18 13:39 ` Peter Korsgaard
[not found] ` <CABBCHifyTV7PV20P8krtmnRaRtwBrLDPuDBej37=AbUmgi-mNg@mail.gmail.com>
2022-12-19 17:06 ` Peter Korsgaard [this message]
[not found] ` <CABBCHic7A3dVoJLXKDFLkq4mYVzGuUbbuPR0EDav8ppHpw6x6g@mail.gmail.com>
2022-12-19 17:08 ` Peter Korsgaard
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=877cyniarr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=lemonoje@gmail.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.