Hi all,
I have been having a very strange problem that I have tracked down to
libtool, and I don't know how to proceed.
I have a Solaris v2.8 machine with a system installed copy of gcc v3.4.2
in /usr/local. Recently a private copy of gcc v4.0.1 was installed in a
private directory. The private d
Graham Leggett said:
> What method needs to be used to tell libtool to link to stdc++ that
> belongs to the compiler being run?
As was pointed out in a followup message (I deleted the message by
accident, sorry!), it should not be necessary to explicitly link to the
stdc++ library, h
Kurt Roeckx said:
> Are you sure your libtool has been regenerated for the new g++?
I rebuilt libtool v1.5.8 which was previously installed, and when this
made no difference I downloaded and built libtool v1.5.18.
I deleted config.guess, config.sub, libtool and ltmain.sh and recreated
them from
Peter O'Gorman said:
> It could be coming from an already installed .la file.
I did a complete machine grep. The only references to libstdc++ within an
.la file on this machine are in libstdc++.la itself, or in the .la files
of the two projects.
libstdc++ is not found in any other .la file on th
Hi all,
While attempting to build two C++ library projects A and B, on a Solaris
v2.8 environment with gcc v4.0.1 (in a private directory) and gcc v3.4.2
(in /usr/local) both installed in the path, and with gcc v4.0.1 taking
precedance, libtool pulls in either the v3.4.2 stdc++, or the v4.0.1
stdc
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configur
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configur
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configu
Hi all,
I have found the reason for libtool linking to the wrong stdc++, the
problem is that I don't know libtool well enough to propose the "right"
solution.
The problem plays out like this:
- The stdc++ library is added to the "postdeps" environment variable, like
this:
postdeps="-lstdc++ -lm
