Should GCC's libsanitizer be expected to build independently
of the rest of GCC?
With a copy of the GCC repository in, say, /src/gcc-trunk,
should I expect to configure and make libsanitizer like so:
$ cd /build/libsanitizer
$ /src/gcc-trunk/libsanitizer/configure && nice make
I ask because the build fails with the error below. The error
indicates that the library assumes that it's being built as
part of GCC, with libstdc++ in the same build tree. (I can
get around the failure by providing the expected libstdc++-v3
directory or a symlink to it).
Other GCC libraries that use libstdc++ (e.g., libitm) don't
make this assumption and build successfully independently
of the rest of a GCC build. I'd like to know if that's by
design (and the assumptions made by libsanitizer are wrong)
or it's just a happenstance than any of them build this way.
libtool: link: cannot find the library
`../../libstdc++-v3/src/libstdc++.la' or unhandled argument
`../../libstdc++-v3/src/libstdc++.la'
make[2]: *** [libasan.la] Error 1
make[2]: Leaving directory `/build/libsanitizer/asan'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/build/libsanitizer'
make: *** [all] Error 2
Thanks
Martin
