On Tuesday 04 September 2012 01:08:15 Rafal Kolanski wrote: > On 24/08/12 06:48, Tomasz Gajewski wrote: > > Christopher Roy Bratusek <[email protected]> writes: > >> You can either do: > >> > >> ./autogen [configureflags] > >> > >> or > >> > >> make SHELL=/bin/bash > > > > I've just came across this problem and found another workaround: > > > > export CONFIG_SHELL="/bin/bash" > > > > This allows to build from deb src packages from: > > > > deb-src http://apt.nanolx.org/ photonic main > > > > without any other problems. > > Thank you, that helps a lot. > > However, I still think that if Makedefs.in requests /bin/sh for the > shell, and then we end up using bash-only features, then that is not > quite right. All it takes is changing one line, and librep builds > without any surprises (dpkg-buildpackage -rfakeroot): > > --- a/Makedefs.in > +++ b/Makedefs.in > @@ -20,7 +20,7 @@ > > version=@version@ > libversion=@libversion@ > -SHELL=/bin/sh > +SHELL=/bin/bash > > Is there any reason that that this is not desired behaviour? > > Sincerely, > > Rafal Kolanski.
The reason why we call /bin/sh is, that this bug is not caused by bashisms from Sawfish, it's a bug in autoconf. Using Bash is just a work-around for faulty autoconf versions. Regards
signature.asc
Description: This is a digitally signed message part.
