public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: Linking problems in latest cvs deck.
       [not found] <200009251744.NAA08728@mal-ach.watson.ibm.com>
@ 2000-09-25 11:25 ` Benjamin Scherrey
  0 siblings, 0 replies; 3+ messages in thread
From: Benjamin Scherrey @ 2000-09-25 11:25 UTC (permalink / raw)
  To: David Edelsohn; +Cc: gcc

	I compiled everything with a 'make bootstrap' which builds the
libraries as well. That's very odd that the 2.95 would have worked,
then. I presume I was building 2.96 with the 2.95 compiler but then
shouldn't the bootstrapped 2.96 be building the standard libraries? Do I
need to build everything again *after* performing a 'make install' on
the 2.96?

	thanx & later,

		Ben Scherrey

David Edelsohn wrote:
> 
>         Did you compile the libraries with gcc-2.95 or CVS gcc-2.96?  The
> C++ name mangling has changed, so the compiler version used to build the
> library needs to match the compiler version building an application.
> 
> David

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Linking problems in latest cvs deck.
@ 2000-09-25 12:04 Benjamin Kosnik
  0 siblings, 0 replies; 3+ messages in thread
From: Benjamin Kosnik @ 2000-09-25 12:04 UTC (permalink / raw)
  To: gcc

I've been unable to reproduce this problem for over a week. Can you
please read this documentation about configuring and building?

http://sources.redhat.com/libstdc++/install.html


Our configure lines are a bit different, but I don't expect this is
the root cause of your problem.

from my config.status file:
/mnt/hd/bliss/src.gcc/configure
--with-gcc-version-trigger=/mnt/hd/bliss/src.gcc/gcc/version.c
--host=i686-pc-linux-gnu --verbose --prefix=/mnt/hd/bliss/H-x86-gcc-3
--enable-debug --enable-libstdcxx-v3 --enable-cshadow-headers
--enable-threads=posix --enable-languages=c,c++ --norecursion

If you can pass 'g++ -v' to your built compiler, you can see what
directories are being searched for the libstdc++ library. You might
want to use nm to look at this binary, and see if it has some of the
basic symbols, such as

std:cout

ie:

%nm -A libstdc++.a | grep cout
libstdc++.a:ios.o:         U _3std.cout
libstdc++.a:ios.o:         U _3std.wcout
libstdc++.a:stdstreams.o:00000140 B _3std.cout
libstdc++.a:stdstreams.o:00000460 B _3std.wcout

%nm -A --demangle libstdc++.a | grep cout
libstdc++.a:ios.o:         U std::cout
libstdc++.a:ios.o:         U std::wcout
libstdc++.a:stdstreams.o:00000140 B std::cout
libstdc++.a:stdstreams.o:00000460 B std::wcout


best,
benjamin

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Linking problems in latest cvs deck.
@ 2000-09-25 10:42 Benjamin Scherrey
  0 siblings, 0 replies; 3+ messages in thread
From: Benjamin Scherrey @ 2000-09-25 10:42 UTC (permalink / raw)
  To: gcc

	I recently posted a message describing the inability to link anything
with the new libstdcxx-v3 in the latest cvs code. I just updated my code
and get the same results. My platform is i686 Linux 2.2.13. I'm
configured with '--enable-shared --enable-libstdcxx-v3
--enable-languages=cxx --enable-threads'. Am I the only one getting
these results? Interesting thing is that when I reinstall my gcc-2.95.2
code, its able to link to these libraries! What gives?

	thanx & later,

		Ben Scherrey

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-09-25 12:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <200009251744.NAA08728@mal-ach.watson.ibm.com>
2000-09-25 11:25 ` Linking problems in latest cvs deck Benjamin Scherrey
2000-09-25 12:04 Benjamin Kosnik
  -- strict thread matches above, loose matches on Subject: below --
2000-09-25 10:42 Benjamin Scherrey

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).