[16953] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 4365 Volume: 9

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Sep 18 18:20:51 2000

Date: Mon, 18 Sep 2000 15:20:28 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <969315627-v9-i4365@ruby.oce.orst.edu>
Content-Type: text

Perl-Users Digest           Mon, 18 Sep 2000     Volume: 9 Number: 4365

Today's topics:
        Regular Expressions: Counting matches? <johndoyle33@hotmail.com>
    Re: Regular Expressions: Counting matches? <johndoyle33@hotmail.com>
    Re: Regular Expressions: Counting matches? <kmetcalf@lighthousemarketing.com>
    Re: Regular Expressions: Counting matches? <ren.maddox@tivoli.com>
    Re: Regular Expressions: Counting matches? <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
    Re: Regular Expressions: Counting matches? <ren.maddox@tivoli.com>
    Re: Regular Expressions: Counting matches? <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
    Re: Regular Expressions: Counting matches? <sariq@texas.net>
    Re: Regular Expressions: Counting matches? <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
    Re: single line regex and multi-line regex without rese <ren.maddox@tivoli.com>
    Re: Strange characters when using forms ^M <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
    Re: Substring Golf? <ren.maddox@tivoli.com>
        syslog problem <tambaax@yahoo.com>
    Re: Teaching Perl <bart.lateur@skynet.be>
    Re: Teaching Perl (brian d foy)
    Re: tutorial for advanced experimental regex  features? (William C. Ray)
    Re: tutorial for advanced experimental regex  features? <ren.maddox@tivoli.com>
    Re: Two questions: 1)Erasing temporary files 2)post met nobull@mail.com
        Upgrade Error: ld.so.1: perl: fatal: libdb-3.1.so: open bluearchtop@my-deja.com
        Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Mon, 18 Sep 2000 18:52:02 GMT
From: Chovy <johndoyle33@hotmail.com>
Subject: Regular Expressions: Counting matches?
Message-Id: <8q5o87$3o2$1@nnrp1.deja.com>

Hello,

I want to find out how many times a word is matched in a string a text.
Basically, I want to count the number of links on a page...
ie-

---
m/<a href=/ig
---

how do I find out how many times it's been matched?

Please help!

Thanks,

--
Thanks,
Chovy
johndoyle33@hotmail.com


Sent via Deja.com http://www.deja.com/
Before you buy.


------------------------------

Date: Mon, 18 Sep 2000 19:29:11 GMT
From: Chovy <johndoyle33@hotmail.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <8q5qd9$6e9$1@nnrp1.deja.com>

In article <8q5o87$3o2$1@nnrp1.deja.com>,
  Chovy <johndoyle33@hotmail.com> wrote:
> Hello,
>
> I want to find out how many times a word is matched in a string a
text.
> Basically, I want to count the number of links on a page...
> ie-
>
> ---
> m/<a href=/ig
> ---
>
> how do I find out how many times it's been matched?
>
> Please help!
>
> Thanks,
>
> --
> Thanks,
> Chovy
> johndoyle33@hotmail.com
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Well, I came up with this, but not sure if there is a built-in function
in perl for the same task.

$count = 0;
for ($html =~ m/<a href="(.*?)"/g) {
  $count++;
  print "matched $_\n";
}


print "# of links:$count\n";


------

If there is a better way to count the number of times something appears,
 using RegEx, please let me know!


--
Thanks,
Chovy
johndoyle33@hotmail.com


Sent via Deja.com http://www.deja.com/
Before you buy.


------------------------------

Date: 18 Sep 2000 19:54:13 GMT
From: kevin metcalf <kmetcalf@lighthousemarketing.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <39C67341.DE69CBA0@lighthouseNOTmarketingNOT.com>

According to the perl bible (wall, christiansen, schwartz) you would use:
$nummatches = tr/<a href=/<a href=/ig;

or some such similar thing.

Kevin

Chovy wrote:

> Hello,
>
> I want to find out how many times a word is matched in a string a text.
> Basically, I want to count the number of links on a page...
> ie-
>
> ---
> m/<a href=/ig
> ---
>
> how do I find out how many times it's been matched?
>
> Please help!
>
> Thanks,
>
> --
> Thanks,
> Chovy
> johndoyle33@hotmail.com
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.



------------------------------

Date: 18 Sep 2000 14:33:19 -0500
From: Ren Maddox <ren.maddox@tivoli.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <m3itrtwl4w.fsf@dhcp11-177.support.tivoli.com>

Chovy <johndoyle33@hotmail.com> writes:

> Hello,
> 
> I want to find out how many times a word is matched in a string a text.
> Basically, I want to count the number of links on a page...
> ie-
> 
> ---
> m/<a href=/ig
> ---
> 
> how do I find out how many times it's been matched?

As it happens, that construct in a list context will return all of the
matches.  Take that result and put it in a scalar context and you get
the number of matches.  Try:

scalar(()=/<a href=/ig)

-- 
Ren Maddox
ren@tivoli.com


------------------------------

Date: 18 Sep 2000 20:22:32 GMT
From: kevin metcalf <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <39C679E5.63CBECF7@lighthouseNOTmarketingNOT.com>

kevin metcalf wrote:

> According to the perl bible (wall, christiansen, schwartz) you would use:
> $nummatches = tr/<a href=/<a href=/ig;
>
> or some such similar thing.
>
> Kevin
>
> Chovy wrote:
>
> > Hello,
> >
> > I want to find out how many times a word is matched in a string a text.
> > Basically, I want to count the number of links on a page...
> > ie-
> >
> > ---
> > m/<a href=/ig
> > ---
> >
> > how do I find out how many times it's been matched?
> >
> > Please help!
> >
> > Thanks,
> >
> > --
> > Thanks,
> > Chovy
> > johndoyle33@hotmail.com
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.

Or perhaps I should have escaped some characters?  ;)  Come on, gotta make
homework a <i>little</i> bit easier, no?



------------------------------

Date: 18 Sep 2000 15:29:15 -0500
From: Ren Maddox <ren.maddox@tivoli.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <m3g0mxwijo.fsf@dhcp11-177.support.tivoli.com>

kevin metcalf <kmetcalf@lighthousemarketing.com> writes:

> According to the perl bible (wall, christiansen, schwartz) you would use:
> $nummatches = tr/<a href=/<a href=/ig;

You've confused tr/// with s///.  tr/// works on single characters
(and doesn't have an i or g modifier).  s/// works like you've given,
but doesn't count occurrences per se.

-- 
Ren Maddox
ren@tivoli.com


------------------------------

Date: 18 Sep 2000 21:00:13 GMT
From: kevin metcalf <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <39C682BA.F004A689@lighthouseNOTmarketingNOT.com>

Ren Maddox wrote:

> kevin metcalf <kmetcalf@lighthousemarketing.com> writes:
>
> > According to the perl bible (wall, christiansen, schwartz) you would use:
> > $nummatches = tr/<a href=/<a href=/ig;
>
> You've confused tr/// with s///.  tr/// works on single characters
> (and doesn't have an i or g modifier).  s/// works like you've given,
> but doesn't count occurrences per se.

I know.  Something didn't sit right after that post so I went back to the pb
and found it on page 74-75 of 2nd eddition.  I'll look it up when I get home in
the 3rd edition and see what pages it's on.

Thanks for keeping me honest!  ;)

Kevin



------------------------------

Date: Mon, 18 Sep 2000 16:04:57 -0500
From: Tom Briles <sariq@texas.net>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <39C68379.2A6521AF@texas.net>

kevin metcalf wrote:
> 
> Ren Maddox wrote:
> 
> > kevin metcalf <kmetcalf@lighthousemarketing.com> writes:
> >
> > > According to the perl bible (wall, christiansen, schwartz) you would use:
> > > $nummatches = tr/<a href=/<a href=/ig;
> >
> > You've confused tr/// with s///.  tr/// works on single characters
> > (and doesn't have an i or g modifier).  s/// works like you've given,
> > but doesn't count occurrences per se.
> 
> I know.  Something didn't sit right after that post so I went back to the pb
> and found it on page 74-75 of 2nd eddition.  I'll look it up when I get home in
> the 3rd edition and see what pages it's on.

If you're implying that Programming Perl says 'tr' will do what *you*
said 'tr' will do, you are incorrect.

- Tom


------------------------------

Date: 18 Sep 2000 21:16:25 GMT
From: kevin metcalf <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
Subject: Re: Regular Expressions: Counting matches?
Message-Id: <39C68686.2E33E46D@lighthouseNOTmarketingNOT.com>

Tom Briles wrote:

> kevin metcalf wrote:
> >
> > Ren Maddox wrote:
> >
> > > kevin metcalf <kmetcalf@lighthousemarketing.com> writes:
> > >
> > > > According to the perl bible (wall, christiansen, schwartz) you would use:
> > > > $nummatches = tr/<a href=/<a href=/ig;
> > >
> > > You've confused tr/// with s///.  tr/// works on single characters
> > > (and doesn't have an i or g modifier).  s/// works like you've given,
> > > but doesn't count occurrences per se.
> >
> > I know.  Something didn't sit right after that post so I went back to the pb
> > and found it on page 74-75 of 2nd eddition.  I'll look it up when I get home in
> > the 3rd edition and see what pages it's on.
>
> If you're implying that Programming Perl says 'tr' will do what *you*
> said 'tr' will do, you are incorrect.

I'm sorry.  I thought my "I know..." line made it clear that I was aware of my
error.  I was not intending to use the bible to back up something which was obviously
flawed.  At this point I will exercise extreme self control and not make a horrible
pun that would undoutably result in my banishment from all communities perl world
wide.  ;)  Again, sorry for the misunderstanding, I will avoid cut and past responses
in the future.

Kevin



------------------------------

Date: 18 Sep 2000 14:27:08 -0500
From: Ren Maddox <ren.maddox@tivoli.com>
Subject: Re: single line regex and multi-line regex without resetting $/
Message-Id: <m3og1lwlf7.fsf@dhcp11-177.support.tivoli.com>

[REPOSTING -- looks like I screwed up the original post attempt somehow...]
eric@fruitcom.com (Eric Smith) writes:

> Eric Smith posted
>  > I have text that must be parsed line by line but also multi-line paragraphs
>  > enclosed with the `[' `]' characters.  I can either to the single line
>  > matchine or the multi-line matching, the latter by undef-ing $/;  Problem
>  > is that I cannot get the single line groking to work even with locally
>  > undef-ing the $/ and then redefining it again - once it is undefined, the
>  > whole file is slurped of course.

Don't undef $/, set it to what you need it to be instead.  In this
case, it seems that whenever you find /^\s*\[/, you should set $/ to
"]\n".  This does assume that there is no white space after the "]".
Otherwise, you could just set $/ to "]" and then slurp the newline
afterwards.

#!/usr/local/bin/perl -w
use strict;
while (<>) {
  if (/^\s*\[/) {
    local $/ = "]";
    $_ .= <>;
    $/ = "\n";          # this takes care of trailing whitespace
    $_ .= <>;
    # handle bracketed multi-line string here
    next;
  } 
  # handle non-bracketed lines here
}
__END__

This works on the example text given.  I started with "]\n", but there
is some trailing whitespace, so I switched to what you see above.

[Example text omitted for brevity.]

-- 
Ren Maddox
ren@tivoli.com


------------------------------

Date: 18 Sep 2000 20:16:25 GMT
From: kevin metcalf <NOTkmetcalf@lighthouseNOTmarketingNOT.com>
Subject: Re: Strange characters when using forms ^M
Message-Id: <39C67876.2C3FCD52@lighthouseNOTmarketingNOT.com>




> > > ,when recieving info from a TEXT AREA, I get a couple of ^M

> > The ^M is a control character representation of a return.  When the data
> > is returned, use something like:
> > $value =~ s/%0D//g;
>
> That would remove every occurrence of the three-character string '%0D'.

True, but if this is before you have stripped out the meta characters then
this is EXACTLY what you wanted to do, no?

Kevin
--
To email, untie the nots from my address



------------------------------

Date: 18 Sep 2000 13:59:16 -0500
From: Ren Maddox <ren.maddox@tivoli.com>
Subject: Re: Substring Golf?
Message-Id: <m3hf7dy1a3.fsf@dhcp11-177.support.tivoli.com>

Larry Rosler <lr@hpl.hp.com> writes:

> > my($num=shift)=~y/ //d;($numa,$numb,$numc,$numd)=split/(.{4})/,$num
> > 
> > It's quite short, and reasonably neat...
> 
> It would be much neater if it compiled correctly.

After fixing the syntax error, it would be even neater if it actually
did what it was purported to do:

$ perl -e '(my $num=shift)=~y/ //d;
($numa,$numb,$numc,$numd)=split/(.{4})/,$num;
print "$num=>", join ":", $numa, $numb, $numc, $numd, "\n";' 123456789012345

Gives:
123456789012345=>:1234::5678:

Gotta watch out when you use split and want only the delimiters --
that's not what you get.

Changing the split to: $num=~/(.{0,4})/g  fixes the problem.  You can
leave off the "0," if you don't want to handle having less than four
digits at the end (which, notably, the original substr solution does
handle).

$ perl -e '(my$num=shift)=~y/ //d;
($numa,$numb,$numc,$numd)=$num=~/(.{0,4})/g;
print "$num=>", join ":", $numa, $numb, $numc, $numd, "\n";' 123456789012345

Gives:
123456789012345=>1234:5678:9012:345:

-- 
Ren Maddox
ren@tivoli.com


------------------------------

Date: Mon, 18 Sep 2000 15:28:49 -0500
From: "TH" <tambaax@yahoo.com>
Subject: syslog problem
Message-Id: <8q5tlj$7hc$1@tilde.csc.ti.com>

I am getting the following error while trying to write using the syslog
function

"Prototype mismatch: sub Sys::Syslog::_LARGE_FILE_SOURCE vs () (at eval 5)
line 1."

Any ideas what might be wrong?

TIA,
TH.
[Remove x from tambaax while replying]




------------------------------

Date: Mon, 18 Sep 2000 19:04:45 GMT
From: Bart Lateur <bart.lateur@skynet.be>
Subject: Re: Teaching Perl
Message-Id: <6mpcss4djdtnc8iqajc8ms0h12mqno5d2p@4ax.com>

Sigvald Refsum wrote:

>Start with the small point of what exactly "c" is on the left hand side of the
>"equal sign" compared to what "c" is on the rigth hand side.

It's not an equal sign. Er... it does not symbolise an equal sign. It's
an assignment symbol. The LHS and the RHS have a before/after
relationship to each other. Just like when one gets a haircut. You don't
have both haircuts at the same time. (Half of them, maybe...)

-- 
	Bart.


------------------------------

Date: Mon, 18 Sep 2000 15:46:32 -0400
From: brian@smithrenaud.com (brian d foy)
Subject: Re: Teaching Perl
Message-Id: <brian-ya02408000R1809001546320001@news.panix.com>

In article <6mpcss4djdtnc8iqajc8ms0h12mqno5d2p@4ax.com>, Bart Lateur <bart.lateur@skynet.be> posted:

> Sigvald Refsum wrote:
> 
> >Start with the small point of what exactly "c" is on the left hand side of the
> >"equal sign" compared to what "c" is on the rigth hand side.
> 
> It's not an equal sign. Er... it does not symbolise an equal sign.

this just made me realize that when i present the assignment operator
is say "dollar foo equals ...".  i suppose it makes sense in context
since i haven't noticed a conceptual problem with it during an class.

perhaps you say something different (and that doesn't take 50
words to get out ;) ?

-- 
brian d foy                    
CGI Meta FAQ <URL:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
Perl Mongers <URL:http://www.perl.org/>


------------------------------

Date: 18 Sep 2000 14:31:10 -0400
From: ray@soyokaze.biosci.ohio-state.edu (William C. Ray)
Subject: Re: tutorial for advanced experimental regex  features?
Message-Id: <200009181827.OAA25640@soyokaze.biosci.ohio-state.edu>



Having just fought through implementing (with the assistance of the
kind members of this group, to give credit where it is due)
exactly what the original poster is trying to do, I have two additional
comments that I haven't seen mentioned:

1)  The (?{...}) construct, while syntactically acceptable in 5.005_03,
    does not seem to carry $1, $2, etc into the context of the inner
    eval.  If I recall correctly, these end up carrying in the values
    that they held before the beginning of the current match under 5.005_03,
    making the construct somewhat less useful than it could be.  This
    is fixed in 5.6 and the code as demonstrated several places in
    this and other recent discussion works as expected under 5.6.

2)  Somebody correct me if I'm wrong (just another C hacker here - I
    have a love/hate relationship with Perl's refusal to let me properly
    access and manage memory), but from testing, it looks like the
    regex engine maintains at least some parts of its state globally, so
    if one attempts to use a regex in the context of an internal eval
    in a regex, the results are at best undefined.

    For example, if one does something like the following, strange things
    can happen.

Will Ray
ray@soyokaze.biosci.ohio-state.edu


#!/usr/local/bin/perl

    $mydebug = 4;    # control whether this breaks or not
                     # set to 1, it should work.
                     # set to 2, it might work
                     # set to 3, it will probably segfault
                     # set to 4, it will probably run, but
                     #           muck up the context of the
                     #           regex in the main while loop


    # Stupid subroutine - depending on the value of $mydebug
    #   checks to determine if its arguments sum to 27
    #   or diddles around with some regexes, and attempts
    #   see if either of the arguments last two
    #   character positions is "27" or splits both arguments
    #   between characters and returns a fail, which should make
    #   the outer regex iterate through all possible combinations,
    #   seems to really break something instead. (yes, I know it's a
    #   stupid subroutine, just trying to give the regex engine a
    #   quick workout)
    sub foo {
      my ($invar1, $invar2) = @_;
      my (@invar1split, @invar2split, $i);
    # local ($1,$2);                # trying this won't fail,
                                    # but it won't help either.
      if ($mydebug == 1)
      {
        if(($invar1 + $invar2) == 27 )
        {
          return 1;
        }
          print $invar1." and ".$invar2." do not sum to 27\n";
        return 0;
      }
      if ($mydebug == 2)
      {
        if($invar1 =~ /27$/) { return 1 };   # just a plain match
        if($invar2 =~ /27$/) { return 1 };
        print "Neither ".$invar1." nor ".$invar2." end in 27\n";
        return 0;
      }
      if ($mydebug == 3)
      {
        if($invar1 =~ /(27)$/) { return 1 }; # put something in $1, breaks
        if($invar2 =~ /(27)$/) { return 1 }; # even if we local $1 above.
        print "Neither ".$invar1." nor ".$invar2." end in 27\n";
        return 0;
      }
      if ($mydebug == 4)
      {
        @invar1split = split "",$invar1;
	@invar2split = split "",$invar2;
        return 0;                            # universally fail here,
                                             # this is just to demonstrate
                                             # that split mucks up the
                                             # outer context even if it
                                             # shouldn't touch $1, etc.
      }
    }

    $junkstring="bbbb";
    $teststring="122341215026012705758";


    # run exhaustively through our teststring looking
    # for places where there are positions where
    # substrings extracted as $1 and $2 satisfy foo()
    # above.

    while (length($teststring) > 1)
    {

      $junkstring =~ /()/;   # Force $1 to be "", as this next bit
                             # behaves differently under 5.005_03 and
                             # 5.6 - can produce some weird results
                             # if we use a valid match here.
      $teststring =~ /
                      ^(                 # Starting from the beginning of
                         (.+)(.+)        # pick two arbitrary strings
                                         # next to eachother (you can
                                         # insert arbitrary regex requirements
                                         # here as well)
                       )
                       (?(?{
                             not foo($2,$3)
                         })
                         (?!)            # evaluate foo() for the two
                       )                 # substrings and fail the regex
                                         # if foo() fails
                     /x;

      if ($1 ne "") {                    # we got a match that satisfies foo()
        print "Found ".$1."\n";
        print "      containing ".$2." and ".$3." which satisfy foo()\n";
      }
      $teststring =~ s/.//;              # drop one character from the front
                                         # of $teststring

    }                                    # and try again





------------------------------

Date: 18 Sep 2000 14:15:02 -0500
From: Ren Maddox <ren.maddox@tivoli.com>
Subject: Re: tutorial for advanced experimental regex  features?
Message-Id: <m3em2hy0jt.fsf@dhcp11-177.support.tivoli.com>

ray@soyokaze.biosci.ohio-state.edu (William C. Ray) writes:

>     $mydebug = 4;    # control whether this breaks or not
>                      # set to 1, it should work.
>                      # set to 2, it might work
>                      # set to 3, it will probably segfault
>                      # set to 4, it will probably run, but
>                      #           muck up the context of the
>                      #           regex in the main while loop

$ perl -v
This is perl, v5.6.0 built for i686-linux-thread-multi

3 fails on the first successful match.
1 and 2 seem to be fine
even 4 seems to be fine

Guess that's why they call them experimental features.... :)

-- 
Ren Maddox
ren@tivoli.com


------------------------------

Date: 18 Sep 2000 18:49:14 +0100
From: nobull@mail.com
Subject: Re: Two questions: 1)Erasing temporary files 2)post method
Message-Id: <u9snqxfv51.fsf@wcl-l.bham.ac.uk>

as <art_s@pacbell.net> writes upside down and quotes the whole of the
message he's following up.  He then goes on to winge about being told
he's off-topic.

In short, he's a troll.  But, contrary to popular belief, we do try to
help people here even if they deliberately set out to piss us off.

> Abigail wrote:
> 
> > as (art_s@pacbell.net) wrote on MMDLXXIV September MCMXCIII in
> > <URL:news:39C4283D.50195FE@pacbell.net>:
> > :) I have two questions involving processsing CGI.
> >
> > This group's topic is not CGI.
> >
> > :) 1) I write temporary files like gifs in a cgi script. I would like to
> > :) erase them when the script is done and the pic is displayed to the user.
> > :) Unfortunately, the methods i have tried seem to erase the temporary
> > :) graphic before the server sends it to the user.
> >
> > The solution to this is utterly straightforward, but it has nothing to
> > do with Perl. You'd do the same thing if you programmed in any other
> > language. About the only Perl thing that's relevant is 'unlink'.
>
> 'unlink' is precisely what does not work.

Nonsense.  The unlink works just dandy.  What doesn't work is deleting
a file and then trying to open it.  It doesn't matter what language to
wrote the script in.

There are 3 obvious alternatives: 
 
1) Don't redirect to a temporary file - simply have the script emit
   the image.

2) Have a garbage collection process that runs periodically and
   deletes temporary files over a certain age.  

3) Have your CGI script fork-off-and-die (not forgetting to close
   STDOUT) and then sleep for a bit before deleting the file.

(2) Requires that you can have periodic tasks.  (3) Can have a lot of
sleeping processes if you are getting a lot of hits.

Like Abigail says this has nothing to do with Perl, you'd have the
same choices with a CGI script written in any language.

-- 
     \\   ( )
  .  _\\__[oo
 .__/  \\ /\@
 .  l___\\
  # ll  l\\
 ###LL  LL\\


------------------------------

Date: Mon, 18 Sep 2000 19:45:50 GMT
From: bluearchtop@my-deja.com
Subject: Upgrade Error: ld.so.1: perl: fatal: libdb-3.1.so: open failed: No such file or directory
Message-Id: <8q5rd7$7rt$1@nnrp1.deja.com>

I just upgraded from 5.005 to 5.6 and previous scripts that worked now
give me:

ld.so.1: perl: fatal: libdb-3.1.so: open failed: No such file or
directory

The make test worked fine however in all tests. This particular script
uses DB_File.  Is there something I need to do?

Thanks


Sent via Deja.com http://www.deja.com/
Before you buy.


------------------------------

Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 16 Sep 99)
Message-Id: <null>


Administrivia:

The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc.  For subscription or unsubscription requests, send
the single line:

	subscribe perl-users
or:
	unsubscribe perl-users

to almanac@ruby.oce.orst.edu.  

| NOTE: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.

For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V9 Issue 4365
**************************************


home help back first fref pref prev next nref lref last post