Automated smoke report for patch 15951 on solaris - 2.8
v1.12 using gcc version 2.95.2 19991024 (release)
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
Configuration
------- --------------------------------------------------------------------
O O O O -Duseperlio
O O O O -Duseperlio -Duse64bitint
O O O O -Duseperlio -Duselongdouble
O O O O -Duseperlio -Dusemorebits
F F F F -Uuseperlio
| | | +- PERLIO = perlio -DDEBUGGING
| | +--- PERLIO = stdio -DDEBUGGING
| +----- PERLIO = perlio
+------- PERLIO = stdio
Failures:
solaris stdio/perlio -Uuseperlio
solaris stdio/perlio -DDEBUGGING -Uuseperlio
t/japh/abigail......................FAILED at test 129
.../t/japh/abigail....FAILED test 129
Just like Merijn, now I'm getting failures here as well (but not on Linux).
The program doesn't generate any output. However, if we add a newline
as second argument to the print, it does print "Just another Perl Hacker"
(with newlines after each character).
The problem is demonstrated by the following small program:
#!/usr/bin/perl -w
print "a";
exec $0;
With -Uuseperlio, this doesn't generate any output on Solaris.
On Linux, or when build with -Duseperlio, it generates an infinite
list of 'a's.
Now, this might be related to the remark in perlport.pod:
=item exec LIST;
Does not automatically flush output handles on some platforms.
(SunOS, Solaris, HP-UX)
But if that's true, why does it work when using perlio, even if you
say PERLIO=stdio?
Abigail
