From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000233]: host-sed-clean target always assumes that host-sed was built via build-sed-host-binary
Date: Mon, 12 Feb 2007 05:50:18 -0800 [thread overview]
Message-ID: <564da43a8aa0649cfaca684adf4d655e@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=233
======================================================================
Reported By: samrobb
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 233
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-22-2005 19:40 PDT
Last Modified: 02-12-2007 05:50 PST
======================================================================
Summary: host-sed-clean target always assumes that host-sed
was built via build-sed-host-binary
Description:
When a usable sed is detected on the host, the host-sed built target is set
to depend on use-sed-host-binary. The host-sed-clean and host-sed-dirclean
targets always assume that host version of sed was built using the
build-sed-host-binary target.
The attached patch make host-sed-clean and host-sed-dirclean empty targets
that call clean and dirclean targets that depend on the intial sed build
type.
======================================================================
----------------------------------------------------------------------
samrobb - 04-22-05 19:56
----------------------------------------------------------------------
Sorry - this isn;t (and shouldn't be) marked as arch-specific.
----------------------------------------------------------------------
vapier - 09-07-05 17:39
----------------------------------------------------------------------
fixed in a slightly different way, thanks
Issue History
Date Modified Username Field Change
======================================================================
04-22-05 19:40 samrobb New Issue
04-22-05 19:40 samrobb File Added: host-sed-clean.patch
04-22-05 19:56 samrobb Note Added: 0000183
09-07-05 17:39 vapier Note Added: 0000503
09-07-05 17:39 vapier Status assigned => closed
09-07-05 17:39 vapier Resolution open => fixed
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=564da43a8aa0649cfaca684adf4d655e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox