public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gnuteam@kpit.com To: gcc-gnats@gcc.gnu.org Cc: rekhad@kpit.com, aratid@kpit.com Subject: c++/4165: gcc 3.0.1 fails to build on linux for sh-coff,sh-hms for language c++ Date: Wed, 29 Aug 2001 02:36:00 -0000 [thread overview] Message-ID: <20010829093537.25354.qmail@sourceware.cygnus.com> (raw) >Number: 4165 >Category: c++ >Synopsis: gcc 3.0.1 fails to build on linux for sh-coff,sh-hms for language c++ >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Aug 29 02:36:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: self >Release: gcc 3.0.1 >Organization: >Environment: linux Redhat 6.2 >Description: While building the sh-coff & sh-hms tool chain the binutils (2.11.2), gcc core compiler and newlib (1.9.0) got build successfully. The final build for gcc full compiler fails with the following error.... ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:397:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:398:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:399:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:400:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:401:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:402:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:403:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:404:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:405:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:406:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/md5.c:407:7: warning: function-like macro "FI" must be used with arguments in traditional C ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strsignal.c: In function `psignal': ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strsignal.c:599: warning: comparison between signed and unsigned ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strdup.c: In function `strdup': ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strdup.c:5: warning: implicit declaration of function `malloc' ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strdup.c:5: warning: implicit declaration of function `strlen' ../../../../../../fsfsrc/gcc-3.0.1/libiberty/strdup.c:8: warning: implicit declaration of function `strcpy' ../../../../../fsfsrc/gcc-3.0.1/libstdc++-v3/libsupc++/eh_personality.cc: In function `void __cxa_call_unexpected(_Unwind_Exception*)': ../../../../../fsfsrc/gcc-3.0.1/libstdc++-v3/libsupc++/eh_personality.cc:403: warning: new declaration `void __cxa_call_unexpected(_Unwind_Exception*)' ../../../../../fsfsrc/gcc-3.0.1/libstdc++-v3/libsupc++/eh_personality.cc:403: warning: ambiguates built-in declaration `void __cxa_call_unexpected(void*)' /tmp/ccNr8TAE.s: Assembler messages: /tmp/ccNr8TAE.s:555: Error: Rest of line ignored. First ignored character is `<'. make[3]: *** [basic_file.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive-am] Error 2 make: *** [all-target-libstdc++-v3] Error 2 Build for sh-elf tool chain for gcc 3.0.1 is successful. The sh-coff & sh-hms build is successful if the languages specified is only c and not c++. >How-To-Repeat: 1. Build binutils 2.11.2 2. Configure gcc with --enable-languages=c,c++ --target=sh- coff --with-newlib --prefix=/usr/.. make LANGUAGES="c c++" all-gcc make LANGUAGES="c c++" install-gcc 3. Build Newlib 1.9.0 4. Make the final Gcc (Build fail occurs at this stage.) >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-08-29 2:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010829093537.25354.qmail@sourceware.cygnus.com \ --to=gnuteam@kpit.com \ --cc=aratid@kpit.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=rekhad@kpit.com \ /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).