Bugzilla Bug 220353

Apache fails to build with libtool-2.2.x with the following error:
ain  -c mod_authn_file.c && touch mod_authn_file.slo
/bin/sh /var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8/shlibtool
--silent --mode=link i686-pc-linux-gnu-gcc -pthread  -O2 -march=i686 -pipe
-mtune=i686  -L/usr/lib  -Wl,--as-needed -Wl,--no-as-needed    -o
mod_authn_file.la -rpath /usr/lib/apache2/modules -module -avoid-version 
mod_authn_file.lo
/bin/sh:
/var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8/shlibtool: No
such file or directory Error 127
make[4]: Leaving directory
`/var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8/modules/aaa'
make[3]: *** [shared-build-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8/modules/aaa'
make[2]: *** [shared-build-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8/modules'
make[1]: *** [shared-build-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/www-servers/apache-2.2.8-r2/work/httpd-2.2.8'
make: *** [all-recursive] Error 1

The patch in URL fixes the problem here. Please add it to our patchset.
Courtesy of Arfrever Frehtes Taifersar Arahesis.

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

The fix doesn't work, unfortunately.

I got around it by reemerging libtool-1.5.x, emerge apache, and then reemerging
libtool-2.2.x

But then, I don't know whether the mod_authn_file still works or not. Will
test.

Roby, how did you applied patch? You have to incorporate it into apache
patchset to make build system handle it correctly...

The patch works for me as well.

The patch works for me too, ~amd64, 
sys-devel/libtool-2.2.4
www-servers/apache-2.2.8-r2

patch works for me too.

amd64
www-servers/apache-2.2.8-r2
sys-devel/libtool-2.2.4

Upstream has accepted my patch.

How can I apply the patch to the apache patch set? Isn't an ordinary epatch
statement enough?

If even upstream accepted this patch, why didn't it hit the tree during recent
revbump ?

(In reply to comment #10)
> If even upstream accepted this patch, why didn't it hit the tree during recent
> revbump ?
> 

because it was just a security revbump

Well, this patch doesn't break anything for libtool 1.5 and fixes a problem
with libtool 2 AND got accepted by upstream.
And don't forget that it's the latest in tree so it will affect ~arch the
moment
libtool 2 gets unmasked again.
And as a sidenote:
it seems that substitute useflag is missing a description, at least it did when
I syncd about 2 hours ago.

Sorry, my mistake - substitute is not a useflag.

fixed in 2.2.8-r4