From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: MessageBundle ???
Date: Mon, 04 Apr 2011 13:09:00 -0000 [thread overview]
Message-ID: <4D99C2EC.3070008@redhat.com> (raw)
In-Reply-To: <2D34830A80A0421D8D670F96FF04818A@e6550>
On 04/04/2011 02:04 PM, dj_def wrote:
>> It should just detect /usr/bin/gcj . What is i686-pc-linux-gnu-gcj doing
>> is
>> /usr/bin anyway?
>
> Yes, in ubuntu /usr/bin/i686-linux-gnu-gcj points to /usr/bin/gcj-x.x where
> x-x is the version. Even /usr/bin/gcj points to /usr/bin/gcj-x.x (so the
> debian update-alternatives script can make you choose among versions simply
> modifying the /usr/bin/gcj link).
> The link I made (i686-pc-linux-gnu-gcj) points to
> /usr/bin/i686-linux-gnu-gcj that points to /usr/bin/gcj-x.x .
>
> A question: especially for prerequisites and dependancies, are there
> specific instructions when cross-compiling for windows? Should I consider
> http://kegel.com/crosstool/ as the main reference?
I can guess, but I don't really know. Windows, thank heaven, is something
I haven't had to touch for a long time.
Andrew.
next prev parent reply other threads:[~2011-04-04 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:04 dj_def
2011-04-04 13:09 ` Andrew Haley [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-04 12:00 dj_def
2011-04-04 12:13 ` Andrew Haley
2011-04-01 14:22 dj_def
2011-04-01 14:57 ` Andrew Haley
2011-04-01 17:43 ` Andrew Haley
2011-04-01 19:32 ` Mark Wielaard
2011-04-04 9:38 ` Andrew Haley
2011-04-01 8:51 dj_def
2011-04-01 9:57 ` Andrew Haley
2011-04-01 10:09 ` Andrew Haley
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=4D99C2EC.3070008@redhat.com \
--to=aph@redhat.com \
--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).