Skip Menu |
Queue is disabled
This queue is disabled and you may not create new tickets in it.
Report information
Id: 4242
Status: resolved
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors: hmbrand <h.m.brand [at] xs4all.nl>
Cc:
AdminCc:

Operating System: HPUX
PatchStatus: (no value)
Severity: none
Type: (no value)
Perl Version: 5.7.0
Fixed In: (no value)



Date: Mon, 04 Sep 2000 19:44:03 +0200
From: H.Merijn Brand <h.m.brand [...] hccnet.nl>
To: perlbug [...] perl.org
Subject: OK: perl v5.7.0 on PA-RISC2.0 11.00 (INSTALLED)
Download (untitled) / with headers
text/plain 2.9k
This is a success report for perl from h.m.brand@hccnet.nl, generated with the help of perlbug 1.32 running under perl v5.7.0. Perl reported to build OK on this system. Where has the report for the latest aplied patch gone? I really liked that info in patchlevel.h. Should we put it back there? somehow ... This one is up to and including 7016. --- Flags: category=install severity=none --- Site configuration information for perl v5.7.0: Configured by merijn at Mon Sep 4 19:19:29 METDST 2000. Summary of my perl5 (revision 5.0 version 7 subversion 0) configuration: Platform: osname=hpux, osvers=11.00, archname=PA-RISC2.0 uname='hp-ux l1 b.11.00 u 9000800 527706567 unlimited-user license ' config_args='-ds' hint=recommended, useposix=true, d_sigaction=define usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef useperlio=undef d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef Compiler: cc='cc', ccflags =' -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ', optimize='+O2 +Onolimit', cppflags='-DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include' ccversion='A.11.01.21505.GP', gccversion='', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, usemymalloc=y, prototype=define Linker and Libraries: ld='ld', ldflags ='-L/pro/local/lib -Wl,+vnocompatwarnings' libpth=/pro/local/lib /lib /usr/lib /usr/ccs/lib /usr/local/lib libs=-lnsl -lnm -lndbm -lgdbm -ldb -ldld -lm -lc -lndir -lcrypt -lsec libc=/lib/libc.sl, so=sl, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_hpux.xs, dlext=sl, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-B,deferred ' cccdlflags='+z', lddlflags='-b +vnocompatwarnings -L/pro/local/lib' Locally applied patches: --- @INC for perl v5.7.0: lib /pro/lib/perl5/5.7.0/PA-RISC2.0 /pro/lib/perl5/5.7.0 /pro/lib/perl5/site_perl/5.7.0/PA-RISC2.0 /pro/lib/perl5/site_perl/5.7.0 /pro/lib/perl5/site_perl/5.005/PA-RISC2.0 /pro/lib/perl5/site_perl/5.005 /pro/lib/perl5/site_perl . --- Environment for perl v5.7.0: HOME=/u/usr/merijn LANG=C LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=.:/u/usr/merijn/bin/private:/u/usr/merijn/bin:/pro/local/bin:/pro/bin:/usr/hosts:/usr/bin:/usr/dt/bin:/usr/bin/X11:/opt/ansic/bin:/usr/sbin:/etc:/sbin:/usr/lib:/usr/ccs/bin:/usr/contrib/bin:/opt/nettladm/bin:/opt/fc/bin:/opt/fcms/bin:/opt/upgrade/bin:/opt/pd/bin:/usr/contrib/bin/X11:/opt/java/bin:/opt/hparray/bin:/opt/resmon/bin:/opt/pred/bin:/opt/langtools/bin:/opt/perf/bin:/opt/imake/bin:/opt/hpnp/bin:/pro/tu/bin PERL_BADLANG (unset) SHELL=/bin/sh SHLIB_PATH (unset)
Date: Mon, 4 Sep 2000 21:41:57 -0500
From: Jarkko Hietaniemi <jhi [...] iki.fi>
To: "H.Merijn Brand" <h.m.brand [...] hccnet.nl>
Cc: perl5-porters [...] perl.org
Subject: Re: [ID 20000904.006] OK: perl v5.7.0 on PA-RISC2.0 11.00 (INSTALLED)
Download (untitled) / with headers
text/plain 789b
On Mon, Sep 04, 2000 at 07:44:03PM +0200, H.Merijn Brand wrote: Show quoted text
> This is a success report for perl from h.m.brand@hccnet.nl, > generated with the help of perlbug 1.32 running under perl v5.7.0. > > Perl reported to build OK on this system. > > Where has the report for the latest aplied patch gone? > I really liked that info in patchlevel.h.
When I released the 5.7.0, I took that label latest applied patch info out. Show quoted text
> Should we put it back there? somehow ...
It's easy to put back. But the problem is that the patchlevel.h has to be explicitly updated, I did that when released my snapshots. I would prefer a more integrated thing, something in perforce that would automatically bump the release level whenever a change is checked in. Show quoted text
> This one is up to and including 7016.
report is back in


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org