Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Andrey Nechypurenko <andreynech@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Build error with 2021.11.x
Date: Mon, 07 Feb 2022 19:43:42 +0100	[thread overview]
Message-ID: <87ee4esejl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOiXNkCq0M11qPm=nyJdLgFPRSf7Y+rWfhgGfPLuXsWk4ziCaw@mail.gmail.com> (Andrey Nechypurenko's message of "Mon, 7 Feb 2022 11:33:16 +0100")

>>>>> "Andrey" == Andrey Nechypurenko <andreynech@gmail.com> writes:

 > Hello Buildrooters,
 > I just updated Buildroot from 2021.08.x to 2021.11.x and got build problems.
 > In particular, ICU library could not be built. I was trying with ARM
 > external toolchain and with Linaro 2018 getting the same error.

 > It would be great if someone can provide hints on what might be wrong and
 > how to fix the problem. Below are the relevant logs and information.

 > Thank you,
 > Andrey.

 >>>> icu 69-1 Configuring

[snip]

 > INTLTOOL_PERL=/usr/bin/perl CFLAGS="-D_LARGEFILE_SOURCE
 > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -O3 -g0
 > -D_FORTIFY_SOURCE=1
 > -I/home/and/p2/build/prodx/host/arm-buildroot-linux-gnueabihf/sysroot/usr/include/drm"
 > LDFLAGS=" -ldrm" ac_cv_lbl_unaligned_fail=yes

Hmm, is this a pristine upstream Buildroot 2021.11 without any external
packages? You seem to be passing some extra CFLAGS / LDFLAGS to the
configure script.

Variables like TARGET_CONFIGURE_OPTS are global, so you cannot change it
in a custom package without causing problems, like this:

 > configure:3057: checking whether the C compiler works
 > configure:3079:
 > /home/and/p2/build/prodx/host/bin/arm-linux-gnueabihf-gcc
 > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -O3
 > -g0 -D_FORTIFY_SOURCE=1
 > -I/home/and/p2/build/prodx/host/arm-buildroot-linux-gnueabihf/sysroot/usr/include/drm
 > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
 > -ldrm conftest.c -latomic >&5
 > /home/and/p2/build/prodx/host/opt/ext-toolchain/bin/../lib/gcc/arm-linux-gnueabihf/7.3.1/../../../../arm-linux-gnueabihf/bin/ld:
 > cannot find -ldrm

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

  reply	other threads:[~2022-02-07 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 10:33 [Buildroot] Build error with 2021.11.x Andrey Nechypurenko
2022-02-07 18:43 ` Peter Korsgaard [this message]
2022-02-07 19:44   ` Andrey Nechypurenko

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=87ee4esejl.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=andreynech@gmail.com \
    --cc=buildroot@buildroot.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