From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org, jemarch@gnu.org
Subject: Re: libgmp: link to the correct shared library
Date: Fri, 24 Jul 2020 02:00:24 +0200 [thread overview]
Message-ID: <8009390.Ai7DkcWk9P@omega> (raw)
In-Reply-To: <18e0dcb5-556d-9601-ff4f-d3e610234b99@cs.ucla.edu>
Hi Paul,
> > Also, adding -Wl,-rpath=/PREFIX64/lib to LDFLAGS will have ill consequences
> > when the package contains shared libraries and uses libtool to create them. See
> > <https://lists.gnu.org/archive/html/bug-gnulib/2020-05/msg00102.html>.
>
> That's OK too, since Emacs and coreutils don't use libtool to create packages.
GNU poke is likely to use GMP soon. When it does that, it will of course use
the module 'libgmp'. And this package happens to use libtool.
> Coreutils 'expr' already links to GMP anyway. :-)
:-)
> > Do you think there is something to add to the documentation
> > https://www.gnu.org/software/gnulib/manual/html_node/Searching-for-Libraries.html ?
>
> I am hoping that I do not have to read that documentation; I just want to keep
> building Coreutils the way it's been built for quite some time. ... I merely
> want to be able to use GMP without worrying about libtool.
You can. For uses of system-wide installed GMP, nothing changes. For users who
built GMP on their own, there is the configure option --with-libgmp-prefix. If
there is a problem with it, you can redirect the reports to bug-gnulib or me.
You probably don't want to deal with libtool because of its deep platform
dependencies? 'havelib' also has some platform dependencies, but
- much less of them,
- they are contained in a single file, 'build-aux/config.rpath',
- this file does not need updates more frequently than once in 5 years.
Bruno
next prev parent reply other threads:[~2020-07-24 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:03 [PATCH] libgmp: new module Paul Eggert
2020-07-12 20:30 ` Bruno Haible
2020-07-12 20:57 ` libgmp tests: Add some safety checks Bruno Haible
2020-07-12 21:48 ` libgmp: link to the correct shared library Bruno Haible
2020-07-23 22:13 ` Paul Eggert
2020-07-23 22:30 ` Bruno Haible
2020-07-23 23:23 ` Paul Eggert
2020-07-24 0:00 ` Bruno Haible [this message]
2020-07-26 17:23 ` Paul Eggert
2020-07-26 17:54 ` Paul Eggert
2020-07-12 21:57 ` libgmp: Avoid warning when --without-libgmp is used Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8009390.Ai7DkcWk9P@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jemarch@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).