From: Me Myself and I <stargate7thsymbol@live.co.uk>
To: <gcc-help@gcc.gnu.org>, <java@gcc.gnu.org>
Subject: Question about Question.
Date: Thu, 19 Apr 2012 05:46:00 -0000 [thread overview]
Message-ID: <BAY147-W65904817FE23F6DADD737D03D0@phx.gbl> (raw)
I have the feelilng that someone has forgotten to look at my questions.
Is there anyone who can tell me how to make the GCJ behave a little better for me?
Am running GCJ on cygwin Windows 7.
I have a few compiler errors I can't figure out.
//---------------------------------------------------------------------------------------
ImagePixels.java:103: error: JuniorJPanel cannot be resolved to a type
JuniorJPanel contentPanel = new JuniorJPanel(getColoredImage(Color.BLACK,300,300));
^^^^^^^^^^^^
//---------------------------------------------------------------------------------------
This is a fabricated java class in one directory.
-How do I specify a new CLASSPATH statement under /etc/profile so that GCJ will see my
fabricated classes in a directory, such that I will not have to specify further
specific information for each class and that neighbouring classes will be detected?
-If I have extra java lib jar files I want import statements to detect, what do
I do so that the gcj will recognise them when compiling?
-I find also that my windows executable generated by my cygwin run GCJ
requires cygwin1.dll to work. Is there a way to avoid needing a seperate file
at all? Is there an option to build this file into my generated executable?
next reply other threads:[~2012-04-19 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 5:46 Me Myself and I [this message]
2012-04-19 8:38 ` Jonathan Wakely
2012-04-19 10:54 ` Brian Jones
2012-04-19 23:53 ` Ian Lance Taylor
2012-04-20 0:20 ` Jonathan Wakely
2012-04-20 7:36 ` Chris Burdess
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=BAY147-W65904817FE23F6DADD737D03D0@phx.gbl \
--to=stargate7thsymbol@live.co.uk \
--cc=gcc-help@gcc.gnu.org \
--cc=java@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).