Package: pnetc
Version: 0.6.12-1
Severity: serious

Hi,

building the package pnetc in a clean sid build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
fi
touch debian/stamp-autotools-files
chmod a+x /tmp/buildd/pnetc-0.6.12/build-tree/pnetC-0.6.12/configure 
if test ""; then cd ""; else cd "build-tree/pnetC-0.6.12"; fi && CC="cc" 
CXX="g++" CFLAGS="-g -Wall -O2" CXXFLAGS="-g -Wall -O2" 
/tmp/buildd/pnetc-0.6.12/build-tree/pnetC-0.6.12/configure  
--build=i486-linux-gnu --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/pnetc" 
--srcdir=. --disable-maintainer-mode   
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... cli-unknown-none
checking build system type... i486-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking whether to enable maintainer-specific portions of Makefiles... no
checking for cscc... /usr/bin/cscc
checking for ilrun... /usr/bin/ilrun
checking for ilgac... /usr/bin/ilgac
checking for ildd... /usr/bin/ildd
checking for cscc-cpp... /usr/bin/cscc-cpp
checking for cygpath... no
checking for ilranlib... /usr/bin/ilranlib
checking for gawk... no
checking for mawk... mawk
checking for gcc... /usr/bin/cscc
checking whether the C compiler (/usr/bin/cscc -x c  -fcross-compile-check 
-nostdlib) works... no
configure: error: installation or configuration problem: C compiler cannot 
create executables.
make: *** [build-tree/pnetC-0.6.12/config.status] Error 1
=========================================================================

Is it really intended to replace gcc by cscc?

In configure.in, CC is set to $CSCC, after which the default macros

AC_PROG_AWK
AC_PROG_CC

are run. Looks like this doesn't work. I wonder how it worked before.
cscc doesn't know about some of the above cc options.

--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/


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

Reply via email to