Platform is SUSE Enterprise 10 SP2. Bootstrapping fails in the `emerge -e system' step, at package 68 of 138, which is perl-core/Module-Build-0.36.07. The console has ... Installing /local/scratch/portage/perl-core/Module-Build-0.36.07/image/local/tmp/d/usr/share/man/man3/Module::Build::Authoring.3pm Installing /local/scratch/portage/perl-core/Module-Build-0.36.07/image/local/tmp/d/usr/share/man/man3/Module::Build::Compat.3pm Installing /local/scratch/portage/perl-core/Module-Build-0.36.07/image/local/tmp/d/usr/bin/config_data >>> Completed installing Module-Build-0.36.07 into /local/scratch/portage/perl-core/Module-Build-0.36.07/image/local/tmp/d/ ecompressdir: bzip2 -9 /local/tmp/d/usr/share/man * QA Notice: the following files use invalid (possible non-prefixed) shebangs: * local/tmp/d/usr/bin/config_data-0.36.07-Module-Build-0.36.07:/local/scratch/nightly/2010-10-27/usr/bin/perl5.12.1 (in PATH but target not found) * ERROR: perl-core/Module-Build-0.36.07 failed: * Aborting due to QA concerns: invalid shebangs found The pathname that appears in the QA Notice actually exists in the filesystem: > file /local/scratch/nightly/2010-10-27/usr/bin/perl5.12.1 /local/scratch/nightly/2010-10-27/usr/bin/perl5.12.1: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, stripped
what is the bootstrap portage you have at the moment it fails?
what is your EPREFIX and ROOT set to?
The `USE=-git emerge -u system' step pulls in portage version 2.2.01.17133, so that is the version that should be in effect. Not sure what you mean by ROOT? The value of EPREFIX is /local/tmp/j, where /local/tmp is a symlink pointing to /local/scratch (which is a true directory), and /local/scratch/j is a symlink to /local/scratch/nightly/2010-11-01 (directories all the way).
Created attachment 252809 [details, diff] shebang-check.patch ok, then I see where this goes wrong. Can you please try attached patch to see if that fixes the issue sufficiently for you?
I'm under the understanding that EPREFIX as a symlink does not work with the toolchain (tried it, failed badly), should supporting it even be attempted?
well, if it is as easy to fix, as this is, then I see no reason why not to attempt to
Good news, the patch fixes the problem and bootstrapping succeeds all the way again.
ok, fixing then