From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] Makefile: add target to clean targetfs
Date: Wed, 11 Mar 2015 07:06:52 +0200 [thread overview]
Message-ID: <20150311050652.GB2177@tarshish> (raw)
In-Reply-To: <CAMQcK5Kz4_vyCVv3Xq9Sms7UWd2Qjew1c60bXZzkfn6f40QeNg@mail.gmail.com>
Hi Ryan,
On Tue, Mar 10, 2015 at 06:41:39PM -0500, Ryan Barnett wrote:
> > +1. You enabled +PACKAGE_OPENSSH+ to have a SSH server running on your
> > + board. But you figure out that +sshd+ does not run well on your
> > + target's architecture. Thus you decide to disable +PACKAGE_OPENSSH+
> > + and enable +PACKAGE_DROPBEAR+ instead. You run +make+, +openssh+
> > + gets built and installed. Problem: +openssh+ files are still present
> > + in +output/target+!
>
> One case that comes to mind here is that will this ensure that
> packages are installed in the correct order with dependencies? I am
> not exactly sure how the dependencies for packages works, but if you
> remove all the '.stamp_target_install' will that ensure that all the
> packages get installed in the correct order?
>
> Busybox is the package that comes to my mind first that we need to
> ensure the installation order. From testing your scenario outlined
> above it appears that busybox gets installed before even dropbear
> would get built which would ensure that any full version of busybox
> would get install correctly over the symlinks to busybox.
The package dependencies system should ensure the right installation order.
The following excerpts from package/pkg-generic.mk demonstrate that:
$(2)_TARGET_INSTALL_TARGET = $$($(2)_DIR)/.stamp_target_installed
...
$(1): $(1)-install
...
$(1)-install: $(1)-install-staging $(1)-install-target $(1)-install-images
...
$(1)-install-target: $$($(2)_TARGET_INSTALL_TARGET)
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-03-11 5:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 0:25 [Buildroot] [PATCH 1/1] Makefile: add target to clean targetfs Emeric Vigier
2015-03-10 4:45 ` Baruch Siach
2015-03-10 14:56 ` Emeric Vigier
2015-03-10 15:17 ` Baruch Siach
2015-03-10 19:28 ` [Buildroot] [PATCH v2 " Emeric Vigier
2015-03-10 23:41 ` Ryan Barnett
2015-03-11 5:06 ` Baruch Siach [this message]
2015-03-11 8:22 ` Angelo Compagnucci
2015-03-11 8:58 ` Baruch Siach
2015-03-12 8:32 ` Angelo Compagnucci
2015-03-12 14:56 ` Emeric Vigier
2015-03-12 14:44 ` Emeric Vigier
2015-03-12 14:46 ` Ryan Barnett
2015-03-12 8:36 ` Angelo Compagnucci
2015-03-12 15:59 ` Jérôme Oufella
2015-04-27 0:45 ` [Buildroot] [PATCH v3 " Emeric Vigier
2015-04-27 4:11 ` Baruch Siach
2015-04-28 14:36 ` Emeric Vigier
2015-04-27 8:28 ` Andreas Naumann
2015-04-28 15:06 ` Emeric Vigier
2015-07-14 21:56 ` Emeric Vigier
2015-07-16 15:15 ` Emeric Vigier
2015-07-23 20:51 ` Andreas Naumann
2015-10-04 16:56 ` Arnout Vandecappelle
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=20150311050652.GB2177@tarshish \
--to=baruch@tkos.co.il \
--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.