|
From: | John W. Eaton |
Subject: | Re: DEFUN_DLD link rule |
Date: | Fri, 30 Aug 2013 15:00:31 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
On 08/30/2013 02:40 PM, Michael Goffioul wrote:
Because gnulib provides many replacement functions under Windows, which are being picked up by other libraries (liboctinterp and dldfcn) through the overridden headers provided by gnulib. So even if you initially only wanted it to be used by liboctave, it's actually being used for other components as well, especially on non POSIX-compliant systems, where many replacement functions are being used.
What is the difference between (for example) liboctave/array/libarray.la and libgnu/libgnu.la? Why don't you have to add liboctave/array/libarray.la explicitly to the liboctinterp.la link command? I thought they were both supposed to be handled as convenience libraries for constructing liboctave. jwe
[Prev in Thread] | Current Thread | [Next in Thread] |