From: Whitney, Scott <scwhitn@amazon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Overlay not using a merged /usr?
Date: Fri, 21 Feb 2020 17:17:44 +0000 [thread overview]
Message-ID: <1582305463997.17600@amazon.com> (raw)
In-Reply-To: <87r1yqd31p.fsf@dell.be.48ers.dk>
That worked perfectly. Thanks very much, Peter!
Scott Whitney
________________________________________
From: Peter Korsgaard <jacmet@gmail.com> on behalf of Peter Korsgaard <peter@korsgaard.com>
Sent: Wednesday, February 19, 2020 10:12 AM
To: Whitney, Scott
Cc: buildroot at busybox.net
Subject: Re: Overlay not using a merged /usr?
>>>>> "Whitney," == Whitney, Scott <scwhitn@amazon.com> writes:
> Hello Buildroot community,
> I am working with a TI AM6548 SoC, and need to add some firmware
> (.elf) files so that they will end up in /lib/firmware/ti-pruss.
> These files get loaded into some special cores within the SoC to
> create additional Ethernet ports.
> I am using a Buildroot overlay with BR2_EXTERNAL, and tried to add the files under rootfs-overlay/lib/firmware/ti-pruss, i.e.:
> scwhitn at ud9a5a686d6f756:~/Projects/AR_Reflex3_Buildroot/overlay/board/control-carrier/rootfs-overlay$ ls lib/firmware/ti-pruss
> am65x-pru0-prueth-fw.elf am65x-rtu0-prueth-fw.elf
> am65x-pru1-prueth-fw.elf am65x-rtu1-prueth-fw.elf
> However, when I run make, I get the following error, and I'm not sure how to resolve it:
>>>> Sanity check in overlay /home/local/ANT/scwhitn/Projects/AR_Reflex3_Buildroot/overlay/board/control-carrier/rootfs-overlay
> ERROR: The overlay in
> /home/local/ANT/scwhitn/Projects/AR_Reflex3_Buildroot/overlay/board/control-carrier/rootfs-overlay
> is not using a merged /usr for the following directories: /lib
> Makefile:738: recipe for target 'target-finalize' failed
> make: *** [target-finalize] Error 1
You are presumably using a merged /usr (BR2_ROOTFS_MERGED_USR), where
/lib should be a symlink to /usr/lib, so when you add a rootfs overlay
containing a /lib directory this is no longer valid and it complains.
Simply put your files in the overlay under /usr/lib/.. instead.
> I'm using buildroot-2019.02.6. This is _urgent_; it's the last
> peripheral that we need to support before the project can be handed
> over to out client as complete.
You may consider moving to 2019.02.9 for a number of (security) fixes
since the 2019.02.6 release, and also notice that the 2019.02.x will go
end of life in approximately 1 month, so consider updating to 2020.02
(once released at the end of the month).
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-02-21 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:25 [Buildroot] Overlay not using a merged /usr? Whitney, Scott
2020-02-19 15:12 ` Peter Korsgaard
2020-02-21 17:17 ` Whitney, Scott [this message]
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=1582305463997.17600@amazon.com \
--to=scwhitn@amazon.com \
--cc=buildroot@busybox.net \
/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.