Bug#812646: cpluff: FTBFS - macro "cpi_lock_framework" passed 1 arguments, but takes just 0

[Balint Reczey]

Control: severity -1 normal
Control: tags -1 moreinfo

Hi Michael,

On Mon, 25 Jan 2016 17:45:56 + Michael Tautschnig  wrote:
> Package: cpluff
> Version: 0.1.3-3
> Severity: serious
> Usertags: goto-cc
> 
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder
> and pbuilder) the build failed with the following error.
> 
> [...]
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -I.. -I../libcpluff -I../libcpluff -DNDEBUG -I. 
> -DCP_C_API=CP_EXPORT -DCP_HOST="\"x86_64-pc-linux-gnu\"" 
> -DCP_DATADIR="\"/usr/share\""  -g -O0 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o cpluff.lo cpluff.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -I.. 
> -I../libcpluff -I../libcpluff -DNDEBUG -I. -DCP_C_API=CP_EXPORT 
> -DCP_HOST=\"x86_64-pc-linux-gnu\" -DCP_DATADIR=\"/usr/share\" -g -O0 
> -fstack-protector-strong -Wformat -Werror=format-security -c cpluff.c  -fPIC 
> -DPIC -o .libs/cpluff.o
> cpluff.c:80:39: error: macro "cpi_lock_framework" passed 1 arguments, but 
> takes just 0
>  CP_HIDDEN void cpi_lock_framework(void) {
>^
> cpluff.c:80:41: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before '{' token
>  CP_HIDDEN void cpi_lock_framework(void) {
>  ^
> cpluff.c:88:41: error: macro "cpi_unlock_framework" passed 1 arguments, but 
> takes just 0
>  CP_HIDDEN void cpi_unlock_framework(void) {
>  ^
> cpluff.c:88:43: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before '{' token
>  CP_HIDDEN void cpi_unlock_framework(void) {
>^
> Makefile:535: recipe for target 'cpluff.lo' failed
> make[4]: *** [cpluff.lo] Error 1
> 
> 
> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.
It looks like the POSIX threading is not detected properly in your build
environment but is detected on every buildd using sbuild.
I decrease the severity of the bug report because FTBFS does not occur
on any official buildd and it looks like a problem in goto-cc.

Cheers,
Balint

Bug#812646: cpluff: FTBFS - macro "cpi_lock_framework" passed 1 arguments, but takes just 0

[Michael Tautschnig]

Package: cpluff
Version: 0.1.3-3
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -I.. -I../libcpluff -I../libcpluff -DNDEBUG -I. 
-DCP_C_API=CP_EXPORT -DCP_HOST="\"x86_64-pc-linux-gnu\"" 
-DCP_DATADIR="\"/usr/share\""  -g -O0 -fstack-protector-strong -Wformat 
-Werror=format-security -c -o cpluff.lo cpluff.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -I.. -I../libcpluff 
-I../libcpluff -DNDEBUG -I. -DCP_C_API=CP_EXPORT 
-DCP_HOST=\"x86_64-pc-linux-gnu\" -DCP_DATADIR=\"/usr/share\" -g -O0 
-fstack-protector-strong -Wformat -Werror=format-security -c cpluff.c  -fPIC 
-DPIC -o .libs/cpluff.o
cpluff.c:80:39: error: macro "cpi_lock_framework" passed 1 arguments, but takes 
just 0
 CP_HIDDEN void cpi_lock_framework(void) {
   ^
cpluff.c:80:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
'{' token
 CP_HIDDEN void cpi_lock_framework(void) {
 ^
cpluff.c:88:41: error: macro "cpi_unlock_framework" passed 1 arguments, but 
takes just 0
 CP_HIDDEN void cpi_unlock_framework(void) {
 ^
cpluff.c:88:43: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
'{' token
 CP_HIDDEN void cpi_unlock_framework(void) {
   ^
Makefile:535: recipe for target 'cpluff.lo' failed
make[4]: *** [cpluff.lo] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


cpluff-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature