Hi Conny, We've retested using the following steps:
- Recompile arsperl o Received a lot of warnings - Run make test o Received errors on 1 out of 26 tests. o Note: when running the test we didn't use a config file for the server info, we responded to the prompts Next you: - Wrote a simple test script (see below) - Executing the program received the following runtime errors (screenshot of this output is also included): o Can't locate auto/ARS/autosplit.ix in @INC (@INC contains: /usr/local/lib64/perl5/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5 /usr/share/perl5 .) at /usr/share/perl5/AutoLoader.pm line 173. o at ARS.pm line 64 o Can't locate loadable object for module ARS in @INC (@INC contains: /usr/local/lib64/perl5/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5 /usr/share/perl5 .) at ../remedy/scripts/perl/test.pl line 4 o Complication file in require at ../remedy/scripts/perl/test.pl line 4 o BEGIN failed-compilation aborted at ../remedy/scripts/perl/test.pl line 4 The test script is as simple as we could make: [cid:[email protected]] Here's a screenshot of the error output (the same as what I typed out above): [cid:[email protected]] Thanks again for your assistance, Rance From: [email protected] [mailto:[email protected]] Sent: July-27-15 10:24 AM To: [email protected] Cc: [email protected] Subject: Re: [Arsperl-users] Errors with ARSPerl 2.0 on 64 bit Linux environment API v8101 Hi Rance, I think I've found your "mistake". It seems like you put in the servername with a blank or some other strange character in front. Pls. check the file t/config.cache You can safely delete the file and rerun perl Makefile.PL or you edit this file. KR Conny Von: Young, Rance [mailto:[email protected]] Gesendet: Montag, 27. Juli 2015 14:49 An: ARSperl User Discussion Cc: Daniel Asselin Betreff: Re: [Arsperl-users] Errors with ARSPerl 2.0 on 64 bit Linux environment API v8101 Hi Conny, Thanks for the response. Yes actually that's a strange error because we're building arsperl on the same system that remedy is running on. Remedy is up, and users can connect both through the user tool, and the midtier. Thanks, Rance From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: July-27-15 7:35 AM To: [email protected]<mailto:[email protected]> Subject: Re: [Arsperl-users] Errors with ARSPerl 2.0 on 64 bit Linux environment API v8101 Hi Rance, "Cannot open catalog; Message number = 90 ( remdevapp1-mo3.osn.wireless.rogers.com : RPC: Success) (ARERR #90))" I've seen this kind of error when the servername is not resolvable. Pls. test if "ping remdevapp1-mo3.osn.wireless.rogers.com" works. It should at least resolve the name to an ip address. KR Conny Von: Young, Rance [mailto:[email protected]] Gesendet: Montag, 27. Juli 2015 13:12 An: [email protected]<mailto:[email protected]> Betreff: [Arsperl-users] Errors with ARSPerl 2.0 on 64 bit Linux environment API v8101 Hi folks, I'm working with a colleague trying to configure ARSPerl on a 64 bit linux environment and running into issues. I was hoping that someone could provide assistance, or information on whether anyone has tried compiling on 64 bit linux yet? Specs are as follows: Perl v5.10.1 built for x86_64-linux-thread-multi Linux red hat enterprise 6.6 santiago in a VM. Steps taken: - make perl using 9.0 API failed (errors related to header file changes) - make perl using 8.1 API generated many warnings - make test failed with errors Output from the attempt to make the project with 8.1 API is attached. Thanks in advance for any assistance you can provide, Rance Young
------------------------------------------------------------------------------
-- Arsperl-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/arsperl-users
