Bug 365397

Summary:	sys-apps/acl-2.2.51 configure fails when /bin/sh points is dash and not bash
Product:	Gentoo Linux	Reporter:	Piotr Karbowski (RETIRED) <slashbeast>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED FIXED
Severity:	major	CC:	alecm
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	366671
Attachments:	Ebuild fix, adding CONFIG_SHELL to econf. build.log config.log emerge --verbose --info

Description Piotr Karbowski (RETIRED) gentoo-dev

2011-04-30 10:27:32 UTC

Created attachment 271615 [details, diff]
Ebuild fix, adding CONFIG_SHELL to econf.

I am unable to build the current acl-2-2.51 on all my system because of *real* /bin/sh (dash). If I put bash as /bin/sh it works.

The issue is because libtool or a friend of libtool failing to set proper shell.

The very beginning of make:
>>> Source configured.
>>> Compiling source in /var/portage/tmp/portage/sys-apps/acl-2.2.51/work/acl-2.2.51 ...
make --quiet -j4 
eval: 1: base_compile+= x86_64-pc-linux-gnu-gcc: not found
eval: 1: base_compile+= -O2: not found
eval: 1: base_compile+= -pipe: not found
eval: 1: base_compile+= -march=native: not found
eval: 1: base_compile+= -mtune=generic: not found

And more, the issue is that libtool script in acl dir (generated while running configure) have bashism (variable+=' added content). If after configure I grep for files with 'bash' it find some. The issue is that configure/libtool/some magic that I have no idea about use bash to generate libtool script, with bashism, and then it running it with /bin/sh.

As a solution I found that I can pass CONFIG_SHELL variable to econf (configure) to stop it from autodetecting, it works. In fact, the 2.2.49-r1 version works as it should.

Comment 1 Jeroen Roovers (RETIRED) gentoo-dev

2011-05-02 02:34:07 UTC

Please document why you CC developers or do not do it at all.

Comment 2 SpanKY gentoo-dev

2011-05-02 03:01:21 UTC

Comment on attachment 271615 [details, diff]
Ebuild fix, adding CONFIG_SHELL to econf.

we're not doing this

Comment 3 SpanKY gentoo-dev

2011-05-02 03:02:02 UTC

post the full build log as well as `emerge --info --verbose` and the config.log

Comment 4 Piotr Karbowski (RETIRED) gentoo-dev

2011-05-02 07:28:25 UTC

Created attachment 271851 [details]
build.log

Comment 5 Piotr Karbowski (RETIRED) gentoo-dev

2011-05-02 07:28:42 UTC

Created attachment 271853 [details]
config.log

Comment 6 Piotr Karbowski (RETIRED) gentoo-dev

2011-05-02 07:31:28 UTC

Created attachment 271855 [details]
emerge --verbose --info

Comment 7 Piotr Karbowski (RETIRED) gentoo-dev

2011-05-02 07:38:49 UTC

(In reply to comment #1)
> Please document why you CC developers or do not do it at all.

Because acl have 'Maintainer: base-system@gentoo.org'. As there is option to CC people I am using it to reduce time before the real developers will see this bugreport, somethinges bugwranglers misasigning bugs like they did with fcron and until I cc'ed flameeyes the bug was there, for months. There are bugs with Status:NEW for a years here, as long as there is option to CC and I am pretty sure who should I CC I am doing it.


(In reply to comment #3)
> post the full build log as well as `emerge --info --verbose` and the config.log

Done, also, I reproduced it with clean stage3, just emerge dash, deploy it as /bin/sh and emerge acl-2.2.51.

Comment 8 SpanKY gentoo-dev

2011-05-16 02:46:23 UTC

*** Bug 366393 has been marked as a duplicate of this bug. ***

Comment 9 SpanKY gentoo-dev

2011-05-16 06:06:04 UTC

probably fixed now

http://sources.gentoo.org/sys-apps/acl/acl-2.2.51.ebuild?r1=1.1&r2=1.2
http://sources.gentoo.org/sys-apps/acl/files/acl-2.2.51-config-shell.patch?rev=1.1

Comment 10 Piotr Karbowski (RETIRED) gentoo-dev

2011-05-16 17:21:51 UTC

Yeah, fixed. Thanks.