Hi Gary,
On Tue, Oct 23, 2012 at 6:04 PM, Gary V. Vaughan wrote:
>>> lt-func_mode_compile> func_to_tool_file alloc.c
>>> func_convert_file_msys_to_w32
>
> Are you building on some variant of Windows?
OS/X Lion.
>> $to_tool_file_cmd "$1" <= "$to_tool_file_cmd" is empty
>>
Here ya go. The full log of the "autogen.sh" run, the configure and the build.
The project is "bdwgc", whatever that is.
$ bash -x ./autogen.sh
>sh> export 'PS4=>sh-${FUNCNAME}> '
>sh> PS4='>sh-${FUNCNAME}> '
>sh-> do_always
>sh-do_always> export 'PS1=\w\n\$ '
>sh-do_always> PS1='\w\n\$ '
>sh-do_
P.S.:
$ fgrep to_tool_file_cmd *
libtool:*,"$to_tool_file_cmd",*)
libtool: $to_tool_file_cmd "$1"
libtool: case $nm_file_list_spec~$to_tool_file_cmd in
ltmain.sh:*,"$to_tool_file_cmd",*)
ltmain.sh: $to_tool_file_cmd "$1"
ltmain.sh:case $nm_file_list_spec~
Hi Bruce,
Looking at your log, _LT_PATH_CONVERSION_FUNCTIONS is never run because
the configure output doesn't even show the selection of func_to_tool_file_cmd
from the check it expands to. This is likely induced by the swathe of
autoconf warnings when you try to rebuild configure, leaving you wi
Hi Bruce,
On 24 Oct 2012, at 19:22, Bruce Korb wrote:
> P.S. Were you able to help Mark Weaver with: user_search_path vs
> libtool --mode=execute -dlopen ?
> I'm holding on to the next release until I know what Guile is going to
> do about fiddling LD_LIBRARY_PATH.
That seems to have fallen off
On Wed, Oct 24, 2012 at 7:22 AM, Gary V. Vaughan wrote:
> Hi Bruce,
>
> On 24 Oct 2012, at 19:22, Bruce Korb wrote:
>> P.S. Were you able to help Mark Weaver with: user_search_path vs
>> libtool --mode=execute -dlopen ?
>> I'm holding on to the next release until I know what Guile is going to
>>
