From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package
Date: Thu, 14 Dec 2023 08:41:16 +0100 [thread overview]
Message-ID: <20231214084116.48e04ecf@windsurf> (raw)
In-Reply-To: <5EB6E748-BA27-414C-9AB0-434429B724BF@amd.com>
On Thu, 14 Dec 2023 05:29:47 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Thank you for your research. I had not looked into how to fix
> newlib, so that it installs to the correct place to begin with.
>
> From my side, I think patching newlib is clearly better because we
> can try to upstream the patch to newlib. Once upstream, no patch or
> fix up hack will be needed anymore when we bump to a newer newlib
> version.
>
> I will test this patch with your branch as well to verify that we can
> remove my fix up post installation hack. If this patch works, I
> propose going with the patch.
Well, the thing is that there is probably a reason why upstream does
not install headers/libs in the standard location and decides to go
with this custom tooldir thing. So I'm really not sure changing this
will be upstreamable. Or perhaps by making it configurable, so that it
can be overridden using a ./configure option?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-14 7:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 7:34 [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 02/10] package/gcc-bare-metal: " Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 03/10] package/newlib-bare-metal: " Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 04/10] toolchain/toolchain-bare-metal-buildroot: new toolchain Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 05/10] boot/zynqmp-firmware: new boot firmware Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 06/10] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 07/10] configs/zynqmp*: build pmufw source Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 08/10] boot/versal-firmware: new boot firmware Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 09/10] configs/versal_vck190_defconfig: build plm and psmfw source Neal Frager via buildroot
2023-12-04 7:34 ` [Buildroot] [PATCH v8 10/10] package/versal-firmware: remove package Neal Frager via buildroot
2023-12-13 22:28 ` [Buildroot] [PATCH v8 01/10] package/binutils-bare-metal: new package Thomas Petazzoni via buildroot
2023-12-14 5:29 ` Frager, Neal via buildroot
2023-12-14 7:41 ` Thomas Petazzoni via buildroot [this message]
2023-12-14 7:51 ` Frager, Neal via buildroot
2023-12-14 7:58 ` Thomas Petazzoni via buildroot
2023-12-14 8:12 ` Frager, Neal via buildroot
2023-12-14 9:15 ` Thomas Petazzoni via buildroot
2023-12-14 14:43 ` Frager, Neal via buildroot
2023-12-15 9:40 ` Frager, Neal via buildroot
2023-12-14 7:10 ` Frager, Neal via buildroot
2023-12-14 7:48 ` Thomas Petazzoni via buildroot
2023-12-14 7:57 ` Frager, Neal via buildroot
2024-01-12 7:20 ` Frager, Neal via buildroot
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=20231214084116.48e04ecf@windsurf \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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.