public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "lucier at math dot purdue dot edu" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/32010] New: bootstrap fails; chooses wrong zlib for building jc1 Date: Sun, 20 May 2007 16:41:00 -0000 [thread overview] Message-ID: <bug-32010-271@http.gcc.gnu.org/bugzilla/> (raw) Configured with env CC=/pkgs/gcc-4.2.0-64/bin/gcc ../4.2.0/configure --build=powerpc64-apple-darwin8.8.0 --host=powerpc64-apple-darwin8.8.0 --target=powerpc64-apple-darwin8.8.0 --with-gmp=/pkgs/gmp-4.2.1-64/ --with-mpfr=/pkgs/gmp-4.2.1-64/ --prefix=/pkgs/gcc-4.2.0-64 and made with make bootstrap. Bootstrap fails win stage2 with /Users/gcc-test/programs/gcc/objdir-gcc-4.2.0/./prev-gcc/xgcc -B/Users/gcc-test/programs/gcc/objdir-gcc-4.2.0/./prev-gcc/ -B/pkgs/gcc-4.2.0-64/powerpc64-apple-darwin8.8.0/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -o jc1 \ java/parse.o java/class.o java/decl.o java/expr.o java/constants.o java/lang.o java/typeck.o java/except.o java/verify-glue.o java/verify-impl.o java/zextract.o java/jcf-io.o java/win32-host.o java/jcf-parse.o java/mangle.o java/mangle_name.o java/builtins.o java/resource.o java/jcf-write.o java/buffer.o java/check-init.o java/jcf-depend.o java/jcf-path.o java/boehm.o java/java-gimplify.o main.o libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a -L../zlib -lz ../libcpp/libcpp.a ./../intl/libintl.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a ld64 warning: in /usr/lib/libz.dylib, file is not of required architecture Undefined symbols: _inflateEnd, referenced from: _read_zip_member in jcf-io.o _inflate, referenced from: _read_zip_member in jcf-io.o _inflateInit2_, referenced from: _read_zip_member in jcf-io.o ld64-62.1 failed: symbol(s) not found collect2: ld returned 1 exit status make[3]: *** [jc1] Error 1 make[2]: *** [all-stage2-gcc] Error 2 make[1]: *** [stage2-bubble] Error 2 make: *** [bootstrap] Error 2 Now, I can't find a bug report for this. I've also bootstrapped the 4.2.0 development branch many times with this configuration; see, e.g., <http://gcc.gnu.org/ml/gcc-testresults/2007-05/msg00727.html> -- Summary: bootstrap fails; chooses wrong zlib for building jc1 Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lucier at math dot purdue dot edu GCC build triplet: powerpc64-apple-darwin8.8.0 GCC host triplet: powerpc64-apple-darwin8.8.0 GCC target triplet: powerpc64-apple-darwin8.8.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32010
next reply other threads:[~2007-05-20 16:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-20 16:41 lucier at math dot purdue dot edu [this message] 2007-05-23 22:11 ` [Bug java/32010] " lucier at math dot purdue dot edu 2007-05-24 1:19 ` lucier at math dot purdue dot edu
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-32010-271@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: linkBe 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).