public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zclai at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67067] "Trouble closing elf file" and "-static-libstdc++ not implemented" Date: Sat, 01 Aug 2015 03:28:00 -0000 [thread overview] Message-ID: <bug-67067-4-epMJdBkruj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67067-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67067 --- Comment #4 from Alex Lai <zclai at yahoo dot com> --- (In reply to Alex Lai from comment #1) > on Solaris x86, I downloaded MPC, GMP and MPFR and extracted them into GCC > source directory as mpc,gmp and mpfr directories and configure GCC source > with: > > $ ../gcc-5.2.0.src/configure --prefix=$HOME/gcc-5.2.0 > --enable-languages=c,c++ > $ gmake > > I got the following error: > > Assembler: optimize.c > "/var/tmp//ccMndPR3.s", line 85111 : Trouble closing elf file > gmake[3]: *** [cp/optimize.o] Error 1 > > > The file mentioned in the error message doesn’t exist. > > $ ls -l "/var/tmp//ccEtAJ5n.s" > /var/tmp//ccEtAJ5n.s: No such file or directory > > The file system has plenty of room: > > $ df -h /var/tmp > Filesystem size used avail capacity Mounted on > /dev/dsk/c0t0d0s6 99G 27G 71G 28% /var > > $ uname -a > SunOS sbdsvrwm566 5.10 Generic_150401-20 i86pc i386 i86pc > > > the only error message in config.log is as follows: > > configure:5091: g++ -o conftest -g -O2 -static-libstdc++ -static-libgcc > conftest.cpp >&5 > g++: unrecognized option `-static-libstdc++' > conftest.cpp:11:2: #error -static-libstdc++ not implemented > configure:5091: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "" > | #define PACKAGE_TARNAME "" > | #define PACKAGE_VERSION "" > | #define PACKAGE_STRING "" > | #define PACKAGE_BUGREPORT "" > | #define PACKAGE_URL "" > | /* end confdefs.h. */ > | > | #if (__GNUC__ < 4) || (__GNUC__ == 4 && __GNUC_MINOR__ < 5) > | #error -static-libstdc++ not implemented > | #endif > | int main() {} > > > the lib exists and its path is included in lib search path: > > $ ls -l /usr/local/lib/libstdc++.so > lrwxrwxrwx 1 root root 18 May 31 2012 > /usr/local/lib/libstdc++.so -> libstdc++.so.6.0.3 > $ echo $LD_LIBRARY_PATH > /opt/SUNWspro11/SUNWspro/prod/lib:/usr/local/lib:/usr/lib:/usr/lib/X11 > > > the error apparently is due to the missing space between -static and > -libstdc++. however,none of the mentioned confdefs.h conftest.cpp exist > either under the source or build directory or installed packages. > > obviously the older gcc was used to compile the new gcc: > > configure:4074: checking for gcc > configure:4090: found /usr/sfw/bin/gcc > configure:4101: result: gcc > configure:4330: checking for C compiler version > configure:4339: gcc --version >&5 > gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) > Copyright (C) 2004 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > $ echo $PATH > /usr/ccs/bin:/usr/bin:/usr/sfw/bin:/usr/sbin:/usr/local/bin:/opt/SUNWspro/ > bin:/bin:/usr/bin:/usr/sbin:/usr/ucb:/bns/bin:/usr/openwin/bin: such issue doesn't appear if I compile gmp, mpfr and mpc separately before compiling gcc. >From gcc-bugs-return-493866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Aug 01 06:11:27 2015 Return-Path: <gcc-bugs-return-493866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 100887 invoked by alias); 1 Aug 2015 06:11:26 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 100865 invoked by uid 48); 1 Aug 2015 06:11:22 -0000 From: "chengniansun at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/67088] New: Incorrect location of error on invalid type used in bit-field declaration Date: Sat, 01 Aug 2015 06:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: chengniansun at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: <bug-67088-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-08/txt/msg00008.txt.bz2 Content-length: 1524 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67088 Bug ID: 67088 Summary: Incorrect location of error on invalid type used in bit-field declaration Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: chengniansun at gmail dot com Target Milestone: --- I define a struct with a bit field but declare it as "double". Gcc emits an error on it but point to the start of the line, not the location of this attribution declaration. $: cat t.c struct S { double d; double s:1; }; $: gcc-trunk -c t.c t.c:2:3: error: bit-field ‘s’ has invalid type double d; double s:1; ^ $: clang-trunk -c t.c t.c:2:20: error: bit-field 's' has non-integral type 'double' double d; double s:1; ^ ~ 1 error generated. $: gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/6.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --enable-languages=c,c++,objc,obj-c++,fortran,lto --disable-werror --with-gmp=/usr/local/gcc-trunk --with-mpfr=/usr/local/gcc-trunk --with-mpc=/usr/local/gcc-trunk --with-cloog=/usr/local/gcc-trunk --prefix=/usr/local/gcc-trunk Thread model: posix gcc version 6.0.0 20150731 (experimental) [trunk revision 226431] (GCC) $: >From gcc-bugs-return-493867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Aug 01 07:24:32 2015 Return-Path: <gcc-bugs-return-493867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 88207 invoked by alias); 1 Aug 2015 07:24:31 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 88185 invoked by uid 48); 1 Aug 2015 07:24:28 -0000 From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/67087] FAIL: gcc.dg/cpp/_Pragma3.c (test for excess errors) - file timestamp issue Date: Sat, 01 Aug 2015 07:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-67087-4-RgoJdg3qj7@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67087-4@http.gcc.gnu.org/bugzilla/> References: <bug-67087-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-08/txt/msg00009.txt.bz2 Content-length: 495 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg087 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Not a bug, use ./contrib/gcc_update --touch before running the testsuite.
next prev parent reply other threads:[~2015-08-01 3:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-30 15:25 [Bug c++/67067] New: #error -static-libstdc++ not implemented zclai at yahoo dot com 2015-07-30 15:33 ` [Bug c++/67067] "Trouble closing elf file" and "-static-libstdc++ not implemented" zclai at yahoo dot com 2015-07-30 17:07 ` redi at gcc dot gnu.org 2015-07-30 19:36 ` zclai at yahoo dot com 2015-08-01 3:28 ` zclai at yahoo dot com [this message] 2024-01-24 10:31 ` [Bug bootstrap/67067] " redi at gcc dot gnu.org 2024-01-24 13:15 ` ro at gcc dot gnu.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=bug-67067-4-epMJdBkruj@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: 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).