[Linux-ha-dev] Re: [Linux-HA] Solaris10 x86

Xun Sun xun.sun.cn at gmail.com
Sat Feb 18 05:51:38 MST 2006


On 2/18/06, David Lee <t.d.lee at durham.ac.uk> wrote:
> On Fri, 17 Feb 2006, Xun Sun wrote:
>
> > On 2/17/06, Xun Sun <xun.sun.cn at gmail.com> wrote:
> > > Hi Davis,
> > > This is a problem with our Makefile, not your missing package.
> > >
> > > On 2/17/06, Davis, Jacob <Jacob_Davis at sra.com> wrote:
> > > > Thank you for the help.
> > > > There was no AR environment variable set, but editing the libtool script as you suggested solved the AR problem.
> > > >
> > > > Sadly, I know have a new problem. The build continues untill I get to mgmt:
> > > >
> > > > ------snip--------
> > > > Making all in mgmt
> > > > gmake[2]: Entering directory `/root/download/heartbeat-2.0.3/lib/mgmt'
> > > > source='pymgmt_wrap.c' object='_pymgmt_la-pymgmt_wrap.lo' libtool=yes \
> > > > depfile='.deps/_pymgmt_la-pymgmt_wrap.Plo' tmpdepfile='.deps/_pymgmt_la-pymgmt_wrap.TPlo' \
> > > > depmode=none /bin/bash ../../depcomp \
> > > > /bin/bash ../../libtool  --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../linux-ha -I../../include -I../../include -I../../include -I../../linux-ha -I../../linux-ha -I../../libltdl -I../../libltdl -I../..          -I../..  -DLIBNET_LIL_ENDIAN  -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -I/usr/include/libxml2
> > >
> > > >-I/opt/LXHAhb/include/python2.3
> > >
> > > Python.h file could not be found, because /opt/LXHAhb/include/ is the
> > > place where header files from heartbeat should be installed, not the
> > > place to find python headers.
> > >
> > > I'm going to file a bug on this problem.
> > >
> >
> > It is bug 1096:
> >
> >     http://www.osdl.org/developer_bugzilla/show_bug.cgi?id=1096
>
> I agree it is a bug in "Makefile.am", but there may be a "configure.in"
> aspect also.
>
> Do we want to pursue this on this list (i.e. "linux-ha-dev") or on
> bugzilla?  it ought to be in a place that Jacob Davis can at least monitor
> what we discuss.  (We could add his email to the bugzilla's "Cc:".)
>
> But for the moment, could Jacob supply the information below, please?
>
> Jacob:  What was your "configure" output concerning python?  Or at least
> the information extracted from that:
>
> For instance my S10 box, which doesn't have python (actually it does, but
> hidden away), and therefore tries to avoid building "mgmt" gives:
>
>    sol10host% grep -n Python.h *
>    config.log:9944:configure:41555: checking python2.2/Python.h usability
>    config.log:9946:conftest.c:172: python2.2/Python.h: No such file or directory
>    config.log:10120:| #include <python2.2/Python.h>
>    config.log:10122:configure:41600: checking python2.2/Python.h presence
>    config.log:10124:conftest.c:138: python2.2/Python.h: No such file or directory
>    config.log:10264:| #include <python2.2/Python.h>
>    config.log:10266:configure:41671: checking for python2.2/Python.h
>    config.log:10301:     python2.2/Python.h
>    config.log:10643:ac_cv_header_python2_2_Python_h=no
>    sol10host%
>
> whereas my Linux box, which does have a python, gives:
>
>    linuxhost% grep Python.h *
>    config.log:configure:41555: checking python2.4/Python.h usability
>    config.log:configure:41600: checking python2.4/Python.h presence
>    config.log:configure:41671: checking for python2.4/Python.h
>    config.log:ac_cv_header_python2_4_Python_h=yes
>    linuxhost%
>
> Also, what is the path to the "Python.h" file that configure needs to be
> finding?  (I'm not necessarily proposing building in this path, but rather
> trying to get an understanding about how we should be looking for it and
> then passing on that knowledge through the configure/make process.)
>
One way to heal the problem is to add Python.h location into CPPFLAGS.
Assuming the Python headers are installed in standard location
(otherwise they may be at arbitrary locations and we are unable to
find them programmingly in configure.in, then the user should specify
the CPPFLAGS to include them), I propose a straightforward solution:

*AC_CHECK_HEADER[/usr/include/$PYTHON_HEADER_DIR/Python.h], if
successful, CPPFLAGS+=-I/usr/include/$PYTHON_HEADER_DIR, else

*AC_CHECK_HEADER[/usr/local/include/$PYTHON_HEADER_DIR/Python.h], if
successful, CPPFLAGS+=-I/usr/local/include/$PYTHON_HEADER_DIR, else

*AC_CHECK_HEADER[$PYTHON_HEADER_DIR/Python.h]

By the last trial, we are assured even if Python headers aren't in
standard location, they still can be found if user specified CPPFLAGS
to us.

Test of other standard locations (as for Solaris or other systems) can
be recommended and added.

Any comments or better ideas?

> (You're probably one of the first people in the world to be trying
> heartbeat 2.0.x on Solaris 10 with Python!)
>
> Best wishes.
>
>
> --
>
> :  David Lee                                I.T. Service          :
> :  Senior Systems Programmer                Computer Centre       :
> :                                           Durham University     :
> :  http://www.dur.ac.uk/t.d.lee/            South Road            :
> :                                           Durham DH1 3LE        :
> :  Phone: +44 191 334 2752                  U.K.                  :
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
>
--
Thanks & regards
Xun Sun



More information about the Linux-HA mailing list