public inbox for
 help / color / mirror / Atom feed
From: Andrew Haley <>
Subject: Re: MessageBundle ???
Date: Mon, 04 Apr 2011 12:13:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <9F062AC5F5744F97B7D244509DC9DE28@e6550>

On 04/04/2011 01:00 PM, dj_def wrote:
> I did other tests: I compiled gcc-4.3.0 (with 4.6 and 4.7 I was unable to 
> compile because of libltdl errors and missing jvm.exe) correcting 
> and with --enable-maintainer-mode.
> To make it succesfully I had to
> 1) sudo ln -sf /usr/bin/i686-linux-gnu-gcj /usr/bin/i686-pc-linux-gnu-gcj
> (I did this because during some gcc configuration process, it detects 
> /usr/bin/i686-pc-linux-gnu-gcj instead of /usr/bin/i686-linux-gnu-gcj...
> it could be some ubuntu packaging issue as before compiling I installed the 
> whole gcc ubuntu package...)

It should just detect /usr/bin/gcj .  What is i686-pc-linux-gnu-gcj doing is
/usr/bin anyway?

> 2) gcj 
> /pathToSrcDir/gcc-4.3.0/ecj.jar -findirect-dispatch --main=org.eclipse.jdt.internal.compiler.batch.GCCMain 
>  -o ~/moveinecj1
>    sudo mv ~/moveinecj1 /usr/bin/ecj1
>    sudo chmod +x /usr/bin/ecj1
> (this should be a known issue when cross-compiling)

I don't quite see what the problem is here.  Yes, you have to have ecj1
to build with --enable-java-maintainer-mode.

> Well... with this version there is not any " 
> missing resource problem" but the previous problem is not completely solved:
> class Test {
>   public static void main(String argv[]) {
>     System.out.printf("%09.3f%n",3.1415926535);
>   }
> }

> this time the program does not crash but also does not print anything (it 
> could be normal as now it uses parseInt).

I already said, I think.  Formatted floating-point output has not been written.


  reply	other threads:[~2011-04-04 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 12:00 dj_def
2011-04-04 12:13 ` Andrew Haley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-04 13:04 dj_def
2011-04-04 13:09 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).