From: Jan Kiszka <jan.kiszka@web.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
otus-devel@lists.madwifi-project.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ar9170-fw: Use self-built toolchain by default
Date: Sat, 06 Jun 2009 20:32:20 +0200 [thread overview]
Message-ID: <4A2AB634.9020904@web.de> (raw)
In-Reply-To: <1244311169.17485.16.camel@johannes.local>
[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]
Johannes Berg wrote:
> On Sat, 2009-06-06 at 19:13 +0200, Jan Kiszka wrote:
>> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
>> ---
>>
>> Makefile | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index e0113d6..5fc0868 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -1,7 +1,7 @@
>> # Type is AP or STA
>> TYPE ?= STA
>>
>> -PFX ?= /usr/share/gnush_v0901_elf-1/bin/sh-elf-
>> +PFX ?= $(shell pwd)/toolchain/inst/bin/sh-elf-
>
> This will fail in strange ways if the user doesn't first manually build
> the toolchain... It does that if you don't have it installed, but it
> would be nice to tell them to build it?
>
What about this? There are probably smarter ways to achieve this, but
I'm not speaking fluently 'make'.
---------->
Switch the default to our own toolchain and provide a hint in case it's
missing or the provided PFX does not point to a gcc.
Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
---
Makefile | 12 +++++++-----
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/Makefile b/Makefile
index e0113d6..6316f62 100644
--- a/Makefile
+++ b/Makefile
@@ -1,11 +1,13 @@
# Type is AP or STA
TYPE ?= STA
-PFX ?= /usr/share/gnush_v0901_elf-1/bin/sh-elf-
-CC = $(PFX)gcc
-LD = $(PFX)ld
-AS = $(PFX)as
-OBJCOPY = $(PFX)objcopy
+PFX ?= $(shell pwd)/toolchain/inst/bin/sh-elf-
+VALID_PFX = $(if $(wildcard $(PFX)gcc), $(PFX), \
+ $(error Error: sh2 gcc not found. To build your own, invoke 'make -C toolchain'.))
+CC = $(VALID_PFX)gcc
+LD = $(VALID_PFX)ld
+AS = $(VALID_PFX)as
+OBJCOPY = $(VALID_PFX)objcopy
# CPU is a Little endian sh2a-nofpu-or-sh3-nommu
CPU = -m2
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-06 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 17:13 [PATCH 2/2] ar9170-fw: Use self-built toolchain by default Jan Kiszka
2009-06-06 17:59 ` Johannes Berg
2009-06-06 18:32 ` Jan Kiszka [this message]
2009-06-06 18:47 ` Johannes Berg
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=4A2AB634.9020904@web.de \
--to=jan.kiszka@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=otus-devel@lists.madwifi-project.org \
/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.