Package: netdude
version: 0.3.3-2.2
Severity: serious
Justification: FTBFS on i386

Hi,

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

Relevant part:
make[4]: Entering directory `/build/user/netdude-0.3.3/protocols/fddi'
if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. 
-I../.. -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include 
-I../.. -I../../libltdl -I../../include -W -Wall    -g -O2 -MT nd_fddi.lo -MD 
-MP -MF ".deps/nd_fddi.Tpo" -c -o nd_fddi.lo nd_fddi.c; \
        then mv -f ".deps/nd_fddi.Tpo" ".deps/nd_fddi.Plo"; else rm -f 
".deps/nd_fddi.Tpo"; exit 1; fi
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include/gtk-1.2 
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I../.. -I../../libltdl 
-I../../include -W -Wall -g -O2 -MT nd_fddi.lo -MD -MP -MF .deps/nd_fddi.Tpo -c 
nd_fddi.c  -fPIC -DPIC -o .libs/nd_fddi.o
In file included from /usr/include/netinet/if_fddi.h:26,
                 from ./nd_fddi.h:29,
                 from nd_fddi.c:34:
/usr/include/linux/if_fddi.h:88: error: expected specifier-qualifier-list 
before '__be16'
make[4]: *** [nd_fddi.lo] Error 1
make[4]: Leaving directory `/build/user/netdude-0.3.3/protocols/fddi'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/build/user/netdude-0.3.3/protocols'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/user/netdude-0.3.3'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/user/netdude-0.3.3'
make: *** [build-stamp] Error 2

The full build log is available from
http://people.debian.org/~lucas/logs/2007/06/14/

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  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