public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10053: weak declaration must precede definition errors on OSF 4.0d in libsupc++
Date: Thu, 13 Mar 2003 05:26:00 -0000	[thread overview]
Message-ID: <20030313052601.21669.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10053; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: tilps@hotmail.com
Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/10053: weak declaration must precede definition errors on OSF 4.0d in libsupc++
Date: Wed, 12 Mar 2003 21:22:45 -0800

 This is also happening on i686-unknown-openbsd3.1, the last time I  
 could bootstrap was on March 9 (midnight eastern time) so something  
 after that caused this:
 /export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/gcc/xgcc  
 -shared-libgcc  
 -B/export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/gcc/ -nostdinc++  
 -L/export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/i686-unknown- 
 openbsd3.1/fpic/libstdc++-v3/src  
 -L/export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/i686-unknown- 
 openbsd3.1/fpic/libstdc++-v3/src/.libs  
 -B/home/gates/pinskia/openbsd/i686-unknown-openbsd3.1/bin/  
 -B/home/gates/pinskia/openbsd/i686-unknown-openbsd3.1/lib/ -isystem  
 /home/gates/pinskia/openbsd/i686-unknown-openbsd3.1/include -isystem  
 /home/gates/pinskia/openbsd/i686-unknown-openbsd3.1/sys-include -fpic  
 -I/home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/../gcc  
 -I/home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/../include  
 -I/export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/i686-unknown- 
 openbsd3.1/fpic/libstdc++-v3/include/i686-unknown-openbsd3.1  
 -I/export/gates/pinskia/src/gnu/gcc/src/objdir.openbsd/i686-unknown- 
 openbsd3.1/fpic/libstdc++-v3/include  
 -I/home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/libsupc++ -O2 -g -O2  
 -g -O2 -fpic -fno-implicit-templates -Wall -Wno-format -W  
 -Wwrite-strings -Winline -fdiagnostics-show-location=once -c  
 /home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/libsupc++/ 
 eh_aux_runtime.cc  -fPIC -DPIC -o eh_aux_runtime.o
 /home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/libsupc++/ 
 eh_aux_runtime.cc:42: error: weak
     declaration of `std::exception::exception(const std::exception&)'  
 must
     precede definition
 /home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/libsupc++/ 
 eh_aux_runtime.cc:42: error: weak
     declaration of `std::bad_cast::bad_cast(const std::bad_cast&)' must  
 precede
     definition
 /home/gates/pinskia/src/gnu/gcc/src/libstdc++-v3/libsupc++/ 
 eh_aux_runtime.cc:52: error: weak
     declaration of `std::bad_typeid::bad_typeid(const std::bad_typeid&)'  
 must
     precede definition
 gmake[7]: *** [eh_aux_runtime.lo] Error 1
 
 Thanks,
 Andrew Pinski
 


             reply	other threads:[~2003-03-13  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  5:26 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-06 23:30 billingd
2003-04-05  4:06 billingd
2003-03-13  5:26 Billinghurst, David (CRTS)
2003-03-13  5:16 tilps

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=20030313052601.21669.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).