Re: Smoke 18378 aix 4.3.1.0 cc_r 5.0.2.0 (8 cpus)
I'm going to have to disable my single AIX smoke since it just keeps failing in Configure and I have no time to debug it now for a few weeks at least. This is the very frustrating failure I get: Could not load program ./try: Dependent module libc.a(shr.o) could not be loaded. Could not load module libc.a(shr.o). Error was: No such file or directory Unable to configure perl in this configuration The cool thing? If I add the option -x to this exec... ... + echo (Feeding myself to /usr/bin/bsh to avoid AIX 4's /bin/sh.) + exec /usr/bin/bsh ./Configure -Dusedevel -Duse64bitint -des to trace what's going on, the whole following Configure run *FREEZES* AND *KILLS* the underlying shell, not in the same spot, but in some random spot. (I'm thankful to be using the screen utility so that I can always kill a hang up shell...) My interactive shell under which I was running the Configure really seems to go bye-bye, according to ps. All in all, too cool for me to debug now. (Smells like a broken /bin/bsh, but I simply don't have the time to play with it now.) The final insult to the injury is that *with* threads Configure finishes just fine, it's the non-threads, and use64bitint builds that hang as described above. -- Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
Re: Smoke 18378 aix 4.3.1.0 cc_r 5.0.2.0 (8 cpus)
On Mon 06 Jan 2003 16:12, Jarkko Hietaniemi [EMAIL PROTECTED] wrote: I'm going to have to disable my single AIX smoke since it just keeps failing in Configure and I have no time to debug it now for a few weeks at least. This is the very frustrating failure I get: Could not load program ./try: Dependent module libc.a(shr.o) could not be loaded. Could not load module libc.a(shr.o). Error was: No such file or directory Unable to configure perl in this configuration The cool thing? If I add the option -x to this exec... Maybe Test::Smoke is the module that has yielded the most end-user frustration after all :) [ well, except for DBD::Oracle maybe, which mostly indicates that the pooor user /has to/ work with Oracle ] ... + echo (Feeding myself to /usr/bin/bsh to avoid AIX 4's /bin/sh.) + exec /usr/bin/bsh ./Configure -Dusedevel -Duse64bitint -des to trace what's going on, the whole following Configure run *FREEZES* AND *KILLS* the underlying shell, not in the same spot, but in some random spot. (I'm thankful to be using the screen utility so that I can always kill a hang up shell...) My interactive shell under which I was running the Configure really seems to go bye-bye, according to ps. All in all, too cool for me to debug now. (Smells like a broken /bin/bsh, but I simply don't have the time to play with it now.) The final insult to the injury is that *with* threads Configure finishes just fine, it's the non-threads, and use64bitint builds that hang as described above. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0 633 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Smoke 18378 aix 4.3.1.0 cc_r 5.0.2.0 (8 cpus)
On Wed 01 Jan 2003 20:09, Jarkko Hietaniemi [EMAIL PROTECTED] wrote: c c c c c c c c -Duse64bitint F F F F -Dusethreads | | | +- PERLIO = perlio -DDEBUGGING | | +--- PERLIO = stdio -DDEBUGGING | +- PERLIO = perlio +--- PERLIO = stdio Need help? The MANIFEST messages however show a possible runover. You mean the .nfs files? Nah, that's standard with these NFS servers. Many 'c' errors (or the reason(s) therefor) can be found in mktest.log I would appreciate ideas of what's going wrong, I'm currently trying to run Configure with 'sh -x' to get more ideas. Once I've got the output from that, I'll share it with you. The cc is relatively old, but please don't ask upgrading, this box is basically just running till it dies, no maintenance or anything. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0 633 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Smoke 18378 aix 4.3.1.0 cc_r 5.0.2.0 (8 cpus)
On Wed 01 Jan 2003 10:08, Jarkko Hietaniemi [EMAIL PROTECTED] wrote: Automated smoke report for patch 18378 on aix - 4.3.1.0 (aix-thread-multi) v1.16 using cc_r version 5.0.2.0 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep 18378 Configuration (common) none --- -- c c c c c c c c -Duse64bitint F F F F -Dusethreads | | | +- PERLIO = perlio -DDEBUGGING | | +--- PERLIO = stdio -DDEBUGGING | +- PERLIO = perlio +--- PERLIO = stdio Need help? The MANIFEST messages however show a possible runover. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0 633 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Smoke 18378 aix 4.3.1.0 cc_r 5.0.2.0 (8 cpus)
c c c c c c c c -Duse64bitint F F F F -Dusethreads | | | +- PERLIO = perlio -DDEBUGGING | | +--- PERLIO = stdio -DDEBUGGING | +- PERLIO = perlio +--- PERLIO = stdio Need help? The MANIFEST messages however show a possible runover. You mean the .nfs files? Nah, that's standard with these NFS servers. I would appreciate ideas of what's going wrong, I'm currently trying to run Configure with 'sh -x' to get more ideas. Once I've got the output from that, I'll share it with you. The cc is relatively old, but please don't ask upgrading, this box is basically just running till it dies, no maintenance or anything. -- Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
