From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001042]: package/Makefile.in sets wrong TARGET_PATH
Date: Mon, 12 Feb 2007 05:44:48 -0800 [thread overview]
Message-ID: <8b6d264dac516ee09f94feb31694ce1a@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=1042
======================================================================
Reported By: belandor
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1042
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 09-21-2006 06:23 PDT
Last Modified: 02-12-2007 05:44 PST
======================================================================
Summary: package/Makefile.in sets wrong TARGET_PATH
Description:
in buildroot svn revision {2006-09-21}, package/Makefile.in sets
TARGET_PATH=$(STAGING_DIR)/bin:$(TOOL_BUILD_DIR)/bin:/bin:/sbin:/usr/bin:/usr/sbin:$(PATH)
This makes it impossible to use a gcc which is not installed in the system
to compile uClibc (e.g. if /usr/bin/gcc does not support ada, it is not
possible to provide an ada capable gcc in the path and install)
This should be changed into
TARGET_PATH=$(STAGING_DIR)/bin:$(TOOL_BUILD_DIR)/bin:$(PATH)
If /bin:/sbin:/usr/bin:/usr/sbin are not in PATH, then this has probably
good reasons and buildroot should not attempt to include them in the
TARGET_PATH. - Otherwise they should come _AFTER_ the inclusion of PATH.
======================================================================
----------------------------------------------------------------------
bernhardf - 09-30-06 14:09
----------------------------------------------------------------------
Sounds reasonable. Done.
Issue History
Date Modified Username Field Change
======================================================================
09-21-06 06:23 belandor New Issue
09-21-06 06:23 belandor Status new => assigned
09-21-06 06:23 belandor Assigned To => uClibc
09-30-06 14:09 bernhardf Status assigned => closed
09-30-06 14:09 bernhardf Note Added: 0001673
09-30-06 14:09 bernhardf Resolution open => fixed
02-12-07 05:44 vapier Status closed => assigned
02-12-07 05:44 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:44 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=8b6d264dac516ee09f94feb31694ce1a@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