[Slackbuilds-users] [FIX] Eclipse + xulrunner issue.
Bradley D. Thornton
Bradley at NorthTech.US
Fri May 13 07:00:42 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hey Thanks Antonio :)
There's my fix, with no kludges ;)
I'll get right on it.
On 05/12/2011 08:58 PM, Antonio Hernández Blas wrote:
> On Sun, May 1, 2011 at 2:00 AM, Bradley D. Thornton
> <Bradley at northtech.us> wrote:
> Hi Bradley:
> I've just took my time to search more about this issue and i conclude
> that actually it's not an eclipse bug, but rather the problem exists
> in the way xulrunner is builded.
> First, Eclipse's SWT Browser (it's internal web browser) uses
> xulrunner depending in its version , so the current Eclipse 3.6.x
> requires XULRunner 1.8.x - 1.9.2.x.
> And second, SWT can use xulrunner *just* if this was builded without
> it's optimization flag  and i have seen that Alien Bob's one 
> (SBo also ) uses "--enable-optimize="$CFLAGS" \"
> According with Grant Gayed it's really important to build xulrunner
> without the use of "--enable-optimize"  to get a functional eclipse
> browser (swt+xulrunner) both in x86 and x86_64. Also he makes another
> important question, ¿which platform of jre (and i add jdk) you use? If
> you use eclipse x86_64, then it would search for a jre/jdk x86_64 and
> a xulrunner x86_64. Important to know to avoid issues between them
>  http://www.eclipse.org/swt/faq.php#browserlinux
>  http://dev.eclipse.org/mhonarc/lists/platform-swt-dev/msg06874.html
>  http://connie.slackware.com/~alien/slackbuilds/xulrunner/build/xulrunner.SlackBuild
>  http://slackbuilds.org/slackbuilds/13.37/libraries/xulrunner/xulrunner.SlackBuild
>  http://web.archiveorange.com/archive/v/rtUM3C62ZOKbXX0i2y9A
>  http://ubuntuforums.org/showthread.php?t=1263776
>  http://blog.javaee.cz/2009/11/ubuntu-910-64bit-and-custom-32bit-jdk.html
>> When eclipse 3.6.1 hit, I went and installed it as soon as I could, long
>> before the warning notice in the README for the Slackbuild. I even
>> submitted a bug report to Eclipse, and got one response, several months
>> later asking a couple of questions that led nowhere.
>> It seems they're clueless over at Eclipse to this bug, and my ticket is
>> still open after all these months.
>> Maybe when the next version is released their bug will be fixed?
> Actually i think that they know about this "bug", but its not in their
> hands to decide how a linux distribution builds xulrunner.
>> For the time being, Eclipse 3.6.0 works fine, so my recommendation at
>> this time, for people running Slackware64, is to avoid installing 3.6.1
>> since this bug has not been addressed, and none of the kludges to fix it
>> seem to apply for 64bit OS.
>> I'd be interested in hearing other perspectives.
> I've already send an eclipse SlackBuild update for version 3.6.2 to
> André Barboza (the current maintainer) but i have not the
> time-platform to test if its true what Grant Gayed stated in his
> posts. If someone can make some test in this aspect could be very
> helpful to "fix" this situation. Just build xulrunner *without* the
> use of "--enable-optimize" (or "--disable-optimize" if applies) and
> let eclipse decides the use of uxlrunner *without* your meddling
> . And yes... i think that André Barboza solution (patch) its
> not the correct answer but maybe i could be wrong ;-)
>  http://www.eclipse.org/swt/faq.php#specifyxulrunner
>  http://www.eclipse.org/swt/faq.php#howdetectmozilla
>  http://www.eclipse.org/swt/faq.php#printmozillapath
Bradley D. Thornton
Manager Network Services
TEL: +1.760.666.2703 (US)
TEL: +44.203.318.2755 (UK)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Find this cert at x-hkp://pool.sks-keyservers.net
-----END PGP SIGNATURE-----
More information about the SlackBuilds-users