From: "Yann E. MORIN via buildroot" <buildroot@buildroot.org>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: Edgar Bonet <bonet@grenoble.cnrs.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] Compilation Issue with Commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4
Date: Sun, 30 Nov 2025 08:36:13 +0100 [thread overview]
Message-ID: <aSvz7eiTAwAEzNu_@landeda> (raw)
In-Reply-To: <CAH+XeQbz7B6QcQUnbH5x+M2bE=1snLkZXW4syQdZm-3H_AfaMQ@mail.gmail.com>
José, All,
On 2025-11-29 22:46 +0100, José Luis Salvador Rufo spake thusly:
> For disclosure, here is my build information that triggered the error:
>
> build log:
> ```
> [...]
> support/scripts/check-merged -t skeleton -u -b
> /usr/src/simplek8s/rootfs-skeleton
> The skeleton in -t is not properly setup:
> - /usr/bin should exist, be a directory, and not be a symlink
> - /usr/lib should exist, be a directory, and not be a symlink
> The skeleton in skeleton is not properly setup:
> - /usr/bin should exist, be a directory, and not be a symlink
> - /usr/lib should exist, be a directory, and not be a symlink
> The skeleton in -u is not properly setup:
> - /usr/bin should exist, be a directory, and not be a symlink
> - /usr/lib should exist, be a directory, and not be a symlink
> The skeleton in -b is not properly setup:
> - /usr/bin should exist, be a directory, and not be a symlink
> - /usr/lib should exist, be a directory, and not be a symlink
> [...]
> ```
[--SNIP--]
> Some configs:
> ```
> [...]
> BR2_ROOTFS_SKELETON_CUSTOM=y
> BR2_ROOTFS_SKELETON_CUSTOM_PATH="$(CONFIG_DIR)/rootfs-skeleton"
> BR2_ROOTFS_OVERLAY="$(CONFIG_DIR)/rootfs-overlay"
> [...]
> ```
Ah, so this is what I missed: use of a custom skeleton. I tested all
kinds of overlays, but forgot to test a custom skeleton.
So, it did not break for overlays, while it breaks for skeleton, but
that is not weird: the checks for the skeleton are strict, while they
are lax for the overlays. So, that's what causes the failure for you.
This is important information, that should have been given in the commit
log (maybe not so extensively, but still),
Thank you for the feedback! 👍
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-11-30 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 17:14 [Buildroot] Compilation Issue with Commit 793ebd5d28095c8df45a0d183d273d8a84b3f0a4 José Luis Salvador Rufo
2025-11-29 17:53 ` Yann E. MORIN via buildroot
2025-11-29 19:35 ` Edgar Bonet via buildroot
2025-11-29 20:23 ` Yann E. MORIN via buildroot
2025-11-29 20:38 ` José Luis Salvador Rufo
2025-11-29 21:46 ` José Luis Salvador Rufo
2025-11-30 7:36 ` Yann E. MORIN via buildroot [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=aSvz7eiTAwAEzNu_@landeda \
--to=buildroot@buildroot.org \
--cc=bonet@grenoble.cnrs.fr \
--cc=salvador.joseluis@gmail.com \
--cc=yann.morin.1998@free.fr \
/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