David,
Thanks for the welcoming :). Yes I do work for Sun. That helped me
make it through the compile which was a good sign. Next I ran into
another issue when I did the "make install" -
*** Error code 1
The following command caused the error:
set fnord $MAKEFLAGS; amf=$2; \
dot_seen=no; \
target=`echo install-recursive | sed s/-recursive//`; \
list='libltdl debian pkg port replace include lib
heartbeat membership telecom resources lrm crm fencing
logd tools doc ct
s config contrib'; for subdir in $list; do \
echo "Making $target in $subdir"; \
if test "$subdir" = "."; then \
dot_seen=yes; \
local_target="$target-am"; \
else \
local_target="$target"; \
fi; \
(cd $subdir && gmake $local_target) \
|| case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
done; \
if test "$dot_seen" = "no"; then \
gmake "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `install-recursive'
Any ideas here?
Thanks,
Paul
On Feb 5, 2008, at 7:29 AM, David Lee wrote:
On Mon, 4 Feb 2008, Paul Roberts wrote:
I'm trying to build Heartbeat on S10 x86 and I'm getting a failure
when I try to build it from source. Can anyone help?
lex `test -f conf_lex.l || echo './'`conf_lex.l
"conf_lex.l":line 80: Error: missing translation value
gmake[2]: *** [conf_lex.c] Error 1
gmake[2]: Leaving directory `/export/home/pr199865/Heartbeat/
heartbeat-2.1.3/telecom/recoverymgrd'
Firstly, I spot "Paul Roberts <[EMAIL PROTECTED]>".
How good it is to have someone from inside Sun taking an interest in
heartbeat! (For a few years, I've been trying to maintain heartbeat
portability to include Sun, so it's nice to have company...)
Anyway, I haven't looked in depth at your problem. But it's worth
bearing
in mind that heartbeat sprang from a GNU/Linux environment and the
vast
majority of its real use in such environment.
Now turning to my own Solaris build, I see that "configure" ends up
finding my local GNU "flex", rather than the Sun "lex". (I would
expect
that: configure prefers GNU variants over the manufacturer's.)
So I would guess that if I were to force my build to use "lex", it,
too,
would have the same problem as yours.
I'm no "lex" expert at all. (Although, off-topic, it just so
happens that
I currently have open with Sun a Solaris-9/lex bug for which I'm
expecting
a T-patch any day now...please...)
I guess that "telecom/recoverymgrd/conf_lex.l" contains a flex-ism;
something that works in GNU/flex but not in manufacturer "lex". If
you
could investigate that, and try to provide a fix (that must, of
course,
continue to work in "flex") then I (or other developers here) would be
happy to try to incorporate that into future releases.
Welcome aboard, and best wishes.
--
: David Lee I.T. Service :
: Senior Systems Programmer Computer Centre :
: UNIX Team Leader Durham University :
: South Road :
: http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE :
: Phone: +44 191 334 2752 U.K. :
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
