From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Stefan Lippers-Hollmann <s.L-H@gmx.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ar9170-fw
Date: Sat, 01 May 2010 04:38:52 -0400 [thread overview]
Message-ID: <4BDBE89C.20406@dlasys.net> (raw)
In-Reply-To: <201005010323.53295.s.L-H@gmx.de>
On 04/30/2010 09:23 PM, Stefan Lippers-Hollmann wrote:
> Hi
>
> I assume your host's /bin/sh is not bash.
>
ubuntu default
ls -al /bin/sh
lrwxrwxrwx 1 root root 4 2010-04-02 01:25 sh -> dash
I have bumped into similar problems with buildroot.
Is there a serious downside to linking /bin/sh to bash ?
> ---------------------------------------------------------------------------
>
> ar9170.fw: fix bashisms while building the cross toolchain.
>
> Signed-off-by: Stefan Lippers-Hollmann<s.l-h@gmx.de>
>
> --- a/toolchain/Makefile
> +++ b/toolchain/Makefile
> @@ -31,7 +31,8 @@ src/newlib-$(NEWLIB_VER): src/$(NEWLIB_T
>
> src/gcc-$(GCC_VER): src/$(GCC_TAR) src/newlib-$(NEWLIB_VER)
> tar -C src -xjf $<
> - ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/{newlib,libgloss} $@
> + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/newlib $@
> + ln -s $(BASEDIR)/src/newlib-$(NEWLIB_VER)/libgloss $@
>
> binutils: src/binutils-$(BINUTILS_VER)
> mkdir -p build/binutils
>
> ---------------------------------------------------------------------------
>
> While you're at it, I'd suggest to bump the versions for the required
> cross-build environment as well, as it noticably improves stability of the
> firmware images built by it (still not perfectly, but better).
>
> ---------------------------------------------------------------------------
>
> ar9170.fw: update cross-toolchain.
>
> Updating the toolchain improves stability of the built firmware images
> significantly.
>
> * gcc-4.4.4
> * binutils-2.20.1
> * newlib 1.18.0
>
> Signed-off-by: Stefan Lippers-Hollmann<s.l-h@gmx.de>
>
> --- a/toolchain/Makefile
> +++ b/toolchain/Makefile
> @@ -1,12 +1,12 @@
> -BINUTILS_VER=2.19.1
> +BINUTILS_VER=2.20.1
> BINUTILS_URL=http://mirrors.kernel.org/gnu/binutils/binutils-$(BINUTILS_VER).tar.bz2
> BINUTILS_TAR=binutils-$(BINUTILS_VER).tar.bz2
>
> -NEWLIB_VER=1.17.0
> +NEWLIB_VER=1.18.0
> NEWLIB_URL=ftp://sources.redhat.com/pub/newlib/newlib-$(NEWLIB_VER).tar.gz
> NEWLIB_TAR=newlib-$(NEWLIB_VER).tar.gz
>
> -GCC_VER=4.3.3
> +GCC_VER=4.4.4
> GCC_URL=http://mirrors.kernel.org/gnu/gcc/gcc-$(GCC_VER)/gcc-core-$(GCC_VER).tar.bz2
> GCC_TAR=gcc-core-$(GCC_VER).tar.bz2
>
> ---------------------------------------------------------------------------
>
> Regards
> Stefan Lippers-Hollmann
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.587.7774 dhlii@dlasys.net http://www.dlasys.net
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2010-05-01 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 0:15 ar9170-fw David H. Lynch Jr.
2010-05-01 1:23 ` ar9170-fw Stefan Lippers-Hollmann
2010-05-01 5:43 ` ar9170-fw Johannes Berg
2010-05-01 8:38 ` David H. Lynch Jr. [this message]
2010-05-01 10:11 ` ar9170-fw David H. Lynch Jr.
2010-05-01 11:42 ` ar9170-fw Stefan Lippers-Hollmann
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=4BDBE89C.20406@dlasys.net \
--to=dhlii@dlasys.net \
--cc=linux-wireless@vger.kernel.org \
--cc=s.L-H@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).