public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Henning <phenning@cs.uiowa.edu>
To: egcs@cygnus.com
Cc: jason@cygnus.com, law@cygnus.com
Subject: Re: problems with the recent snapshot (971207)
Date: Mon, 08 Dec 1997 15:55:00 -0000	[thread overview]
Message-ID: <199712082343.RAA29705@server.cs.uiowa.edu> (raw)
In-Reply-To: <199712081821.NAA02972@hal.ttlc.net>

I'm refering to egcs-971207 on linux-2.1.71, glibc-2.0.5c with the
following config:

../egcs-971207/configure --host=i686-pc-linux-gnu --prefix=/usr/local/app/egcs --enable-shared --with-gnu-as --with-gnu-ld --norecursion 
# using "../egcs-971207/config/mh-x86pic" and "../egcs-971207/config/mt-x86pic"


I have the same problem the Tudor is having, which appears to be
similar to the problem Jim Peterson was having
(e.g. http://www.cygnus.com/ml/egcs-bugs/1997-Dec/0106.html ).

Essentially, this program won't link:

===
#include <iostream.h>
#include <string>
int main(void) { string s = "Hello, world"; cout << s << endl; return 0; }
===

Just to be sure that I am not running into old C++ libraries, I moved
all the libstc++* and libg++* files (not egcs) to a junk directory and
re-ran ldconfig.  Just to be really-really sure, I renamed
/usr/include/g++ as well.

When I do a "make bootstrap; make -k check", I run into tons of errors
during the g++ tests because ld.so can't find libstd++.so.2.8.0.
Annoying, but fixable.  Re-running "make -k check", I run into the
following failures during libstdc++ check:

Executing on host: /home/phenning/EGCS/Build/build/gcc/xgcc -B/home/phenning/EGCS/Build/build/gcc/ ../../../../egcs-971207/libstdc++/testsuite/libstdc++.tests/../../tests/tstring.cc  -I.. -I../../../../egcs-971207/libstdc++/testsuite/.. -I../../../../egcs-971207/libstdc++/testsuite/../stl -I.   -I/home/phenning/EGCS/Build/egcs-971207/libio -I/home/phenning/EGCS/Build/build/libraries/libio -g -L/home/phenning/EGCS/Build/build/libraries//libstdc++ -lstdc++   -lm  -o /home/phenning/EGCS/Build/build/libraries/libstdc++/testsuite/tstring   
compiler exited with status 1
output is:
/tmp/cca294841.o:/home/phenning/EGCS/Build/build/libraries/libstdc++/testsuite/../../../../egcs-971207/libstdc++/testsuite/../std/bastring.h:148: undefined reference to `ostream & operator<<<char, string_char_traits<char>, __default_alloc_template<false, 0> >(ostream &, basic_string<char, string_char_traits<char>, __default_alloc_template<false, 0> > const &)'
[plus a lot of other similar errors]


so, tstring.cc compilation and tstring.cc -O compilation fail unexpectedly.

What else can I provide to help resolve this?

Cheers,
Paul Henning

  reply	other threads:[~1997-12-08 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-08 11:24 Tudor Hulubei
1997-12-08 15:55 ` Paul Henning [this message]
1997-12-08 17:07   ` H.J. Lu
1997-12-08 20:22     ` problems with the recent snapshot (971207) (Solved) Jody Goldberg
1997-12-09  0:46       ` H.J. Lu
1997-12-09  6:04   ` problems with the recent snapshot (971207) Orn E. Hansen

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=199712082343.RAA29705@server.cs.uiowa.edu \
    --to=phenning@cs.uiowa.edu \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    --cc=law@cygnus.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: 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).