From mint-bounce@lists.fishpool.fi Sun May 10 11:43:52 2009 From: Eero Tamminen Organization: Koti To: mint@lists.fishpool.fi Subject: Re: [MiNT] mintlib Makefile requires bash as shell Date: Sun, 10 May 2009 18:38:10 +0300 User-Agent: KMail/1.9.9 References: <20090510103946.2e2a4e59@phineus> In-Reply-To: <20090510103946.2e2a4e59@phineus> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905101838.11025.oak@helsinkinet.fi> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: oak@helsinkinet.fi Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hi, On Sunday 10 May 2009, Thomas Huth wrote: > After some investigation, I've found out that the problem is due > to /bin/sh not being the bash on Ubuntu (and Debian), but an > alternative shell called "dash". Bash symlinks /bin/sh by default still in Debian (Lenny i.e. stable). > When I compile the mintlib with "make SHELL=/bin/bash", everything > works fine. > > The problem seems to be the -I$(<../includepath): When I type "echo > $(<../includepath)" in the bash, I get the paths. When I type it in > dash, I get no output at all. > > When I replace the "<" by "cat " at the corresponding places in > buildrules and checkrules, it also compiles fine with the dash again. > > Don't know if this should be fixed in mintlib or rather in dash, but I > though I'd let you know in case somebody else wants to cross-compile > the mintlib on Ubuntu or Debian. Debian/Ubuntu have "checkbashisms" script in the "devscripts" package[1] which can be used to check whether scripts use non-standard Bash stuff. - Eero [1] http://packages.debian.org/lenny/devscripts