On Nov 26, 2012, at 4:24 PM, Fabio M. Di Nitto <fdinitto@xxxxxxxxxx> wrote:
> On 11/26/2012 3:59 PM, James Guthrie wrote:
>> Hi Fabio,
>>
>> I'm not sure if this is what you're looking for, but I found the following lines in the config.status file:
>> link_all_deplibs='unknown'
>> link_all_deplibs_CXX='unknown'
>
> right, that should be overriden to "yes" by configure.
I tried running configure with the --enable-interlib-deps option, which appears to at least make link_all_deplibs='yes', although link_all_deplibs_CXX remains set to 'unknown'.
I still get the same error when compiling though.
> Do you have a script to build a VM similar to your? or anything that
> could speed up the process?
No, I don't
> as far as i can tell, nss/libqb/corosync are simply pointing to
> /opt/OSAGpace, but everything else appears to be in standard PATH.
Yes, this is the case.
Regards,
James
>>
>> Let me know what I should look into next.
>>
>> Regards,
>> James
>>
>> On Nov 26, 2012, at 3:25 PM, "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> wrote:
>>
>>> On 11/26/2012 3:18 PM, James Guthrie wrote:
>>>> Hi Fabio,
>>>>
>>>> thanks for the quick reply.
>>>>
>>>> OS: Linux From Scratch, Kernel 2.6.32
>>>> Configure was called with the following options:
>>>> ./configure \
>>>> --prefix=/opt/OSAGpace/corosync \
>>>> LDFLAGS='-L/opt/OSAGpace/nss/lib' \
>>>> PKG_CONFIG_PATH=$(PKG_CONFIG_PATH):/opt/OSAGpace/qb/lib/pkgconfig \
>>>> nss_CFLAGS='-I/opt/OSAGpace/nss/include/nss' \
>>>> nss_LIBS='-L/opt/OSAGpace/nss/lib/libnss3.so'
>>>>
>>>> I ran into the same problem compiling from the current master branch.
>>>
>>> Ok. Can you verify that:
>>>
>>> +AC_MSG_NOTICE([enable inter-library dependencies: $enable_interlib_deps])
>>> +if test "${enable_interlib_deps}" == "yes"; then
>>> + link_all_deplibs=yes
>>> + link_all_deplibs_CXX=yes
>>> +else
>>> + link_all_deplibs=no
>>> + link_all_deplibs_CXX=no
>>> +fi
>>>
>>> is set to "yes" in the final configure?
>>>
>>>>
>>>> I'm not sure if this will help, but I'm using Autoconf version 2.68 and libtool 2.4. As we are using Linux From Scratch, these tools are compiled as part of the LFS compilation.
>>>
>>> We are using the same tools in those versions. It might very well a
>>> distribution applied patch that changes behavior, anyway I´ll see if i
>>> can setup a VM for debugging. It´s probably the easiest, unless you can
>>> provide me with access to that machine for debugging (that would for
>>> sure be faster than for me to figure out how to install LFS).
>>>
>>> Thanks for the info
>>> Fabio
>>>
>>>>
>>>> If you need to know any more information, let me know.
>>>>
>>>> Regards,
>>>> James
>>>>
>>>> On Nov 26, 2012, at 2:58 PM, "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> wrote:
>>>>
>>>>> On 11/26/2012 2:50 PM, James Guthrie wrote:
>>>>>> Hi All,
>>>>>>
>>>>>> I tried to upgrade to corosync 2.1.0 today. I have been using corosync
>>>>>> 2.0.1 which I compiled from source. I tried to download and compile
>>>>>> 2.1.0 with the same arguments as used for 2.0.1.
>>>>>
>>>>> This is the second time somebody tells about this error, without
>>>>> providing me the info to debug it :)
>>>>>
>>>>> I need to know:
>>>>>
>>>>> - OS/distribution/version
>>>>> - configure options
>>>>>
>>>>> There is a more generic bug/difference in Debian/Ubuntu libtool that
>>>>> makes linking not working properly and there is a specific config
>>>>> options you need to use, but it´s not part of a release yet (aka you
>>>>> need to use git to have it working)
>>>>>
>>>>> Fabio
>>>>>
>>>>> _______________________________________________
>>>>> discuss mailing list
>>>>> discuss@xxxxxxxxxxxx
>>>>> http://lists.corosync.org/mailman/listinfo/discuss
>>>>
>>>>
>>>> _______________________________________________
>>>> discuss mailing list
>>>> discuss@xxxxxxxxxxxx
>>>> http://lists.corosync.org/mailman/listinfo/discuss
>>>>
>>>
>>
>
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
