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]]
Sent: July-27-15 7:35 AM
To: [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
