public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "licheng.1212 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/53527] New: 4.7.0 release can't enable java language
Date: Wed, 30 May 2012 10:55:00 -0000	[thread overview]
Message-ID: <bug-53527-8172@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53527

             Bug #: 53527
           Summary: 4.7.0 release can't enable java language
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: java
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: licheng.1212@gmail.com


[licheng@localhost build]$ ../configure --prefix=${PREFIX} --target=${TARGET}
--with-newlib --with-headers=../../newlib-1.20.0/newlib/libc/include/
--with-ar=${PREFIX}/bin/${TARGET}-ar --with-as=${PREFIX}/bin/${TARGET}-as
--with-ld=${PREFIX}/bin/${TARGET}-ld --with-mpfr=${PREFIX} --with-gmp=${PREFIX}
--with-ppl=${PREFIX} --with-cloog=${PREFIX} --with-mpc=${PREFIX}
--enable-languages=c,c++,java --disable-multilib 
--with-gcc-version-trigger=../gcc/version.c --disable-libstdcxx-pch
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... mips-unknown-elf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for libitm support... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gnatbind... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1
$$f2
checking for objdir... .libs
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... yes
checking for PWL_handle_timeout in -lpwl... yes
checking for version 0.11 (revision 0 or later) of PPL... yes
checking for installed CLooG PPL Legacy... PPL Legacy
checking for version 0.15.5 (or later revision) of CLooG... yes
configure: error: 
The following requested languages could not be built: java
Supported languages are: c,c++,fortran,go,lto,objc,obj-c++

gcc 4.4.2 is OK


             reply	other threads:[~2012-05-30 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 10:55 licheng.1212 at gmail dot com [this message]
2012-05-30 11:15 ` [Bug java/53527] " rguenth at gcc dot gnu.org
2012-05-31  3:01 ` licheng.1212 at gmail dot com
2012-05-31  7:37 ` licheng.1212 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-53527-8172@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).