Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: <sergei dot cher at thomsonreuters dot com>
Subject: RE: Need help in troubleshooting Sybperl installation on Sun Solaris10
Date: Apr 24 2008 6:46PM


But I finally resolved the issue - it was my fault.

Several days ago my peer simply moved the whole directory tree
"site_perl" with all the Sybperl libraries from the production Sun
Solaris box to my box and put it in 2 places - just in case. I was sure
that I deleted all these files, but apparently I forgot to delete
several directories in one of these 2 locations before running the
install yesterday.

2) So, I cleaned up everything - deleted Sybperl libraries and
directories from everywhere then did the fresh install and everything
started to work.

Lesson learned: 

1) Don't allow anybody to experiment with software on your box - ask
him/her to read the documentation first.

2) Read FAQ in Perl distribution - this issue is described there in the
Paragraph 2.4.

Michael - thanks a lot for your help - I really appreciate it.

Sergei Cher
Thomson Reuters (former Thomson Financial)
Boston, MA, USA

-----Original Message-----
From: []
On Behalf Of Michael Peppler
Sent: Thursday, April 24, 2008 2:14 PM
Subject: Re: Need help in troubleshooting Sybperl installation on Sun
Solaris10 wrote:
> The output of the "make test" is presented below.
> BTW, deleted the old installation and reinstalled Sybperl -2.18.
> commands still fail ("make test" produced the same errors as after the
> first installation).
> =============================================================
> $ /usr/ccs/bin/make test
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(0,
> 'blib/lib', 'blib/arch')" t/*.t
> t/1_db_dblib...........ok
> t/1_db_money...........ok
> t/2_ct_ctlib...........ok
> t/2_ct_cursor..........ok
> t/2_ct_nsql............ok
> t/2_ct_prepare.........ok
> t/2_ct_xblk............ok
> t/3_bcp................Sybase message 10331, Severity 14, state 1
> Server `tm3qadb1'
> Line 1
>     CREATE TABLE permission denied, database vrdn_network, owner dbo
>     1> create table vrdn_network..bcp(f1 char(5), f2 int, f3 text) 

OK - that's a benign error.

Do you have the same env. variables set when you run script that 
generates the SIGBUS error?

Michael Peppler           -                 Peppler Consulting SaRL      -        
Sybase DBA/Developer      -   TeamSybase:
Sybase on Linux FAQ       -