This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH RFA: Build system: Check for -static-libstdc++


Richard Guenther <richard.guenther@gmail.com> writes:

> Can we at least have the option to link the stage1 go1 binary (or whatever
> it is called) dynamically against the just built libstdc++ please?  It would
> be very annoying to have statically linked libstdc++ from a distributors
> point of view.

I assume you mean the stage2/3 go1 binary.

I can add a configure option for this, but it will be independent of
this patch.  This patch just checks whether -static-libstdc++ is
available, and so, in effect, would set the default for the configure
option.  The configure option would be a different patch.

We already have three configure options along these lines:
--with-host-libstdcxx, --with-boot-ldflags, and --with-boot-libs.
Currently when none of these options are used, and
--enable-build-with-cxx is used, the default for --with-boot-ldflags is
-static-libstdc++ -static-libgcc.  The only difference here is that go1
is always built using C++.  But perhaps these options suffice, and we
can just tweak them a bit to set the default for go1 when they are not
used.  In fact, that seems fine to me, as just setting them to any value
would be enough to avoid the default.


Anyhow, is this patch OK for mainline?
    http://gcc.gnu.org/ml/gcc-patches/2010-11/msg00239.html

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]