RE: BerkeleyDB make test problem

[Paul Marquess]

From: Ken Williams [mailto:[EMAIL PROTECTED]

 
 On Thursday, August 21, 2003, at 05:38  AM, Paul Marquess wrote:
 
  I've had a mail from someone using my BerkeleyDB module on OSX. When 
  he does
  the usual make test step it seems to be running the BerkeleyDB.pm 
  file
  that is installed, rather than the one under blib.
 
  I have no first hand experience with OSX - Is this a known issue?
 
 
 Nope, generally 'make test' works fine and tests the module from blib/. 
   Must be something peculiar to either BerkeleyDB or his box.

Thanks Ken

Paul

Re: BerkeleyDB make test problem

[Andrew Brosnan]

 
 On Thursday, August 21, 2003, at 05:38  AM, Paul Marquess wrote:
 
  I've had a mail from someone using my BerkeleyDB module on OSX.
  When he does the usual make test step it seems to be running the
  BerkeleyDB.pm file that is installed, rather than the one under
  blib.
 

I wonder if they have the latest 'Developer Tools' installed?

shrug

Re: Crash reading $|

[Rafael Garcia-Suarez]

Mark Alldritt wrote in perl.macosx :
 
 I'm seeing a crash reading $| in the following code snippet:
 
 local *STDOUT; 
 
 my $copy = $|; # -- crashes here

This bug will be fixed in 5.9.0 and eventually in 5.8.1 if it's picked
up for the next release candidate.

 I'm reading $| in some code that does not know if local *STDOUT has happened
 or not.  Can anyone think of a way to work around this?

Test for fileno(STDOUT) to see whether it's been undefined.
On my linux :

$ cat x 
#!perl -l
print STDERR -,fileno(STDOUT),-;
local *STDOUT;
print STDERR -,fileno(STDOUT),-;

$ perl x 
-1-
--

HTH.

-- 
Ulcers is not *NIX