From: Neil Jerram <neil@ossau.uklinux.net>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-guile@gnu.org
Subject: Re: INSTALL matters
Date: Mon, 15 Jun 2009 20:40:18 +0100 [thread overview]
Message-ID: <873aa1e15p.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <200905240104.09138.bruno@clisp.org> (Bruno Haible's message of "Sun\, 24 May 2009 01\:04\:07 +0200")
Bruno Haible <bruno@clisp.org> writes:
> In the weird cases that you are mentioning (like /dir1/lib/ and /dir2/lib/
> which each contain libA and libB, and the user asks to use /dir1/lib/libA.so
> and /dir2/lib/libB.so), yes, there are platforms where this will not work.
>
> But these are not the typical cases and not the common cases. In this case,
> where the emphasis is on making the user's life easier, it is acceptable to
> choose a solution that "works" only in 98% of the cases.
I agree; I just wanted to make sure that I fully understood.
>> OK, so you _do_ think that $prefix/lib should be added to LDFLAGS by
>> default, and $prefix/include to CPPFLAGS.
>
> Yes. This makes most sense for the installing user.
And I see now that havelib does this.
>> Is there an autoconf macro
>> to do that? If there is, does it support a ./configure option for
>> disabling it, for any cases where it isn't wanted?
>
> Good points :-) You are welcome to ask for this on the autoconf list; I
> support your idea.
OK, but I'll wait for a case (if any) where it's needed.
> The AC_LIB_LINKFLAGS_BODY is maintained for a couple of years already.
> Most problems must have been shaken out already:
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=history;f=m4/lib-link.m4;h=21442033c87bd65912d4337d2f3fe686da708e01;hb=68dfc9591e97db34b5ba693da028ff1f356a12b7
[...]
> The doc is also in gnulib, at
> http://www.gnu.org/software/gnulib/manual/html_node/Searching-for-Libraries.html
> (generated from gnulib/doc/havelib.texi). It's explained in some
> detail, but more from the perspective of the developer than from the
> view of the user.
Many thanks for all your input on this subject, Bruno. I've applied
your suggestions to Guile's master branch (which will become the next
stable release series, 2.0.x):
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=39b94fee4304d56babf5bd62e10c5786a79f4389
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=a89cafc0562942680db63fe8ddf89f466ba2f7af
If you have any further comments on this, I'd be happy to hear them.
Regards,
Neil
prev parent reply other threads:[~2009-06-15 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 23:46 INSTALL matters Bruno Haible
2009-05-09 8:24 ` Neil Jerram
2009-05-10 18:34 ` Bruno Haible
2009-05-17 17:39 ` Neil Jerram
2009-05-23 23:04 ` Bruno Haible
2009-06-15 19:40 ` Neil Jerram [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873aa1e15p.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bruno@clisp.org \
--cc=bug-guile@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).