From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16072] New: Make 4.4.1 breaks glibc 2.38 build when cross compiling for arm_hf
Date: Mon, 13 May 2024 23:05:41 +0000 [thread overview]
Message-ID: <bug-16072-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16072
Bug ID: 16072
Summary: Make 4.4.1 breaks glibc 2.38 build when cross
compiling for arm_hf
Product: buildroot
Version: 2024.02.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: farhandude@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
make 4.4.1 is showing some strange behavior when it comes to handling command
line variables. Buildroot passes 'install_root' command line variable to the
glibc build, this variable is processed in :
buildroot-2024.02.1/output/build/glibc-2.38-44-gd37c2b20a4787463d192b32041c3406c2bd91de0/build/config.make:
...
install_root = $(DESTDIR)
...
DESTDIR is empty
With make 4.4.1, install_root gets overridden in config.make
With make 4.2.1, install_root DOES NOT get overridden
Due to this overriding, glibc tries to install its artifacts in '/' which fails
Farhan
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-05-13 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 23:05 bugzilla [this message]
2024-05-13 23:08 ` [Buildroot] [Bug 16072] Make 4.4.1 breaks glibc 2.38 build when cross compiling for arm_hf bugzilla
2024-06-15 15:21 ` bugzilla
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=bug-16072-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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