Thank you for information.
Alex
On Mon, May 31, 2010 at 10:15 PM, Ralf Wildenhues wrote:
> Hello,
>
> * Gary V. Vaughan wrote on Mon, May 31, 2010 at 05:53:26PM CEST:
> > AFAIK Linux binaries/libraries can be built in the build tree with
> > no hardcoded references to other objects in the build
Hello Ludovic,
Bob has already addressed the rest of this I think, so:
* Ludovic Courtès wrote on Tue, Jun 01, 2010 at 01:15:32AM CEST:
> So it seems that the right test, when compiling natively, involves
> building a shared library and an executable linked against it, and
> running that executab
On Tue, 1 Jun 2010, Ludovic Courtès wrote:
Hello,
GNU Guile relies on TLS (thread-local storage) support where available,
and can live without it on inferior systems. However, I haven’t found a
reliable way to check whether TLS is supported.
Why aren't you using the POSIX TLS APIs? That is
Hello,
GNU Guile relies on TLS (thread-local storage) support where available,
and can live without it on inferior systems. However, I haven’t found a
reliable way to check whether TLS is supported.
Initially, TLS support was tested with:
AC_LINK_IFELSE([AC_LANG_PROGRAM([__thread int tls_inte
Hello,
* Gary V. Vaughan wrote on Mon, May 31, 2010 at 05:53:26PM CEST:
> AFAIK Linux binaries/libraries can be built in the build tree with
> no hardcoded references to other objects in the build tree, so they
> can always be copied into the install tree and continue working
> (although libtool h
On May 31, 2010, at 5:11 PM, Alex Farber wrote:
Sorry, I didn't understand the question. I just tried installation
without relink_command, by removing relink_command from .la file,
and it works. So, I wanted to know when it is really necessary.
On Mon, May 31, 2010 at 10:29 AM, Tor Lillqvi
Sorry, I didn't understand the question. I just tried installation without
relink_command, by removing relink_command from .la file, and it works. So,
I wanted to know when it is really necessary.
On Mon, May 31, 2010 at 10:29 AM, Tor Lillqvist wrote:
> What makes you think the issue relinking i
What makes you think the issue relinking is related to would have
anything to do with Linux in particular?
--tml
___
http://lists.gnu.org/mailman/listinfo/libtool
*.la file produced by libtool contains relink_command, which allows to
relink this library during installation. According to libtool documentation,
this is necessary on the systems where the linker always hardcodes paths to
dependent libraries into the output. What Linux versions require this? I
tr
