Community
Participate
Working Groups
Support existing RAC clients and agents through compatibility layers on Windows IPF and EM64T (64-bit) platform. Work estimate assumes the Windows version is working and this work is focused on porting. Basic support does not include file transfer, SSL, or dynamic discovery (aka peer2peer) support. (enhancement 119571 is being broken down to better track the work through the iterations - start using this bugzilla for committing work in this area)
Corrected time estimate to 1.5 weeks.
Modified title and scope of this bug to include the Windows IPF work only. The Windows EM64T work is now captured in a new bug 130966. Deferring new AC completion via compatibility mode on 3 platforms: Linux IPF, Linux EM64T, and Windows EM64T. The supported platforms are now expected to be: Windows IA32, Linux IA32, and Windows IPF. (Per the TPTP Platform call 3/8/06 with Sri's approval given the need to fit i2 work into a shortened development time.)
Randy - since this is expected to be a build issue, reassigning to you.
Going to have to hand-craft makefiles, which will be *.mak64 named.
Created attachment 40536 [details] Windows IPF Porting Guidelines
Although there are more porting efforts to be done, it appears basic functionality is now in place.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.