public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "szukw000 at arcor dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/44228]  New: gcc-4.4.0 does not compile gcc-4.5.0
Date: Fri, 21 May 2010 12:42:00 -0000	[thread overview]
Message-ID: <bug-44228-19218@http.gcc.gnu.org/bugzilla/> (raw)

compiled with gcc-4.4.0
-----------------------------------------------------
Makefile.Linux.gcc:
====================
flags=CFLAGS='-march=native -mtune=native'
VERSION=gcc-4.5.0
#
do_configure:
    $(flags) ../$(VERSION)/configure \
    --prefix=/usr/local/$(VERSION) \
    --enable-languages=c,c++,fortran,java,objc,ada \
    --disable-nls \
    --with-x \
    --enable-java-awt=xlib,gtk \
    --enable-shared \
    --enable-threads=posix \
    --enable-stage1-checking

do_compile:
    make bootstrap

-------------------------------------------------
Makefile                  libcpp/                  stage1-i686-pc-linux-gnu/
Makefile.Linux.gcc        libdecnumber/            stage1-intl/
build-i686-pc-linux-gnu/  libiberty/               stage1-libcpp/
compare                   prev-gcc/                stage1-libdecnumber/
config.log                prev-i686-pc-linux-gnu/  stage1-libiberty/
config.status*            prev-intl/               stage1-zlib/
fehler                    prev-libcpp/             stage_current
fixincludes/              prev-libdecnumber/       stage_final
gcc/                      prev-libiberty/          stage_last
gnattools/                prev-zlib/               zlib/
i686-pc-linux-gnu/        serdep.tmp
intl/                     stage1-gcc/
-------------------------------------------------
stage_current: stage3
stage_last: stage3
stage_final: stage3
-------------------------------------------------
As I cannot attach a file:

Makefile:857: warning: overriding commands for target `gjdoc'
Makefile:775: warning: ignoring old commands for target `gjdoc'
Makefile:857: warning: overriding commands for target `gjdoc'
Makefile:775: warning: ignoring old commands for target `gjdoc'
jar: internal error:
java.lang.NullPointerException
   at gnu.classpath.tools.jar.Creator.writeCommandLineEntries(Creator.java:219)
   at gnu.classpath.tools.jar.Creator.run(Creator.java:244)
   at gnu.classpath.tools.jar.Main.run(Main.java:276)
   at gnu.classpath.tools.jar.Main.main(Main.java:284)
make[3]: *** [libgcj-4.5.0.jar] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-target-libjava] Error 2
make: *** [bootstrap] Error 2
----------------------------------------------------
winfried


-- 
           Summary: gcc-4.4.0 does not compile gcc-4.5.0
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: szukw000 at arcor dot de


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


             reply	other threads:[~2010-05-21 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 12:42 szukw000 at arcor dot de [this message]
2010-05-21 12:54 ` [Bug target/44228] gcc-4.5.0 does not bootstrap with -march=native rguenth at gcc dot gnu dot org
2010-05-21 13:10 ` szukw000 at arcor dot de

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-44228-19218@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).