Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Running F2 with J9

Well, at the moment I'm not sure. I had seen a similar situation when 
running on my Linux box about 3 weeks ago on WSDD/Eclipse 1. An SWT app 
which ran fine when launched from the workbench had problems with lesstif 
when running J9 from command line. That made me think maybe the launcher 
was doing something, but in retrospect maybe I was just getting "." in 
LD_LIBRARY_PATH working by luck when launched from the workbench.

As for F2, I could have sworn we were launching J9 and JRE in the same 
way, but I was looking over someone's shoulder. It is very possible we 
were launching J9 one directory up from libXm, and with JRE we were 
launching in same directory. I'll have to test again.

> on JRE we need to set LD_LIBRARY_PATH to find the libXm.so.2 library

regarding this - who is responsible for setting LD_LIBRARY_PATH to make 
this happen? Doc, something in SWT, or an RPM installer?

And does McQ's comment about SWT and launcher mean SWT deals with 
launchersrc.zip and eclipseMotif.c, or did I totally misunderstand that? 
(which would be nothing new :-)

-Andrew








Veronika_Irvine@xxxxxxx
Sent by: eclipse-dev-admin@xxxxxxxxxxx
06/04/2002 11:27 AM
Please respond to eclipse-dev

 
        To:     eclipse-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [eclipse-dev] Running F2 with J9


Andrew, on JRE we need to set LD_LIBRARY_PATH to find the libXm.so.2 
library.  Many people have "." on their LD_LIBRARY_PATH by default and as 
a result starting eclipse from the eclipse install directory succeeds 
without doing anything else. 

Are you saying this does not work with J9 or is setting LD_PRELOAD the 
equivalent? 




Andrew_Sandstrom@xxxxxxx 
Sent by: eclipse-dev-admin@xxxxxxxxxxx 
04/06/2002 11:59 AM 
Please respond to eclipse-dev 
        
        To:        eclipse-dev@xxxxxxxxxxx 
        cc: 
        Subject:        Re: [eclipse-dev] Running F2 with J9


There are a couple of problems I'm seeing with runningF2  on the latest 
J9. The J9 team is looking into some of them, but I've got a couple of 
questions on the launcher. Is this the appropriate mailing list?

- For Linux/Motif the J9 arguments are hardcoded  in eclipseMotif.c.  The 
arguments are different in the newest J9 release so the launcher doesn't 
work with the new J9. Should I open a bug report? If so, which component?

- When bypassing the eclipse executable and running J9 by hand, I can 
launch but I get errors in SWT related to Xt and Xm calls. I believe the 
issue is one I've seen before and it is being caused by SWT picking up 
Lesstif libraries on my machine rather than the correct libXm.so that is 
shipped with eclipse.  When launching with jre I don't see this problem, 
but I can't find anywhere in the launch logic where the launcher sets up 
the enivronment for making this work . I can manually add a LD_PRELOAD  to 

my environment and get it to work, but I'm unsure as to why JRE is working 

and not J9.

Thanks
-Andrew





DJ_Houghton@xxxxxxx
Sent by: eclipse-dev-admin@xxxxxxxxxxx
06/03/2002 09:06 AM
Please respond to eclipse-dev


       To:     eclipse-dev@xxxxxxxxxxx
       cc: 
       Subject:        [eclipse-dev] Running F2 with J9

There is a patch available if you are trying to run build F2 with J9.
It is available off the Platform Core team web page on eclipse.org.
Replace the startup.jar in your installation directory with the folllowing 


jar file.
Sorry for the confusion.

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/downloads/patches/I-20020602/startup.jar
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev



_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev






Back to the top