public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jason.vas.dias at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/49077] gcjwebplugin.cc doesn't compile against latest xulrunner 2.0 (firefox-3.6) sdk
Date: Fri, 20 May 2011 13:15:00 -0000 [thread overview]
Message-ID: <bug-49077-8172-mOKD8o9I6b@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49077-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49077
--- Comment #5 from Jason Vas Dias <jason.vas.dias at gmail dot com> 2011-05-20 12:56:44 UTC ---
(In reply to comment #3)
> gcjwebplugin is dead, it should have been removed, but nobody has done that.
> Just don't enable it in configure.
Well then what replaces the Firefox plugin functionality - ie.
what happens when I include '--enable-browser-plugin' in configure args ?
A JVM environment and Java SDK is hardly worthy of the name unless it
can be used to run java applets embedded in webpages from the system
browser - how else is one meant to do this using only GCJ components ?
This problem appears to be the ONLY reason gcjwebplugin fails to build ;
are you sure rumors of its demise are not premature ?
next prev parent reply other threads:[~2011-05-20 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-49077-8172@http.gcc.gnu.org/bugzilla/>
2011-05-20 10:39 ` [Bug java/49077] gcjwebplugin.cc doesn't compile against latest xulrunner 2.0b13 sdk jason.vas.dias at gmail dot com
2011-05-20 10:47 ` jason.vas.dias at gmail dot com
2011-05-20 11:16 ` [Bug java/49077] gcjwebplugin.cc doesn't compile against latest xulrunner 2.0 (firefox-3.6) sdk jakub at gcc dot gnu.org
2011-05-20 13:15 ` jason.vas.dias at gmail dot com [this message]
2011-05-20 13:32 ` jakub at gcc dot gnu.org
2011-05-20 13:53 ` gnu_andrew at member dot fsf.org
2011-05-20 19:18 ` jason.vas.dias at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-49077-8172-mOKD8o9I6b@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).