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. 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. 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
