From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] fs/iso9660: remove obsolete code
Date: Mon, 26 Jan 2015 23:27:10 +0100 [thread overview]
Message-ID: <20150126232710.0586db05@free-electrons.com> (raw)
In-Reply-To: <1421697177-12995-2-git-send-email-nrubinstein@aldebaran.com>
Dear No? Rubinstein,
On Mon, 19 Jan 2015 20:52:56 +0100, No? Rubinstein wrote:
> This rule is superseded by a rule defined in fs/common.mk:
>
> rootfs-$(1)-show-depends:
> @echo $$(ROOTFS_$(2)_DEPENDENCIES)
>
> Signed-off-by: No? Rubinstein <nrubinstein@aldebaran.com>
No, this is not correct, because iso9660.mk unfortunately does not use
the fs/common.mk code. See the comment at the top of the iso9660.mk
file:
################################################################################
#
# Build the iso96600 root filesystem image
#
# Cannot be converted to the ROOTFS_TARGET infrastructure, because of
# the temporary construction in ISO9660_TARGET_DIR.
#
################################################################################
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-26 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 19:52 [Buildroot] [PATCH 1/3] fs/iso9660: allow building a hybrid ISO image Noé Rubinstein
2015-01-19 19:52 ` [Buildroot] [PATCH 2/3] fs/iso9660: remove obsolete code Noé Rubinstein
2015-01-26 22:27 ` Thomas Petazzoni [this message]
2015-01-19 19:52 ` [Buildroot] [PATCH 3/3] docs/manual/beyond-buildroot: building and testing live-CDs Noé Rubinstein
2015-02-02 20:40 ` Thomas De Schampheleire
2015-07-10 17:18 ` Thomas Petazzoni
2015-02-02 20:39 ` [Buildroot] [PATCH 1/3] fs/iso9660: allow building a hybrid ISO image Thomas De Schampheleire
2015-02-03 9:43 ` Noé RUBINSTEIN
2015-02-03 14:35 ` Thomas De Schampheleire
2015-02-02 21:13 ` Arnout Vandecappelle
2015-02-03 14:15 ` 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=20150126232710.0586db05@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.