| Summary: | sys-libs/pam-1.1.0 - ./config.status[2359]: shift: nothing to shift | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | oriol.morell <oriol.morell> |
| Component: | [OLD] Core system | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
This is the config.log
Please find the "emerge --info" in the file attached called typescript Pam failed again Please find the config.log from emerge pam Please find now the build.log of pam Please, find attahced the config.status |
||
Created attachment 204841 [details]
This is the config.log
Please choose "Gentoo Linux" as Product and not "Bugzilla"... Furthermore please add the output of "emerge --info" to this bug. Created attachment 204887 [details]
Please find the "emerge --info" in the file attached called typescript
Excuse me, but I could not choose "Gentoo Linux" as Product and not "Bugzilla"; probably my fault.
Your emerge --info lists two versions of libtool, one of which is _not_ in portage. Please fix your system. Created attachment 205199 [details]
Pam failed again
Ok, libtool is fixed now. Many thanks. Next, we have run revdep-rebuild. Then we did: emerge -vuNDt pam, and the same situation appears.
Please find in the attachment the following outputs: 1) emerge --info ; 2) emerge -vpuNDt pam; and e) emerge -vuNDt pam.
Created attachment 205200 [details]
Please find the config.log from emerge pam
Created attachment 205201 [details]
Please find now the build.log of pam
It looks like the situation persists, even if the emerge is fixed. Please attach the config.status file from the failed build -- it should provide more clues on what is going wrong. Created attachment 205749 [details]
Please, find attahced the config.status
The file attached is: /var/tmp/portage/sys-libs/pam-1.1.0/work/Linux-PAM-1.1.0/config.status
Please, let us know what we could try to probe/check/study to get along with this bug. Many thanks. If we try to use the ebuild /usr/portage/sys-libs/pam/disable-prelude directly it does not compiled. But, if we comment two lines of the ebuild, then it compiles:
127 econf \
128 --libdir=/usr/$(get_libdir) \
129 --docdir=/usr/share/doc/${PF} \
130 --htmldir=/usr/share/doc/${PF}/html \
131 --enable-securedir=/$(get_libdir)/security \
132 --enable-isadir=/$(get_libdir)/security \
133 $(use_enable nls) \
134 $(use_enable selinux) \
135 $(use_enable cracklib) \
136 $(use_enable audit) \
137 $(use_enable debug) \
138 --disable-db \
139 # --disable-dependency-tracking \
140 # --disable-prelude \
141 ${myconf} || die "econf failed"
142 emake sepermitlockdir="/var/run/sepermit" || die "emake failed"
Is it a proper solution to comment "--disable-dependency-tracking \" and
"--disable-prelude \" ?? thanks.
So, removing "--disable-dependency-tracking" from the ebuild, pam gets installed. Is "--disable-dependency-tracking" important? disable-dependency-tracking looks like is just to speed compile time, doesn't it¿? Solved: ~ # cd /bin bin # ls -la /bin/sh lrwxrwxrwx 1 root root 3 May 24 10:04 /bin/sh -> ksh bin # mv /bin/sh /root/bin-sh bin # ln -s bash sh ; ls -la sh lrwxrwxrwx 1 root root 4 Jun 11 09:27 sh -> bash |
config.status: executing depfiles commands ./config.status[2359]: shift: nothing to shift !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-libs/pam-1.1.0/work/Linux-PAM-1.1.0/config.log * * ERROR: sys-libs/pam-1.1.0 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3173: Called econf '--libdir=/usr/lib' '--docdir=/usr/share/doc/pam-1.1.0' '--htmldir=/usr/share/doc/pam-1.1.0/html' '--enable-securedir=/lib/security' '--enable-isadir=/lib/security' '--enable-nls' '--disable-selinux' '--enable-cracklib' '--disable-audit' '--disable-debug' '--disable-db' '--disable-dependency-tracking' '--disable-prelude' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/pam-1.1.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/pam-1.1.0/temp/environment'. * >>> Failed to emerge sys-libs/pam-1.1.0, Log file: