Re: Libtool errors for librep 0.92.2 compilation

Christopher Roy Bratusek <[email protected]>
Newsgroups gmane.comp.window-managers.sawfish
Message-ID <1590795.rbygINoOEW@ambassador>
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 (application/pgp-signature, 490 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAABAgAGBQJQROMTAAoJEEudM3UFdUnieoIH/2g/TVni9tIAdhinVixbCeXO
O3etzk6cbiSgcYZJLebSadSR+Qp7i/ryT1/JyVqCpDhl+9rhuhHI7xCGlwchXKli
uSdBXhHD06H4BQeln1NlwbVkrJk0kAA+pFmLcTciKQt6xTfun1QE1UMRZIVFruW/
PCtGVkJ60TSYgqdmSOJzSmIQhyKDHUwYiTj9A8uPTUppXZ4CYcQdF4vFiXmPN1Nl
rgJDDO1LUMHZqKXUt/B9AWJrTpl8AEfW8KsNRqcPVMc2XmjwbdDtZ9jnc5VtKT9l
vjmOPdoVkJrg+c9LaRB6ECE9s4g8CITPmFq1ZRrq4vYQsAamzIrlLS+P5cXhYrY=
=Xiku
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.