This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] build: add -Wl,-rpath=path to $gmplibs (issue 7124057)
- From: minux <minux dot ma at gmail dot com>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: bonzini at gnu dot org, dj at redhat dot com, neroden at gcc dot gnu dot org, aoliva at redhat dot com, ralf dot wildenhues at gmx dot de, gcc-patches at gcc dot gnu dot org, iant at google dot com, reply at codereview-hr dot appspotmail dot com
- Date: Fri, 18 Jan 2013 04:05:31 +0800
- Subject: Re: [PATCH] build: add -Wl,-rpath=path to $gmplibs (issue 7124057)
- References: <047d7b6d7cc0187e9504d380c271@google.com> <1D7AE1A7-FC66-42BD-AD33-09F9B6826A45@comcast.net>
On Fri, Jan 18, 2013 at 3:39 AM, Mike Stump <mikestump@comcast.net> wrote:
> On Jan 17, 2013, at 11:11 AM, minux.ma@gmail.com wrote:
>> some systems (notably NetBSD), doesn't place the path where libgmp,
>
> I think gcc should try and build and run a gmp program and fail to configure if the binary can't also run. This prevents configuring and building on such a system. The gcc directions for building gmp and friends should say that they must be configured and built with --disable-shared --enable-static if the user doesn't have the installed lib directory in their environment.
any opinions on this? this is very easy to implement with AC_TRY_RUN and
at least it will make the problem turn up early instead of when it's about to
configure libgcc (with the confusing error "gcc not able to compile").
of course, i will exclude the case when we're cross compiling gcc.
I'm happy to leave the problem of setting -rpath to pkgsrc maintainers
as I just want to do a full gcc bootstrap to test another libgcc patch.