[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: improving INSTALL contents, take two
From: |
Ralf Wildenhues |
Subject: |
Re: improving INSTALL contents, take two |
Date: |
Wed, 29 Jul 2009 19:44:37 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-15) |
Hello Alfred,
* Alfred M. Szmidt wrote on Wed, Jul 29, 2009 at 08:51:19AM CEST:
>
> +However, some platforms have known
> +limitations with the semantics of shared libraries that end up requiring
> +recompilation when using this method, particularly noticeable in
> +packages that use @acronym{GNU} Libtool.
>
> Is it worth mentioning this libtool bug? Maybe put it in a footnote?
It is not so much a bug in Libtool as a limitation in some systems.
Of course, if you find a way to work around it, then it could be said
to be a bug in Libtool, but then, even better than documenting that in
end-user text would be to just fix the bug. :-)
> +For packages which support @samp{DESTDIR}, the variable should remain
> +undefined during @command{configure} and @samp{make all}, and only be
> +specified during @samp{make install}.
>
> Does anyone know of a package that gets affected during
> configure/install time by DESTDIR? I find the aboe a bit confusing,
> and think that it might be worth not mentioning it at all.
I can only guess that Eric may have meant it as a reminder to developers
not to define DESTDIR in configure scripts and makefiles.
Cheers,
Ralf