Re: Problem with System Beep

[John Park]

hmm, doesn't seem to work, still.

On Thursday, October 16, 2003, at 04:00  AM, Philippe de Rochambeau 
wrote:

Works fine for me: perl -e 'print "\a"' => beep !

Up the volume!

Philippe

Le jeudi, 16 oct 2003, à 04:54 Europe/Paris, John Park a écrit :

For some reason I can't hear a system beep.
Maybe I'm mistaken, but isn't:
print "\a";
suppose to generate a system beep?
I'm using Mac OS X v10.2.3 and I remember being able to do this with 
v10.0.0.

Thanks
-John

RE: BBEdit-Perl confusion

[Doug McNutt]

At 16:12 -0700 10/16/03, Ingles, Juan W. wrote:
>I wonder: Is this because
>/opt/local/bin/perl   points to the perl 5.6 binary
>or
>5.6 binary path is hard coded in BBEdit

I don't have any /opt/local/bin/. None was created by the CPAN perl 5.8 install in 
July 2002

> > which perl
>on the terminal will tell you what binary you are launching

It just says /usr/bin/perl and says nothing about what it links to.

When I installed 5.8 I had to recreate the link for /usr/bin/perl manually and that 
fixed up almost everything but BBEdit 6.x was in vogue at the time and worksheets were 
brand new.

-- 
-->  There are 10 kinds of people:  those who understand binary, and those who don't 
<--

Re: BBEdit-Perl confusion

[Conrad Schilbe]

On 10/16/03 5:12 PM, "Ingles, Juan W." <[EMAIL PROTECTED]> wrote:

> I wonder: Is this because
> /opt/local/bin/perl   points to the perl 5.6 binary
> or 
> 5.6 binary path is hard coded in BBEdit
> 
> 
> 
>> which perl
> on the terminal will tell you what binary you are launching
> 
> 
> 
> ( not currently at my machine to check )
> juan
> 
> -Original Message-
> From: Vic Norton [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 16, 2003 2:46 PM
> To: [EMAIL PROTECTED]
> Subject: Re: BBEdit-Perl confusion
> 
> I guess there is no fix right now.
> 
> But actually the bug is somewhat convenient. Now a BBEdit script
> starting with
>#!/opt/local/bin/perl -w
># Perl 5.8
> uses Perl 5.8.0 with its @INC list if "Run" from BBEdit and
> uses Perl 5.6.0 with a different @INC list if "Run in Terminal".
> 
> It's not all bad---though it is a bit confusing.
> 
> Regards,
> 
> Vic
> 
> At 12:03 PM -0400 10/16/03, Bare Bones Software Technical Support wrote:
>> There is a bug in BBEdit where run in terminal hard codes the path
>> to perl as /usr/bin/perl instead of taking the other usual steps to
>> choose which interpreter to run. I have a bug logged and this will
>> be corrected for the next release.
> 
> At 9:56 AM -0400 10/16/03, Vic Norton wrote:
>> I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
>> DarwinPorts . Perl
> 5.8.0
>> resides in the "/opt/local/bin" directory, and this directory is at the
>> beginning of $PATH. Everything works well except that BBEdit seems
> rather
>> confused. Any suggestions as to how to rectify this confusion would be
>> appreciated.


I have now also found that running this command in Bbedit:

print `which perl`;

Produces the following error:

"MANPATH: Undefined variable."

That is a very strange error to be produced by that command... I thought
maybe it was a problem using the `` syntax to execute via the shell so I
tried system() syntax, same results... I then thought maybe it was that
bbedit choked on any system command but,

print `echo "test"`;

Worked fine... Very strange must have something to do with a hard coded
environment in perl.

C.

Re: BBEdit-Perl confusion

[Conrad Schilbe]

On 10/16/03 5:12 PM, "Ingles, Juan W." <[EMAIL PROTECTED]> wrote:

> I wonder: Is this because
> /opt/local/bin/perl   points to the perl 5.6 binary
> or 
> 5.6 binary path is hard coded in BBEdit

Would this be in a plist file for BBedit?

C.

> 
> 
> 
>> which perl
> on the terminal will tell you what binary you are launching
> 
> 
> 
> ( not currently at my machine to check )
> juan
> 
> -Original Message-
> From: Vic Norton [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 16, 2003 2:46 PM
> To: [EMAIL PROTECTED]
> Subject: Re: BBEdit-Perl confusion
> 
> I guess there is no fix right now.
> 
> But actually the bug is somewhat convenient. Now a BBEdit script
> starting with
>#!/opt/local/bin/perl -w
># Perl 5.8
> uses Perl 5.8.0 with its @INC list if "Run" from BBEdit and
> uses Perl 5.6.0 with a different @INC list if "Run in Terminal".
> 
> It's not all bad---though it is a bit confusing.
> 
> Regards,
> 
> Vic
> 
> At 12:03 PM -0400 10/16/03, Bare Bones Software Technical Support wrote:
>> There is a bug in BBEdit where run in terminal hard codes the path
>> to perl as /usr/bin/perl instead of taking the other usual steps to
>> choose which interpreter to run. I have a bug logged and this will
>> be corrected for the next release.
> 
> At 9:56 AM -0400 10/16/03, Vic Norton wrote:
>> I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
>> DarwinPorts . Perl
> 5.8.0
>> resides in the "/opt/local/bin" directory, and this directory is at the
>> beginning of $PATH. Everything works well except that BBEdit seems
> rather
>> confused. Any suggestions as to how to rectify this confusion would be
>> appreciated.

RE: BBEdit-Perl confusion

[Ingles, Juan W.]

I wonder: Is this because 
/opt/local/bin/perl   points to the perl 5.6 binary
or 
5.6 binary path is hard coded in BBEdit



> which perl
on the terminal will tell you what binary you are launching



( not currently at my machine to check )
juan

-Original Message-
From: Vic Norton [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 16, 2003 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: BBEdit-Perl confusion

I guess there is no fix right now.

But actually the bug is somewhat convenient. Now a BBEdit script
starting with
 #!/opt/local/bin/perl -w
 # Perl 5.8
uses Perl 5.8.0 with its @INC list if "Run" from BBEdit and
uses Perl 5.6.0 with a different @INC list if "Run in Terminal".

It's not all bad---though it is a bit confusing.

Regards,

Vic

At 12:03 PM -0400 10/16/03, Bare Bones Software Technical Support wrote:
>There is a bug in BBEdit where run in terminal hard codes the path 
>to perl as /usr/bin/perl instead of taking the other usual steps to 
>choose which interpreter to run. I have a bug logged and this will 
>be corrected for the next release.

At 9:56 AM -0400 10/16/03, Vic Norton wrote:
>I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
>DarwinPorts . Perl
5.8.0
>resides in the "/opt/local/bin" directory, and this directory is at the
>beginning of $PATH. Everything works well except that BBEdit seems
rather
>confused. Any suggestions as to how to rectify this confusion would be
>appreciated.

Re: BBEdit-Perl confusion

[Vic Norton]

I guess there is no fix right now.

But actually the bug is somewhat convenient. Now a BBEdit script starting with
#!/opt/local/bin/perl -w
# Perl 5.8
uses Perl 5.8.0 with its @INC list if "Run" from BBEdit and
uses Perl 5.6.0 with a different @INC list if "Run in Terminal".
It's not all bad---though it is a bit confusing.

Regards,

Vic

At 12:03 PM -0400 10/16/03, Bare Bones Software Technical Support wrote:
There is a bug in BBEdit where run in terminal hard codes the path 
to perl as /usr/bin/perl instead of taking the other usual steps to 
choose which interpreter to run. I have a bug logged and this will 
be corrected for the next release.
At 9:56 AM -0400 10/16/03, Vic Norton wrote:
I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
DarwinPorts . Perl 5.8.0
resides in the "/opt/local/bin" directory, and this directory is at the
beginning of $PATH. Everything works well except that BBEdit seems rather
confused. Any suggestions as to how to rectify this confusion would be
appreciated.

Re: BBEdit-Perl confusion

[Doug McNutt]

At 09:56 -0400 10/16/03, Vic Norton wrote:
>I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
>DarwinPorts . Perl 5.8.0
>resides in the "/opt/local/bin" directory, and this directory is at the
>beginning of $PATH. Everything works well except that BBEdit seems rather
>confused.

BBEdit is almost surely executing perl 5.6 and it's probably because of a hard coded 
path.

I had 5.8 running, with some difficulty, over a year ago from the CPAN distribution 
and it is in /opt/. But I had to remove 5.6 from the other directories. It was an 
interesting experience while I learned about gzip and tar to preserve my options.

You'll be OK after that so long as the link in /usr/bin/perl points to the new 
version. Some have complained about Apple's installer requiring the old perl 5.6 but 
it has never bitten me.

-- 
-->  There are 10 kinds of people:  those who understand binary, and those who don't 
<--

BBEdit-Perl confusion

[Vic Norton]

I have recently installed Perl 5.8.0 on my iMac via "PortsManager" from
DarwinPorts . Perl 5.8.0
resides in the "/opt/local/bin" directory, and this directory is at the
beginning of $PATH. Everything works well except that BBEdit seems rather
confused. Any suggestions as to how to rectify this confusion would be
appreciated.
Here is an example of BBEdit's confusion.

In Terminal the command
   % perl -e 'for (@INC) { print "$_\n" }'
produces
   /opt/local/lib/perl5/5.8.0/darwin
   /opt/local/lib/perl5/5.8.0
   /opt/local/lib/perl5/site_perl/5.8.0/darwin
   /opt/local/lib/perl5/site_perl/5.8.0
   /opt/local/lib/perl5/site_perl
   .
When "Run" from BBEdit the script
   #!/opt/local/bin/perl -w
   for (@INC) { print "$_\n" }
produces exactly the same output in the "Unix Script Output" window.
However, when this script is "Run in Terminal" from BBEdit, the output
is
   /Users/vicnorton/Perl/MyPerl/Misc/tests-work
   /System/Library/Perl/darwin
   /System/Library/Perl
   /Library/Perl/darwin
   /Library/Perl
   /Library/Perl
   /Network/Library/Perl/darwin
   /Network/Library/Perl
   /Network/Library/Perl
   .
 Something seems to be wrong here.

 Any suggestions as to what is going on here and how to rectify it
 would be greatly appreciated.
 Regards,

 Vic

--
*---* mailto:[EMAIL PROTECTED]
| Victor Thane Norton, Jr.
| Mathematician and Motorcyclist
| phone: 419-353-3399
*---* http://vic.norton.name

Problems with LWP 5.7.2 (cont'd)

[Philippe de Rochambeau]

Hello,

I updated the Storable module as per the instructions given in 
http://fink.sourceforge.net/faq/usage-fink.php#perl-undefined-symbol 
(thank you Neil Bowers).

Unfortunately, while building LWP 5.7.2, I got the same 
undefined-symbol messages:

Checking for URI... ok
Checking for HTML::Parser..dyld: perl Undefined symbols:
_Perl_safefree
_Perl_safemalloc
_Perl_saferealloc
_Perl_sv_2pv
_Perl_sv_catpvn
_Perl_sv_catsv
_Perl_sv_pvn_force
_perl_call_method
_perl_call_sv
_perl_get_hv
_perl_get_sv
Trace/BPT trap
Philippe

Re: LWP 5.6.8 and 5.7.2

[Neil Bowers]

whenever I run the simple LWP program below, I get the following error 
messages (I am using perl 5.8.0). I get the same message when I try to 
build LWP 5.7.2.

[philippe ~/Desktop] % perl testlwp1.pl
dyld: perl Undefined symbols:
_Perl_safefree
[...loads more...]
_perl_get_sv
Trace/BPT trap
[philippe ~/Desktop] %
Any help would be much appreciated.
I think the following will probably help you:

	http://fink.sourceforge.net/faq/usage-fink.php#perl-undefined-symbol

Neil

Re: LWP 5.6.8 and 5.7.2

[Clint Moore]

On Thursday, October 16, 2003, at 05:49 AM, Philippe de Rochambeau 
wrote:
Hello,

whenever I run the simple LWP program below, I get the following error 
messages (I am using perl 5.8.0). I get the same message when I try to 
build LWP 5.7.2.


You've got an old xs library trying to load.

Check this post out for an explaination and a fix:

http://nntp.x.perl.org/group/perl.perl5.porters/63742

LWP 5.6.8 and 5.7.2

[Philippe de Rochambeau]

Hello,

whenever I run the simple LWP program below, I get the following error 
messages (I am using perl 5.8.0). I get the same message when I try to 
build LWP 5.7.2.

[philippe ~/Desktop] % perl testlwp1.pl
dyld: perl Undefined symbols:
_Perl_safefree
_Perl_safemalloc
_Perl_saferealloc
_Perl_sv_2pv
_Perl_sv_catpvn
_Perl_sv_catsv
_Perl_sv_pvn_force
_perl_call_method
_perl_call_sv
_perl_get_hv
_perl_get_sv
Trace/BPT trap
[philippe ~/Desktop] %
Any help would be much appreciated.

Philippe

== Program ==

use LWP::UserAgent;
$ua = LWP::UserAgent->new;
$ua->agent("MyApp/0.1 ");
 # Create a request
 my $req = HTTP::Request->new(POST => 'http://www.perl.com');
 $req->content_type('application/x-www-form-urlencoded');
 $req->content('match=www&errors=0');
 # Pass request to the user agent and get a response back
 my $res = $ua->request($req);
 # Check the outcome of the response
 if ($res->is_success) {
 print $res->content;
 } else {
 print "Bad luck this time\n";
 }

Re: Problem with System Beep

[John Delacour]

At 10:54 pm -0400 15/10/03, John Park wrote:
 For some reason I can't hear a system beep.
 Maybe I'm mistaken, but isn't:
 print "\a";
 suppose to generate a system beep?
 I'm using Mac OS X v10.2.3 and I remember being able to do this with v10.0.0.
Are you talking of using Apple events with 'do shell script'?  Using 
10.2.8, these two sound the bell for me:

  [eremita:~] jd% perl -e 'print "\a"'

  tell app "Terminal" to do script "perl -e 'print qq~\\a~'" in window 1

and there is no problem with MacPerl...

..but these produce a character and no sound:

  do shell script "perl -e 'print qq~\\a~'"

  do shell script "perl -e '
  open F, qq~>/tmp/bell~;
  print F qq~print qq(\\a)~ ;
  close F;' ;
  perl /tmp/bell"
There is the same problem running the script in BBEdit, probably 
because BBEdit is using AE.  My Eudora perl thing 
, which certainly 
uses AE, will also print a silent character.

JD

Re: DBI and DBD::MySQL (Panther)

[Conrad Schilbe]

To clear up any confusion for others that may pick up this thread, my
previous email stated that a patch should not be made to perl sources... I
mistook the details below as implying that each perl module (i.e.
DBD::mysql) be patched for an error in the Config.pm module. In actuality, I
believe, the patch is intended for the perl source itself... My bad.

A demonstration of when to leave things up to those who know what they are
talking about...

C.

On 10/15/03 6:28 PM, "Edward Moy" <[EMAIL PROTECTED]> wrote:

> In hints/darwin.sh, replace
> 
>   *) ld="MACOSX_DEPLOYMENT_TARGET=10.3 ${ld}" ;;
> 
> with
> 
>   *) ld="env MACOSX_DEPLOYMENT_TARGET=10.3 ${ld}" ;;
> 
> Hopefully, this will go into 5.8.2.
> 
> Ed
> 
> On Oct 15, 2003, at 5:05 PM, David Wheeler wrote:
> 
>> On Wednesday, October 15, 2003, at 04:58  PM, Edward Moy wrote:
>> 
>>> We recently discovered the DBD::mysql problem as well.  The patch is
>>> to edit 
>>> /System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm,
>>> replacing:
>>> 
>>> ld='MACOSX_DEPLOYMENT_TARGET=10.3 cc'
>>> 
>>> with
>>> 
>>> ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc'
>>> 
>>> Unfortunately, this change is too late to get into Panther.
>> 
>> Is there a patch that could go into the Perl sources themselves?
>> 
>> Regards,
>> 
>> David
>> 
>> -- 
>> David Wheeler AIM: dwTheory
>> [EMAIL PROTECTED]  ICQ: 15726394
>> http://www.kineticode.com/ Yahoo!: dew7e
>>Jabber:
>> [EMAIL PROTECTED]
>> Kineticode. Setting knowledge in motion.[sm]
>> 
> 

Re: Problem with System Beep

[Philippe de Rochambeau]

Works fine for me: perl -e 'print "\a"' => beep !

Up the volume!

Philippe

Le jeudi, 16 oct 2003, à 04:54 Europe/Paris, John Park a écrit :

For some reason I can't hear a system beep.
Maybe I'm mistaken, but isn't:
print "\a";
suppose to generate a system beep?
I'm using Mac OS X v10.2.3 and I remember being able to do this with 
v10.0.0.

Thanks
-John