public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: MNewcomb@tacintel.com
To: gcc-help@gcc.gnu.org
Subject: RE: execing 'gcc' from within Java application
Date: Tue, 20 Aug 2002 07:16:00 -0000	[thread overview]
Message-ID: <CA3BC0E3B145D611BD0F00104B874267163178@iroquois.tacintel.com> (raw)

Please Help!

> I have a set of classes that use JNI.  I was using make to 
> build them.  I am  switching to Ant.  When Ant (a Java process)
> execs off gcc, gcc totally screws with my JNI code.  It starts
> replacing all my jobject and jstring variables with
> java::lang::Object and java::lang::String.
> 
> It is just happening when I invoke gcc from within ant.  I 
> check the command line from Ant and it's the exact same thing.
>  In fact, I cut and paste from Ant output to an xterm and
> everything compiles fine.
> 
> So, how do I tell gcc to just compile the code?
> 
> Thanks,
> Michael

             reply	other threads:[~2002-08-20 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20  7:16 MNewcomb [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-19 14:15 MNewcomb

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=CA3BC0E3B145D611BD0F00104B874267163178@iroquois.tacintel.com \
    --to=mnewcomb@tacintel.com \
    --cc=gcc-help@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).