From: Ulrich Hecht <uli@suse.de>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] file update, fixes
Date: Fri, 15 Dec 2006 16:04:20 +0100 [thread overview]
Message-ID: <200612151604.20630.uli@suse.de> (raw)
In-Reply-To: <20061215143107.GC13757@aon.at>
Hi!
On Friday 15 December 2006 15:31, Bernhard Fischer wrote:
> Another candidate.
>
> FILE_SOURCE_DIR:=$(BUILD_DIR)/file-$(FILE_VER)
> FILE_DIR1:=$(BUILD_DIR)/file-$(FILE_VER)-target
> FILE_DIR2:=$(TOOL_BUILD_DIR)/file-$(FILE_VER)
>
> Don't forget to CC="$(HOSTCC)" for the -host version.
>
> Please resend? :)
Alright, alright. But I would sure like to know what a "host file" is
good for. I don't see anything that depends on it.
CU
Uli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: file.patch
Type: text/x-diff
Size: 2710 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061215/62370ec5/attachment.bin
prev parent reply other threads:[~2006-12-15 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 13:29 [Buildroot] [patch] file update, fixes Ulrich Hecht
2006-12-15 14:31 ` Bernhard Fischer
2006-12-15 15:04 ` Ulrich Hecht [this message]
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=200612151604.20630.uli@suse.de \
--to=uli@suse.de \
--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