public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "smith_winston_6079 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/58284] New: Compiling jvgenmain failes with lots of "undefined reference" errors Date: Fri, 30 Aug 2013 16:08:00 -0000 [thread overview] Message-ID: <bug-58284-8172@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58284 Bug ID: 58284 Summary: Compiling jvgenmain failes with lots of "undefined reference" errors Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java Assignee: unassigned at gcc dot gnu.org Reporter: smith_winston_6079 at hotmail dot com I am compiling gcc-4.7.2 with the following configuration: $ /root/tmp/gcc-4.7.2/configure --prefix=/usr/ --with-local-prefix=/usr/local/ --with-native-system-header-dir=/usr/include/ --enable-libada --enable-libssp --enable-libquadmath --enable-libgcj --enable-nls --with-included-gettext --enable-fixed-point --enable-shared --enable-threads --enable-bootstrap --enable-languages=all,ada,go,obj-c++ --enable-stage1-languages=all --enable-werror --enable-checking=all --enable-stage1-checking=all --enable-gather-detailed-mem-stats --enable-libgcj-debug I am getting the following error when compiling jvgenmain: make[3]: Entering directory `/home/_/gcc-4.7.2-build/gcc' rm -f jvgenmain gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -fno-common -DHAVE_CONFIG_H -o jvgenmain java/jvgenmain.o java/mangle_name.o \ libcommon.a ../libcpp/libcpp.a ./../intl/libintl.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a java/jvgenmain.o: In function `VEC_tree_base_last': /root/tmp/gcc-4.7.2/gcc/vecir.h:28: undefined reference to `vec_assert_fail' java/jvgenmain.o: In function `VEC_tree_base_index': /root/tmp/gcc-4.7.2/gcc/vecir.h:28: undefined reference to `vec_assert_fail' java/jvgenmain.o: In function `VEC_tree_base_space': /root/tmp/gcc-4.7.2/gcc/vecir.h:28: undefined reference to `vec_assert_fail' java/jvgenmain.o: In function `VEC_tree_base_splice': /root/tmp/gcc-4.7.2/gcc/vecir.h:28: undefined reference to `vec_assert_fail' java/jvgenmain.o: In function `VEC_tree_base_quick_push': /root/tmp/gcc-4.7.2/gcc/vecir.h:28: undefined reference to `vec_assert_fail' java/jvgenmain.o:/root/tmp/gcc-4.7.2/gcc/vecir.h:28: more undefined references to `vec_assert_fail' follow java/jvgenmain.o: In function `VEC_tree_gc_alloc': /root/tmp/gcc-4.7.2/gcc/vecir.h:29: undefined reference to `vec_gc_p_reserve_exact' ... <lots of such errors, omitted for brevity> java/mangle_name.o: In function `VEC_method_entry_gc_safe_grow': /root/tmp/gcc-4.7.2/gcc/java/java-tree.h:873: undefined reference to `vec_assert_fail' collect2: ld returned 1 exit status make[3]: *** [jvgenmain] Error 1 make[3]: Leaving directory `/home/_/gcc-4.7.2-build/gcc' make[2]: *** [all-stage1-gcc] Error 2 make[2]: Leaving directory `/home/_/gcc-4.7.2-build' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/home/_/gcc-4.7.2-build' make: *** [all] Error 2 Is there anything wrong with the configure arguments that could cause this (I have scanned through the INSTALL directory html pages and could not find anything)? Googling does not seem to help either. One thing to mention: I am building in a directory in /root/tmp/gcc-4.7.2-build which lives on /, but there wasn't enough free space in that partition, so I symlinked it to /home/_/gcc-4.7.2-build/ (which lives on a different partition). Could this cause the issue? Thanks.
next reply other threads:[~2013-08-30 16:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-30 16:08 smith_winston_6079 at hotmail dot com [this message] 2013-08-31 9:45 ` [Bug java/58284] " smith_winston_6079 at hotmail dot com 2013-09-01 9:49 ` smith_winston_6079 at hotmail dot com 2013-09-01 18:03 ` pinskia at gcc dot gnu.org 2013-09-02 13:10 ` smith_winston_6079 at hotmail 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-58284-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: 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).