Hello, I am in the process of trying to install the PCRE library. I run the
configure command with the various options, and I then run the make command,
and this is when I get the error, "warning: file /usr/sfw/lib/libstdc++.so:
attempted multiple inclusion of file". I am on a Solaris 10 oper
On Tue, 24 Apr 2012, Gray, Steve, Wipro wrote:
Hello, I am in the process of trying to install the PCRE library. I run the
configure command with the various
options, and I then run the make command, and this is when I get the error,
“warning: file
/usr/sfw/lib/libstdc++.so: attempted multipl
Steve,
Find out what the path for libstdc++.so is for the one you want,
then set LDFLAGS=-L/correct/path/ when you build the library that it's
complaining about.
Note that it may not be PCRE, but it could be something that PCRE links to.
Use "ldd" or "ldd -s" to find out which libraries are pul
On Tue, 24 Apr 2012, Robert Boehne wrote:
Steve,
Find out what the path for libstdc++.so is for the one you want,
then set LDFLAGS=-L/correct/path/ when you build the library that it's
complaining about.
Note that it may not be PCRE, but it could be something that PCRE links to.
Use "ldd" o
Bob - correct on all counts :)
It can be problematic though, even when the two libstdc++.so files are
symlinks or otherwise identical. If you provide libstdc++.so in a "runtime
only" package, you don't want the compiler's location to be hardcoded. The
fix is to simply force a particular path wit
Bob,
I was expecting some type of a completion message at the end of the make
command. I did not image that this was the end of the make command and that I
could continue. I never tried to continue. Now that you told me that is just
a warning and not an error, I proceeded to run the "make ch
In my configure statement I have "LDFLAGS="-L/usr/sfw/lib -R/usr/sfw/lib"
I run the configure command with this option and I run the make command and I
still get the "multiple inclusion of file error"
From: Robert Boehne [mailto:rboe...@gmail.com]
Sent: Tuesday, April 24, 2012 3:12 PM
To: Gray, S
Run ldd -s on the resulting shared librry that generates the error.
It should show libstdc++.so coming from two different paths, and will also
show which share library each one is coming from.
I suspect that one of them is hardcoded in a file you're linking to (not
specified on your link line).
Ro
