; \
else \
make TEST_ARGS= TESTFILE=TEST _test_notty ; \
fi
make[1]: Entering directory `/opt/blead/perl'
cd t TEST /dev/tty
/bin/sh: TEST: command not found
make[1]: *** [_test_tty] Error 127
make[1]: Leaving directory `/opt/blead/perl'
make: *** [_test] Error 2
--
Rafael Garcia-Suarez
Michael G Schwern [EMAIL PROTECTED] wrote:
perl5-smokers?
A small group of dangerous hippies, addicted to strange drugs.
Usually suffer from lack of sleep. Known to mumble incoherent
acronyms (such as SvNIOKp or SvPVutf8x) all the time.
Nicholas Clark [EMAIL PROTECTED] wrote:
On Thu, Jan 30, 2003 at 01:18:41PM +0100, H.Merijn Brand wrote:
On Thu 30 Jan 2003 12:43, alian [EMAIL PROTECTED] wrote:
make: *** Pas de règle pour fabriquer la cible `interne', nécessaire
pour `miniperlmain.o'. Arrêt.
AHHr
Mike Stok wrote in perl.daily-build :
Would it be useful to run daily builds using Test-Smoke-1.16_30 on a Red
Hat 8 installation running under UML?
What's UML ?
(regarding the version of Test-Smoke : it's better to upgrade as new
versions are released, since the default config for testing
Nicholas Clark wrote in perl.daily-build :
usemymalloc is probably useful on FreeBSD
I'm not sure what else is - many of the other configure flags are somewhat
esoteric.
Possibly either trying with/without bincompat5005 might be interesting,
or doing threads builds with/without multiplicity
The recent smoke failures noticed by Merijn are reproducible with
the environment variables
PERL_UNICODE=
LC_ALL=fr_FR.utf8 (or another utf8 locale)
perlrun states clearly that PERL_UNICODE being unset is not equivalent
to PERL_UNICODE=, but to PERL_UNICODE=0. I don't know how
Test::Smoke
Abe Timmerman wrote in perl.daily-build :
The recent smoke failures noticed by Merijn are reproducible with
the environment variables
PERL_UNICODE=
LC_ALL=fr_FR.utf8 (or another utf8 locale)
perlrun states clearly that PERL_UNICODE being unset is not equivalent
to PERL_UNICODE=, but
Selon Jarkko Hietaniemi [EMAIL PROTECTED]:
where/how are the builds with gcc failing on dec_osf ?
Thanks,
Adi
mktest.out:
Configuration: -Dusedevel -Dlocincpth=/p/include -Dloclibpth=/p/lib
-Dcc=gcc
--
On 23/09/2007, Abe Timmerman [EMAIL PROTECTED] wrote:
It turns out this is due to non-existent directories in $PATH.
I tried the following patch to t/test.pl:runperl()
Thanks, applied as #31962.
On 2002.03.10 04:54 Michael G Schwern wrote:
This one is new: lstat() appears to be emitting some extra warnings.
I wrote the test (in t/lib/warnings/pp_sys). From your attached log :
# pp_sys.c [pp_lstat]
use warnings 'io';
lstat STDIN;
open my $fh, $0 or die # $!;
lstat $fh;
no warnings
Automated smoke report for patch 17411 on linux - 2.2.14-5.0
v1.13 using /opt/gcc31/bin/gcc31 version 3.1
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 =
Abe Timmerman wrote:
Automated smoke report for patch 18027 on MSWin32 - 5.0 Win2000Pro
run/switches...FAILED test 7
I'm responsible for this one.
Can I see the output of run/switches.t ?
Maybe the hex-encoded output of
perl -066 'BEGIN { print ($/) }
H.Merijn Brand [EMAIL PROTECTED] wrote:
-1 not allowed?
Dunno, I was thinking that signal numbers must be (logically)
positive numbers.
So I introduced this test in Config.t (change 18891) to help tracking
a problem on Linux/Gentoo.
But now I see that :
$ uname -a
HP-UX galhp B.10.20 E
Enache Adrian wrote:
On Mon, Mar 24, 2003 at 09:31:42PM +, Nicholas Clark wrote:
The improved libperl.so patch doesn't do nice things to the regular Linux
build:
LD_PRELOAD=$LD_PRELOAD /home/nick/19055/libperl.a ./miniperl -Ilib configpm
configpm.tmp
./miniperl: error while
Enache Adrian wrote:
On Mon, Mar 24, 2003 at 11:18:43PM +0100, Rafael Garcia-Suarez wrote:
Thanks, applied as #19056.
(In fact I was going to apply my own version, less clean, of your patch.)
Aarrgh!
Too late to repent, I already applied this :
(which should be equivalent)
Change 19059
Tels wrote:
I had the same problem on Debian an x86 with 20002, 20006 and 20008
when running 'make test'. I ran the test with 'harness' hundred times
but it always succeeded. Strange. I increased my stacksize to 64M, no
change.
Note that make test runs t/TEST, while make test_harness runs
Jarkko Hietaniemi wrote:
Hmmm, I dunno. In general I would say tests should not produce extra
output unless they mean to fail. Or in other words, the test
harnesses should not be too forgiving. Or they may output using
some known out of band channel, like lines matching ^/#/.
I agree here
H.Merijn Brand wrote:
HP-UX 11.00
You are now on patchlevel 20169
l1:/pro/3gl/CPAN/perl-current 107 Conf
Cleaning up ...
Configure -Dusedevel -des
:
:
`sh cflags optimize='+O2 +Onolimit' pp_sys.o` pp_sys.c
CCCMD = cc -DPERL_CORE -c -Ae -DDEBUGGING -D_HPUX_SOURCE
Johan Vromans wrote:
Johan Vromans [EMAIL PROTECTED] writes:
Automated smoke report for patch 20760 on linux - 2.4.20-2jv.7.x
(i686-linux-thread-multi-ld)
v1.16 using cc version 2.96 2731 (Red Hat Linux 7.2
2.96-112.7.2)
I noticed that 5.8.x builds on my system
Abe Timmerman wrote in perl.daily-build.reports :
Automated smoke report for 5.9.0 patch 21384 on openbsd - 3.3 (sparc64/1 cpu)
../t/comp/require.t.FAILED 10-11
A t/comp test failing, doubleplusungood :-
Those are related to vstrings and floating points.
I'm stuck --
2008/12/19 karl williamson pub...@khwilliamson.com:
Two things: when I do as above using rsync, I merely get a list of the
valid perl sources. If I change the :: to a slash, I actually get the
files. However, .patch contains
blead 20081219.17:05:08 b1fccde5a5d6d9eece3886ce5cb9dc7b9027bee2
2008/12/19 karl williamson pub...@khwilliamson.com:
Craig A. Berry wrote:
On Fri, Dec 19, 2008 at 11:24 AM, Steve Hay steve...@planit.com wrote:
Rafael Garcia-Suarez wrote:
2008/12/19 karl williamson pub...@khwilliamson.com:
Two things: when I do as above using rsync, I merely get a list
2008/12/19 Jerry D. Hedden jdhed...@cpan.org:
On Fri, Dec 19, 2008 at 12:24 PM, Steve Hay steve...@planit.com wrote:
Rafael Garcia-Suarez wrote:
2008/12/19 karl williamson pub...@khwilliamson.com:
Two things: when I do as above using rsync, I merely get a list of
the valid perl sources
On 23/04/06, Steve Peters [EMAIL PROTECTED] wrote:
What's happening above is that TEST cannot handle seeing tests come in
out of order, while harness can. I'm scanning Test::Harness::TAP a bit,
but it seems to be unspecified whether this is OK or not. Should TEST
care if the tests are reported
Abe Timmerman wrote in perl.daily-build.reports :
[stdio/perlio] -Duseithreads -Duse64bitint
../ext/Devel/Peek/t/Peek.t..FAILED 18-19
I suspect that those failures (which I don't reproduce) are caused by
the recent change to dump.c regarding pv_escape function
(change 28490).
On 22/07/06, Jerry D. Hedden [EMAIL PROTECTED] wrote:
All of the above stem from using the SvREFCNT_inc() macro in a void
context. Would adding (void) in front of these suppress these
warnings? Should I submit a patch for that?
You could use SvREFCNT_inc_void or one of its variants (see
H.Merijn Brand wrote in perl.daily-build.reports :
29220 Configuration (common) none
--- -
O O O O O F
O O O O O F -Duse64bitint
O O O O O F -Duselongdouble
O O O O O F -Dusemorebits
Do those failures mean that Dave's
On 07/11/06, Steve Peters [EMAIL PROTECTED] wrote:
On Tue, Nov 07, 2006 at 05:18:31PM -, Rafael Garcia-Suarez wrote:
H.Merijn Brand wrote in perl.daily-build.reports :
29220 Configuration (common) none
--- -
O O O
On Thu, 15 Mar 2007 08:44 -0500, [EMAIL PROTECTED]
shared.xs:381:13: warning: no newline at end of file
shared.xs: In function `Perl_sharedsv_find':
shared.xs:381: error: `swit' undeclared (first use in this function)
Bad sync ? line 381 is :
switch(SvTYPE(sv)) {
looks like the ch was
29 matches
Mail list logo
