Hi,
I have just compiled RRR|Chive on 64-bit linux with the 7.6.03 API. It
seems to work just fine.
I have both tried with and without specifying a TCP-port.
These are the libraries I am linking to:
LDLIBS = -lar_lx64 -lnsl -lpthread -lcurses -ldl
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Does anyone have any suggestions on this? Is it even on the radar of
> anyone at BMC?
>
> -- Nathan
>
> ------------------------------------------------------------
> Nathan Neulinger [email protected]
> Missouri S&T Information Technology (573) 612-1412
> System Administrator - Principal KD0DMH
>
>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:[email protected]] On Behalf Of Neulinger, Nathan
>> Sent: Monday, September 13, 2010 9:44 AM
>> To: [email protected]
>> Subject: 64bit linux (lx64) api still broke with 7.6.3?
>>
>> Been trying to get ARSperl working on a 64bit linux host for a while
>> (snapshots or CVS), but seem to still be having the various 64bit
>> issues, even with the latest 7.6.3 build of the ar API.
>>
>> Does anyone here have any information on this?
>>
>> I don't have any remedy/BMC support access as our AR server is hosted
>> by
>> another campus in our system, but we do use the client and API.
>>
>> Only information I have on the previous bug... is this still not
>> corrected in 7.6.3?
>>
>> defect # SW00330613
>> Summary: Problems with 64 Bit AR API Libraries under Linux
>> Status: Open
>> Type: Product
>> Product: AR System
>> Target Release: Esc 7.5.0 Server
>> Classification Tentatively Targeted
>> Version: 7.5
>> Target Release Version: Future Patch Release
>>
>> The symptom I have still is the can't encode arguments rpc error if
> the
>> login port isn't specified, and glibc double free errors. If I bypass
>> the glibc memory checks with MALLOC_CHECK env var, it looks like it's
>> still unable to connect properly.
>>
>> I'd really like to get moved off of some legacy 32bit systems that are
>> having to be retained to run the AR api, but having to build an entire
>> separate 32bit perl isn't exactly a reasonable alternative.
>>
>> -- Nathan
>>
>> ------------------------------------------------------------
>> Nathan Neulinger [email protected]
>> Missouri S&T Information Technology (573) 612-1412
>> System Administrator - Principal KD0DMH
>>
>>
> _______________________________________________________________________
>> ________
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
