From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/coreutils: allow building as individual binaries
Date: Thu, 20 Jun 2019 22:16:45 +0200 [thread overview]
Message-ID: <20190620201645.GK2216@scaer> (raw)
In-Reply-To: <20190620192137.DB4A482283@busybox.osuosl.org>
Thomas, Markus, All,
On 2019-06-20 21:04 +0200, Thomas Petazzoni spake thusly:
> We add configuration option BR2_PACKAGE_COREUTILS_INDIVIDUAL_BINARIES
> so that coreutils can be built and installed as individual binaries.
> It can be used if the target file system doesn't support symlinks or
> symlinks are undesirable.
[--SNIP--]
> @@ -111,16 +130,28 @@ COREUTILS_CONF_OPTS += --enable-no-install-program=stdbuf
> endif
>
> # link for archaic shells
> +ifeq ($(BR2_PACKAGE_COREUTILS_INDIVIDUAL_BINARIES),y)
> +define COREUTILS_CREATE_TEST_SYMLINK
> + ln -fs test $(TARGET_DIR)/usr/bin/[
> +endef
> +else
> define COREUTILS_CREATE_TEST_SYMLINK
> ln -fs coreutils $(TARGET_DIR)/usr/bin/[
> endef
> +endif
> COREUTILS_POST_INSTALL_TARGET_HOOKS += COREUTILS_CREATE_TEST_SYMLINK
If we are single-binary, then test is it self a symlink to coreutils
already, as done by the install of coreutils.
If we're multi-binary, then test is standalone.
So, in either case, doing the [ -> test symlink should have been valid,
no?
(sorry I did not reply earlier, I only thought about it after seeing
Thomas' split patches.)
Regards,
Yann E. MORIN.
> # gnu thinks chroot is in bin, debian thinks it's in sbin
> +ifeq ($(BR2_PACKAGE_COREUTILS_INDIVIDUAL_BINARIES),y)
> +define COREUTILS_FIX_CHROOT_LOCATION
> + mv $(TARGET_DIR)/usr/bin/chroot $(TARGET_DIR)/usr/sbin
> +endef
> +else
> define COREUTILS_FIX_CHROOT_LOCATION
> rm -f $(TARGET_DIR)/usr/bin/chroot
> ln -sf ../bin/coreutils $(TARGET_DIR)/usr/sbin/chroot
> endef
> +endif
> COREUTILS_POST_INSTALL_TARGET_HOOKS += COREUTILS_FIX_CHROOT_LOCATION
>
> $(eval $(autotools-package))
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-06-20 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 19:04 [Buildroot] [git commit] package/coreutils: allow building as individual binaries Thomas Petazzoni
2019-06-20 20:16 ` Yann E. MORIN [this message]
2019-06-20 20:26 ` Markus Mayer
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=20190620201645.GK2216@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox