Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 18 Dec 2022 14:39:35 +0100	[thread overview]
Message-ID: <87sfhcomp4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABBCHidJG84Y_tpnSAE7t2qksEj4izv_TRMRLxfNcbADDUw05A@mail.gmail.com> (John Lemonovich's message of "Mon, 12 Dec 2022 11:50:10 -0500")

>>>>> "John" == John Lemonovich <lemonoje@gmail.com> writes:

Hello,

 > I am trying to build a rootfs for an Intel SOC FPGA (Arria 10) using
 > buildroot.  I've had success in the past but am now trying to build a newer
 > version FS (Buildroot 2019.11.3 Configuration) and I get stuck at this
 > error.  Does anyone know how to fix/address the error?  I am adding IPv6
 > support, and I believe this is required for one or more of the networking
 > applications I'm including.  I have tried various external toolchains all
 > with the same result, and this output is from the setting  "Toolchain to be
 > downloaded and installed".

2019.11.3 is EOL, please move to 2022.02.x or 2022.11.x.

With that said, you somehow seem to have changed ARCH to upper case
ARM. Do you have any local modifications?

The host build system type comes from:

package/pkg-autotools.mk:
                --host=$$(GNU_TARGET_NAME) \

Where GNU_TARGET_NAME is defined as:

package/Makefile.in:
# Compute GNU_TARGET_NAME
GNU_TARGET_NAME = $(ARCH)-$(TARGET_VENDOR)-$(TARGET_OS)-$(LIBC)$(ABI)

And where ARCH comes from:

Makefile: ARCH := $(call qstrip,$(BR2_ARCH))

Which for your A9 system gets set in arch/Config.in.arm

config BR2_ARCH
        default "arm"           if BR2_arm
        default "armeb"         if BR2_armeb
        default "aarch64"       if BR2_aarch64
        default "aarch64_be"    if BR2_aarch64_be

So I am not sure how you end up with an upper case 'ARM'?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-12-18 13:39 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 [this message]
     [not found]   ` <CABBCHifyTV7PV20P8krtmnRaRtwBrLDPuDBej37=AbUmgi-mNg@mail.gmail.com>
2022-12-19 17:06     ` Peter Korsgaard
     [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=87sfhcomp4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox