From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000365]: $(BUILD_DIR)/busybox/.unpacked does not depend on $(BUILD_DIR)
Date: Mon, 12 Feb 2007 05:50:22 -0800 [thread overview]
Message-ID: <643f4187697158c86369d571d6c34ea6@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=365
======================================================================
Reported By: uzeisberger
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 365
Category: Architecture Specific
Reproducibility: always
Severity: trivial
Priority: normal
Status: assigned
======================================================================
Date Submitted: 08-03-2005 01:06 PDT
Last Modified: 02-12-2007 05:50 PST
======================================================================
Summary: $(BUILD_DIR)/busybox/.unpacked does not depend on
$(BUILD_DIR)
Description:
If I call
$ make `pwd`/build_arm/busybox/.unpacked
(after a matching configuration, s.t. BUILD_DIR=pwd`/build_arm/) the
resulting tar command fails because $(BUILD_DIR) does not exist.
The easy fix would be to add $(BUILD_DIR) to the dependencies of
busybox/.unpacked
The more complete one would be to revise all Makefile snipplets to add
this dependency
======================================================================
----------------------------------------------------------------------
vapier - 08-05-05 23:01
----------------------------------------------------------------------
why exactly is this an issue ?
----------------------------------------------------------------------
vapier - 09-07-05 17:22
----------------------------------------------------------------------
dont see any reason for this at this time ... all packages would have to be
updated, not just busybox
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 01:06 uzeisberger New Issue
08-03-05 01:06 uzeisberger Status new => assigned
08-03-05 01:06 uzeisberger Assigned To => uClibc
08-05-05 23:01 vapier Note Added: 0000387
09-07-05 17:22 vapier Note Added: 0000499
09-07-05 17:22 vapier Status assigned => closed
09-07-05 17:22 vapier Resolution open => won't fix
02-12-07 05:50 vapier Status closed => assigned
02-12-07 05:50 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=643f4187697158c86369d571d6c34ea6@bugs.busybox.net \
--to=bugs@busybox.net \
--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.