This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
Re: V3 PATCH: Use -rpath, not --rpath, when testing
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: V3 PATCH: Use -rpath, not --rpath, when testing
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Sun, 29 Oct 2000 21:22:01 -0800 (PST)
- cc: aoliva at redhat dot com, gcc-patches at gcc dot gnu dot org, libstdc++ at sources dot redhat dot com
> >> (I don't think we really need *everything* static; just
> >> libstdc++ if that's easy to arrange.)
>
> Alexandre> It isn't, unless you break libtool's encapsulation and
> Alexandre> look for libstdc++.a. I don't see any value in testing
> Alexandre> both static and shared versions; I'd rather just defer
> Alexandre> to whatever choices the builder makes at configure time
> Alexandre> (i.e., --enable or --disable-shared).
>
> Talk it over with Benjamin; I've got no opinion.
No. Strangely enough, we need to test both shared and static as long as
both are built, as sometimes the static and shared have different link
properties. This has been an issue historically, where static binaries
link but shared don't (say, on alpha right now, for instance) -- so we
need this info in the "make check" rule.
-benjamin