Summary: | app-admin/apache-tools installs libtool temporary files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ryan Voots <simcop2387> |
Component: | [OLD] Unspecified | Assignee: | Patrick Lauer <patrick> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | mail, patrick |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log captured with /usr/bin/script
emerge info sample script that was installed resulting config.log from build environment from /var/db/pkg |
Description
Ryan Voots
2010-04-20 07:18:57 UTC
Created attachment 228481 [details]
Build log captured with /usr/bin/script
Created attachment 228483 [details]
emerge info
Created attachment 228485 [details]
sample script that was installed
First of all, your CFLAGS are "funny", but that's probably a different matter. Did you try to reemerge libtool/apr/apr-util ? 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". trying the other version of apache-tools in portage also seems to have no effect. About your 'emerge --info': why is the timestamp so old ? Could you also attach config.log from the emerge ? Created attachment 228551 [details]
resulting config.log from build
Here's the config.log
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 What exactly is that /usr/bin/script thing ? Could you try to emerge without it ? 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. (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/. Created attachment 228621 [details]
environment from /var/db/pkg
please re-open if there's still a problem with 2.4.7 |