When you
> build ARSPerl as 32 bit you'll have to use a 32 bit perl interpreter. I feel
> your pain, it's very annoying.
>
> Rusty
>
>
> --- On Tue, 9/9/08, Vaughan, Mark <[EMAIL PROTECTED]> wrote:
>
> > From: Vaughan, Mark <[EMAIL PROTECTED]>
&
-Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Thilo Stapff
> Sent: Tuesday, September 09, 2008 10:02 AM
> To: ARSperl User Discussion
> Subject: Re: [Arsperl-users] ARSperl 1.91 make test errors
>
>
> I don't have any experienc
k <[EMAIL PROTECTED]>
> Subject: Re: [Arsperl-users] ARSperl 1.91 make test errors
> To: "ARSperl User Discussion"
> Date: Tuesday, September 9, 2008, 10:35 AM
> Are there any other possible solutions?
>
> If I can get the SAs to install a 32-bit Perl, do I need to
&g
e ignorance.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Thilo Stapff
> Sent: Tuesday, September 09, 2008 10:02 AM
> To: ARSperl User Discussion
> Subject: Re: [Arsperl-users] ARSperl 1.91 make test errors
>
>
> I don&#
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thilo Stapff
Sent: Tuesday, September 09, 2008 10:02 AM
To: ARSperl User Discussion
Subject: Re: [Arsperl-users] ARSperl 1.91 make test errors
I don't have any experience with 64 bit systems so I can only take a
guess here. To me
I don't have any experience with 64 bit systems so I can only take a
guess here. To me, the situation looks as follows:
The Remedy API libraries are 32 bit, so ARSperl has to be compiled with
-m32.
Your Perl interpreter is 64 bit, so ARSperl would also have to be
compiled as 64 bit, which of cou
I have added the '-m32' switch as suggested in another thread, but I
still get the same errors:
gcc -c -I/export/third-party/remedy/ars/software/ars710p3/api/include
-fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O
-DVERSION=\"1.91\" -DXS_VERSION=\"1.91\" -fPIC
"-I/usr/loc
7 matches
Mail list logo
