From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000517]: Fix gcc-clean so it doesn't remove binutils binaries
Date: Mon, 12 Feb 2007 05:48:13 -0800 [thread overview]
Message-ID: <d949ac66cfc5a1a2ef3b09ddfe8564ad@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=517
======================================================================
Reported By: akvadrako
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 517
Category: Other
Reproducibility: N/A
Severity: tweak
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-28-2005 09:45 PDT
Last Modified: 02-12-2007 05:48 PST
======================================================================
Summary: Fix gcc-clean so it doesn't remove binutils binaries
Description:
this has one disadvantage, the gcc binaries are hardcoded in the makefile,
but I can't find a way to avoid that without gcc-clean being a completely
useless target, as it is now.
======================================================================
----------------------------------------------------------------------
vapier - 10-28-05 23:51
----------------------------------------------------------------------
hardcoding gcc-VER is not a good idea ... just change it to 'gcc*'
----------------------------------------------------------------------
akvadrako - 10-29-05 15:48
----------------------------------------------------------------------
Agreed. Here is an updated patch.
Issue History
Date Modified Username Field Change
======================================================================
10-28-05 09:45 akvadrako New Issue
10-28-05 09:45 akvadrako Status new => assigned
10-28-05 09:45 akvadrako Assigned To => uClibc
10-28-05 09:45 akvadrako File Added: br-gcc-clean-fixes.patch
10-28-05 23:51 vapier Note Added: 0000648
10-29-05 15:49 akvadrako Note Added: 0000649
10-29-05 15:50 akvadrako File Added: br-gcc-clean-fixes-v2.patch
01-27-06 14:50 akvadrako File Added: br-gcc-clean-fixes-v3.patch
02-10-06 10:28 prpplague Additional Information Updated
02-10-06 10:29 prpplague Status assigned => resolved
02-10-06 10:29 prpplague Resolution open => fixed
03-08-06 16:52 vapier Status resolved => closed
02-12-07 05:48 vapier Status closed => assigned
02-12-07 05:48 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:48 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=d949ac66cfc5a1a2ef3b09ddfe8564ad@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