Source: libapache2-mod-fcgid
Version: 1:2.3.5-1
Severity: serious
Tags: squeeze sid
User: [email protected]
Usertags: qa-ftbfs-20100524 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /usr/share/apr-1.0/build/libtool --silent --mode=compile x86_64-linux-gnu-gcc 
>   -DLINUX=2 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_REENTRANT 
> -I/usr/include/apr-1.0 -I/usr/include/openssl -I/usr/include/xmltok -pthread  
> -DFCGID_APXS_BUILD   -DLINUX=2 -D_GNU_SOURCE -D_REENTRANT 
> -I/usr/include/apache2 -I. -I/usr/include/apr-1.0  
> -I/build/user-libapache2-mod-fcgid_2.3.5-1-amd64-9P4xLA/libapache2-mod-fcgid-2.3.5/modules/fcgid
>  
> -I/build/user-libapache2-mod-fcgid_2.3.5-1-amd64-9P4xLA/libapache2-mod-fcgid-2.3.5/modules/fcgid
>  
> -I/build/user-libapache2-mod-fcgid_2.3.5-1-amd64-9P4xLA/libapache2-mod-fcgid-2.3.5/include
>  -I/usr/include/apache2 -I. -I/usr/include/apr-1.0 -prefer-pic -c mod_fcgid.c 
> && touch mod_fcgid.slo
> In file included from fcgid_global.h:26,
>                  from mod_fcgid.c:27:
> fcgid_config.h:4:9: error: macro names must be identifiers
> fcgid_config.h:7:9: error: macro names must be identifiers
> fcgid_config.h:13:9: error: macro names must be identifiers
> make[2]: *** [mod_fcgid.slo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2010/05/24/libapache2-mod-fcgid_1:2.3.5-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to