J-Link problems in Wildfire on Linux

[cmarcum]

Hello everyone,




Is anyone using J-Link on Linux?




I have been trying to run the install test on SuSE 10.2 and CentOS(Red
Hat) 3.8 WS with no luck. I keep getting an error when starting it.



Foreign program "InstallTest" failed to initialize: error PRO_TK_GENERAL_ERROR




Pro/E runs fine otherwise.




I'm using Sun Java 1.5.0 on both. I have tried setting PRO_JAVA_COMMAND
in the shell and also in the config with jlink_java2 set to on.



!trail file version No. 1350
!Pro/ENGINEER TM Wildfire 3.0 (c) 2006 by Parametric Technology Corporation All Rights Reserved.
< 0 0.848593 897 0 0 716 1024 0 0 768 13
!mem_use INCREASE Blocks 7025, AppSize 39171320, SysSize 39270392
< 0 0.623407 734 0 0 526 1024 0 0 768 13
< 0 0.623407 660 0 0 526 1024 0 0 768 13
< 0 0.619000 619 0 0 526 1024 0 0 768 13
< 0 0.590222 619 0 0 498 1024 0 0 768 13
!%CEForeign program "InstallTest" failed to initialize: error PRO_TK_GENERAL_ERROR
!%CEMessage from foreign program: "&#137;

 

[damormino]

We have 10 seats of Pro/E on Linux. We haven't used J-Link yet, to my knowledge. I checked out your page on MechToolsJ for creating parametric hole features. Perhaps we will try MechTools and/or J-Link on Linux. I will report back if I find.

 

[thusske]

I have run ProE Wildfire 2.0 on linux (RH Ent. 4.0) running in asynch mode.


here is what my source file looked like


setenv PATH /usr/java/jdk1.5.0_02/bin:$PATH


setenv CLASSPATH ".:/usr/local/ptc/proeWildfire2.0/text/java/pfcasync.jar"


setenv PRO_COMM_MSG_EXE /usr/local/ptc/proeWildfire2.0/i486_linux/obj/pro_comm_msg


setenv LD_LIBRARY_PATH /usr/local/ptc/proeWildfire2.0/i486_linux/lib





To run the jlink tests requires that you set the location fo the pfc.jar or the pfcasync.jar file. Don't do both, it creats confusion for the compiler and even though it might compile it won't run(been there).


This should all be the same for ProeWildfire 3.0 also. I have since switched from using jlink in Linux to windows Also, something that you might want to try using is NetBeans. I am using 4.1 even though there is a newer version 5 out there, I am using 4.1 becuase in windows jlink only will run for me using jdk version 1.4.2_05.





Hope I have helped a little, and if I can help some more just let me know.





-Tylor
Edited by: thusske

 

[cmarcum]

Hello,

I thought since I started this thread I would end it with what I had found out so far.

I installed RedHat Enterprise Linux 3 WS update 8 which has IBM Java 1.4.2.

J-Link works using this setup on Wildfire 2.0 M220. Wildfire 3.0 M020 didn't but I think that maybe a bug in that build. I'll try another build later.

I know J-Link is not supported for build on 1.5 but I had been using 1.5 on Windows since Pro/E 2001 including WF2 and WF3.
This seems to be an issue with the JNI code in J-Link rejecting 1.5 for some reason.

I tested many distros of Linux including RHEL4 with 1.4 and 1.5 with no luck.
In short, in this case anyway, Supported also seems to mean only.

So I'm refactoring all my code back to 1.4 for now.

Thanks for everyones help.

Carl