On 28/07/2013, at 2:12 PM, Matthew O'Connor <m...@ecsorl.com> wrote:
> > On 07/23/2013 07:04 PM, Andrew Beekhof wrote: >> On 23/07/2013, at 12:32 AM, Matthew O'Connor <m...@ecsorl.com> wrote: >> >>> Hi Andrew, >>> >>> On 07/19/2013 12:22 AM, Andrew Beekhof wrote: >>>>> I've added the PKG_CONFIG_PATH and the two libqb_ lines in an attempt to >>>>>> make things work, as recommended by the configure help. So far, no >>>>>> dice. Is this something that needs to be fixed in the autoconf/autogen >>>>>> stuff? Something I can submit a patch for? (sadly, not versed at all >>>>>> in autoconf/autogen, but willing to learn!) >>>> we get libqb's details from pnk-config, so depending on what how it >>>> processes PKG_CONFIG_PATH, maybe its returning the "main" installation >>>> instead of the one you put in /opt/cluster >>>> >>> The only libqb on my release of Ubuntu (12.04) is the one I built and >>> installed myself - no released packages available last I checked. >>> Managed to get ./configure working by putting the library and include >>> paths into LDFLAGS and CFLAGS (respectively), and putting the env vars >>> AFTER ./configure instead of before. Maybe PKG_CONFIG_PATH would work >>> better there as well. Unfortunately it's still not a totally clean >>> install on Ubuntu as the cluster-glue stuff dictates where the ocf files >>> go. Will either have to build cluster-glue from scratch or take what I >>> have as a compromise and go. >> What version were you trying to build btw? >> Because configure has changed a bit in that area. Maybe HEAD will behave >> better for you... > 1.1.9. I did eventually find that supplying PKG_CONFIG_PATH as an > _argument_ to configure instead of as an environment var made the > necessary difference. I thereafter succeeded in building a full suite > to a non-standard folder. Sadly I couldn't quite get around not using > sudo for most of the "make install"s...changing ownership as an > underprivileged user is obviously a no-no. Glad you made progress in the end :) > > One issue I came across: when configuring the resource-agents package > for install, I had to use a peculiar configure line to get the ocf > scripts in the right place: > > ./configure --prefix=/opt/cluster --with-ocf-root=lib/ocf > > I came to that after digging through how configure was using the > variables related to the OCF root. This seems to be dissimilar to > cluster-glue's usage of --with-ocf-root (which was > --with-ocf-root=/opt/cluster/lib/ocf). Passing along to David who looks after resource-agents for RH. However, once they're no longer in /usr/lib/ocf, they're technically not compliant with the OCF standard anymore ;-) > > One other question: which corosync version do you recommend to use with > 1.1.9+? I'm on 1.4.6 right now. Pacemaker can function with anything since 1.2 iirc. > > Thanks! > > -- Matthew > P.S. I'm looking forward to trying 1.1.10! > >>> Thanks! >>> >>> -- >>> Thank you! >>> Matthew O'Connor >>> (GPG Key ID: 55F981C4) >>> >>> >>> CONFIDENTIAL NOTICE: The information contained in this electronic message >>> is legally privileged, confidential and exempt from disclosure under >>> applicable law. It is intended only for the use of the individual or entity >>> named above. If the reader of this message is not the intended recipient, >>> you are hereby notified that any dissemination, distribution or copying of >>> this message is strictly prohibited. If you have received this >>> communication in error, please notify the sender immediately by return >>> e-mail and delete the original message and any copies of it from your >>> computer system. Thank you. >>> >>> EXPORT CONTROL WARNING: This document may contain technical data that is >>> subject to the International Traffic in Arms Regulations (ITAR) controls >>> and may not be exported or otherwise disclosed to any foreign person or >>> firm, whether in the US or abroad, without first complying with all >>> requirements of the ITAR, 22 CFR 120-130, including the requirement for >>> obtaining an export license if applicable. In addition, this document may >>> contain technology that is subject to the Export Administration Regulations >>> (EAR) and may not be exported or otherwise disclosed to any non-U.S. >>> person, whether in the US or abroad, without first complying with all >>> requirements of the EAR, 15 CFR 730-774, including the requirement for >>> obtaining an export license if applicable. Violation of these export laws >>> is subject to severe criminal penalties. >>> >>> >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > > > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
