David Lee wrote:
After months of not pestering, I'm back... with added mercurial.
I'm trying to build the current "dev" on a system (Solaris) that has no
"swig". And (guess what) a problem.
In the old days, "swig" used to be optional; "configure" had it as a "try"
(meaning desirable if available; warn-and-continue if not available).
These days, all that is commented out, so configure runs to completion,
then 'make' falls in a heap in "lib/mgmt" when it can't find swig. Ouch!
If swig has now become compulsory then "configure.in" needs to fail if it
is absent.
If swig is still optional then various "Makefile.am" need attention.
I'm happy to take a look at this, if someone could state, please, whether
swig is compulosry or is still optional.
(As a side-issue; there are versions of swig in existences out there for
Solaris, so if swig really is now compulsory, then that is do-able, but is
an added pain for the end-user. So if optional, it would be good to cater
for that.)
Thanks.
I know it possibly isn't a direction you would choose to follow but FWIW
there is a sunfreeware swig package available (Intel/Sparc ). Although I
agree that it would be more helpful if it is a compilation dependency
for things to fail at the config stage.
Pete
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
