Hey Jesse,
Thanks very much for the detailed post. It seems like you went through a lot
to get GWT up and running on your system. I'm happy that it's finally
working for you.

We'll review the information that you've provided. If others are running
into this problem, it probably makes sense to create a FAQ entry for this
problem.


Rajeev

On Wed, Jun 17, 2009 at 1:17 PM, Jesse Pangburn <[email protected]>wrote:

>
> I had some problems getting hosted mode to work in Eclipse on my FC10
> 64 bit machine, and they are mostly resolved now.  I wanted to post my
> issues here for others.
>
> First, as you may have read, GWT hosted doesn't work in 64 bit java,
> so you need to install 32 bit JDK.  Believe me, I tried to avoid this
> as well, but Google notes that it doesn't work.  So install Sun's 32
> bit JDK on your system.  I made soft links for /usr/java/latest to my
> 64 bit JDK so by default most stuff would still use it.  But in
> Eclipse for your GWT project, set your project's java build path to
> have the 32 bit JDK instead of the 64 bit JDK and then GWT will run in
> 32 bit mode.  To do this, go to Preferences->Java->Installed_JREs and
> add your 32 bit JDK, then for the project go to the build path and
> "add library".  In there you can find "JRE" and choose the 32 bit JDK
> installation.
>
> Starting up the hosted mode will likely fail due to lack of libraries
> on your system with an exception containing some error about failed to
> load library "blahblah.so".  Use yum and keep installing the libraries
> it's asking for until you don't get these anymore.  For example, if
> you don't know what package "blahblah.so" is in (and I often didn't),
> try this:
> locate -b blahblah.so
> This usually works because you typically already have the 64 bit
> versions of most libraries needed.  Having the full path, now do:
> yum provides /usr/lib64/full/path/to/blahblah.so
> It will display the 64 bit package providing this library.  Just use
> the nice package manager GUI to search for that package, and then
> install the 32 bit (i386) version that should be sitting right next to
> it in the list.
> Wash/rinse/repeat until no more library not found errors.
>
> After this though, I only have 64 bit firefox on my system and while
> hosted mode would start and I could point my 64 bit firefox at
> http://localhost:8080/, still the hosted mode embedded browser didn't
> work.  This sucks because it's a lot faster to debug that way,
> ESPECIALLY since the hosted mode then shows the exceptions when you
> make a mistake in the client code with an invalid cast or something.
> The error I got when starting hosted mode was:
> XPCOM error -2147221164
>
> If you google this, you'll find a lot of different answers that worked
> for different people, the problem is typically that they have 32 bit
> only environments and just have some setting screwed up.  In my 64 bit
> environment with 32 bit parts randomly installed, I found some
> comments about XULRunner not being setup right causing this exact
> error so I checked my packages and found that I had the 64 bit version
> of XULRunner but not the 32 bit version.  After installing the 32 bit
> version of xulrunner, now my hosted mode browser starts up and I can
> debug properly.
>
> The only error I get now when the hosted mode browser starts up is an
> ELF error that /home/jpangburn/.mozilla/libflashplayer.so is ELF64,
> because it's a 32 bit hosted browser looking in my user plugins
> directory and finding my 64 bit flash plugin for my 64 bit firefox.
> Unless you have flash in your GWT apps that you want to test in hosted
> mode, if you get that error still- I suggest ignoring it like I'm
> doing.
>
> Hope this helps someone else!
> Jesse
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to