Bug 316291 – app-admin/apache-tools installs libtool temporary files

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Ryan Voots 2010-04-20 07:18:57 UTC]

When building app-admin/apache-tools-2.2.15 with libtool-2.2.6b i'm getting nothing but wrapper scripts from libtool installed into /usr/sbin/.

i'm attaching a build log, emerge --info, and a sample wrapper script.

Reproducible: Always

Steps to Reproduce:
1. emerge app-admin/apache
Actual Results:  
Got broken temporary libtool wrapper scripts installed into /usr/sbin/

Expected Results:  
Some kind of useful runnable file.

[Comment 1 Ryan Voots 2010-04-20 07:20:05 UTC]

Created attachment 228481 [details]
Build log captured with /usr/bin/script

[Comment 2 Ryan Voots 2010-04-20 07:21:00 UTC]

Created attachment 228483 [details]
emerge info

[Comment 3 Ryan Voots 2010-04-20 07:21:42 UTC]

Created attachment 228485 [details]
sample script that was installed

[Comment 4 Rafał Mużyło 2010-04-20 11:46:25 UTC]

First of all, your CFLAGS are "funny", but that's probably a different matter.

Did you try to reemerge libtool/apr/apr-util ?

[Comment 5 Ryan Voots 2010-04-20 18:02:51 UTC]

Rebuilding those three had no effect on the files in /usr/sbin/ from apache-utils.  it still builds and installs the temporarily scripts from libtool.  I also cleaned up the cflags (been meaning to do that for years, they're left over from extremely old gcc versions from years ago.  now its just; CFLAGS="-march=native -O2 -ftree-vectorize -pipe -ggdb".

[Comment 6 Ryan Voots 2010-04-20 19:03:44 UTC]

trying the other version of apache-tools in portage also seems to have no effect.

[Comment 7 Rafał Mużyło 2010-04-20 19:30:10 UTC]

About your 'emerge --info': why is the timestamp so old ?

Could you also attach config.log from the emerge ?

[Comment 8 Ryan Voots 2010-04-20 20:37:14 UTC]

Created attachment 228551 [details]
resulting config.log from build

Here's the config.log

[Comment 9 Ryan Voots 2010-04-20 21:05:57 UTC]

I didn't realize it had been nearly a month since i had updated my tree, but even after updating it (and upgrading apr, it was the only thing with anything new) i still get this result

[Comment 10 Rafał Mużyło 2010-04-20 22:09:26 UTC]

What exactly is that /usr/bin/script thing ?

Could you try to emerge without it ?

[Comment 11 Ryan Voots 2010-04-20 22:30:12 UTC]

all script is is a command to capture the output of the terminal, i used that for making the build log.  this happens when using it and without using it.

[Comment 12 Rafał Mużyło 2010-04-21 12:16:14 UTC]

(In reply to comment #11)
> all script is is a command to capture the output of the terminal, i used that
> for making the build log.  this happens when using it and without using it.
> 
Portage logs it anyway.

On the off chance that 'emerge --info' was not enough here,
could you attach environment from the emerge ?
You can get it from /var/db/pkg/.

[Comment 13 Ryan Voots 2010-04-21 12:36:40 UTC]

Created attachment 228621 [details]
environment from /var/db/pkg

[Comment 14 SpanKY 2014-01-31 08:25:40 UTC]

please re-open if there's still a problem with 2.4.7