[Debian-ha-maintainers] Bug#802250: gfs2-utils: FTBFS: error: unknown type name 'cpg_error_t'
peter green
plugwash at p10link.net
Fri Oct 30 00:00:31 UTC 2015
Tags: gfs2-utils +stretch
Thanks
I ran into this package trying to get a transition to go through in
raspbian stretch. After attacking some issues with build-dependencies on
obsolete packages and with the clean target not cleaning up properly I
ran into the same error that is given in this bug report.
I fixed a load of errors with type/costant names. it appears that cpg_
prefixes had been replaced with cs_ prefixes. I also fixed a case of a
struct that had had a field removed. Since the app had previously just
been setting that field to null I just removed the assignment.
Unfortunately I then ran into a function that added a new parameter.
gcc -DHAVE_CONFIG_H -I. -I../../make -I../../group/libgfscontrol
-I../../group/include -I/usr/src/linux/include -I../../make
-I../../make -I. -D_FORTIFY_SOURCE=2 -I/usr/include/openais
-I../../dlm/include -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -O2 -ggdb3 -Wall -Wshadow
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings
-Wcast-align -Wbad-function-cast -Wmissing-format-attribute -Wformat=2
-Wformat-security -Wformat-nonliteral -Wno-long-long
-Wno-strict-aliasing -MT gfs_controld-member_cman.o -MD -MP -MF
.deps/gfs_controld-member_cman.Tpo -c -o gfs_controld-member_cman.o
`test -f 'member_cman.c' || echo './'`member_cman.c
member_cman.c: In function 'setup_cluster':
member_cman.c:94:8: error: too few arguments to function 'quorum_initialize'
err = quorum_initialize(&qh, &quorum_callbacks);
^
In file included from member_cman.c:5:0:
/usr/include/corosync/quorum.h:63:12: note: declared here
cs_error_t quorum_initialize (
^
Makefile:564: recipe for target 'gfs_controld-member_cman.o' failed
make[3]: *** [gfs_controld-member_cman.o] Error 1
make[3]: Leaving directory '/gfs2-utils-3.1.3/group/gfs_controld'
Makefile:397: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/gfs2-utils-3.1.3/group'
Makefile:453: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/gfs2-utils-3.1.3'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:18: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
root at odroidu2:/gfs2-utils-3.1.3#
I found some documentation on the paramter in question, but i've no idea
how to chose between the two possible values whin the context of a flyby
fix to existing code.
http://manpages.ubuntu.com/manpages/saucy/man3/quorum_initialize.3.html
The_quorum_type_ argument is set to:
#define QUORUM_FREE 0
#define QUORUM_SET 1
_QUORUM_FREE_ value means that no quorum algorithm is loaded and that no
callbacks will take place.
_QUORUM_SET_ value means that one quorum algorithm is configured and that
callbacks will take place.
When a configuration change occurs, the callback is called from the
*quorum_dispatch()* function.
Debdiff of what I have done so far is attatched.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20151030/7a59858f/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gfs2-utils.debdiff
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20151030/7a59858f/attachment.ksh>
More information about the Debian-ha-maintainers
mailing list