public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/38892] gcc 4.4.0 20090104 - natVMVirtualMachine.cc:903: error: request for member 'frame_type' in ... Date: Tue, 27 Jan 2009 15:13:00 -0000 [thread overview] Message-ID: <20090127151345.13475.qmail@sourceware.org> (raw) In-Reply-To: <bug-38892-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rob1weld at aol dot com 2009-01-27 15:13 ------- Same issue on Fedora 10 # ../gcc_build/gcc/xgcc -v Using built-in specs. Target: i386-redhat-linux Configured with: ../gcc_trunk/configure --enable-languages=c,c++,fortran,java,objc,obj-c++ --enable-shared --disable-static --enable-decimal-float --with-long-double-128 --enable-nls --with-included-gettext --disable-gather-detailed-mem-stats --with-stabs --enable-debug --enable-symvers --enable-version-specific-runtime-libs --without-system-zlib --enable-gtk-cairo --enable-gconf-peer --enable-xmlj --enable-gtk-peer --enable-plugin --enable-tool-wrappers --enable-portable-native-sync --enable-hash-synchronization --enable-interpreter --enable-local-sockets --enable-gjdoc --enable-java-awt=gtk,xlib,x --enable-gc-debug --enable-libgcj-debug --enable-objc-gc --disable-concept-checks --enable-libstdcxx-debug --disable-stage1-checking --enable-checking=release --with-tune=k8 --with-cpu=k8 --with-arch=k8 --enable-__cxa_atexit --disable-libunwind-exceptions --disable-dssi --enable-libgcj-multifile --build=i386-redhat-linux --prefix=/mnt/drive2/gcc_test --with-cloog=/usr/local Thread model: posix gcc version 4.4.0 20090126 (experimental) [trunk revision 143680] (GCC) After applying the same fix as used for OpenSolaris the build continued. Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38892
next prev parent reply other threads:[~2009-01-27 15:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-17 4:43 [Bug bootstrap/38892] New: " rob1weld at aol dot com 2009-01-23 22:32 ` [Bug bootstrap/38892] " rob1weld at aol dot com 2009-01-27 15:13 ` rob1weld at aol dot com [this message] 2009-01-30 4:32 ` rob1weld at aol dot com 2009-01-31 14:34 ` rob1weld at aol dot com 2009-04-22 11:21 ` dave dot korn dot cygwin at gmail dot com 2009-04-22 11:22 ` dave dot korn dot cygwin at gmail dot com 2009-04-22 11:25 ` dave dot korn dot cygwin at gmail dot com 2009-04-22 11:35 ` dave dot korn dot cygwin at gmail dot com 2009-04-22 22:38 ` dave dot korn dot cygwin at gmail dot com 2009-08-21 2:20 ` davek at gcc dot gnu dot org 2009-08-21 2:24 ` davek at gcc dot gnu dot org
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=20090127151345.13475.qmail@sourceware.org \ --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: 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).