Bug#353532: FTBFS (alpha): va_list abuse

2007-05-12 Thread Moritz Schulte
 thanks for the patch. The upstream author, Moritz Schulte, is getting
 PTS mails, so I think he’ll have received the patch. Right Moritz?

Yes, thanks for the patch, I will take care of it soon.
Moritz




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



Bug#353532: FTBFS (alpha): va_list abuse

2007-05-01 Thread Steve Langasek
tags 353532 patch
thanks

Hi Joachim,

As Falk identified when this bug was filed, the current behavior is abuse of
the vsyslog() function which causes a build failure on alpha due to that
arch's implementation of va_list.  There is no reason to call vsyslog() with
a NULL ap argument, syslog() does what's wanted here.

I've prepared a porter NMU to fix this bug in poldi.  The patch to fix this
is attached, and should be applied upstream.  The NMU will be uploaded to
incoming shortly.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/
diff -u poldi-0.3.0/config.guess poldi-0.3.0/config.guess
--- poldi-0.3.0/config.guess
+++ poldi-0.3.0/config.guess
@@ -1,9 +1,10 @@
 #! /bin/sh
 # Attempt to guess a canonical system name.
 #   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
+#   2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation,
+#   Inc.
 
-timestamp='2006-02-23'
+timestamp='2007-03-06'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
@@ -160,6 +161,7 @@
 	arm*) machine=arm-unknown ;;
 	sh3el) machine=shl-unknown ;;
 	sh3eb) machine=sh-unknown ;;
+	sh5el) machine=sh5le-unknown ;;
 	*) machine=${UNAME_MACHINE_ARCH}-unknown ;;
 	esac
 	# The Operating System including object format, if it has switched
@@ -210,7 +212,7 @@
 	echo ${UNAME_MACHINE}-unknown-solidbsd${UNAME_RELEASE}
 	exit ;;
 macppc:MirBSD:*:*)
-	echo powerppc-unknown-mirbsd${UNAME_RELEASE}
+	echo powerpc-unknown-mirbsd${UNAME_RELEASE}
 	exit ;;
 *:MirBSD:*:*)
 	echo ${UNAME_MACHINE}-unknown-mirbsd${UNAME_RELEASE}
@@ -770,6 +772,8 @@
 	case ${UNAME_MACHINE} in
 	pc98)
 		echo i386-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
+	amd64)
+		echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
 	*)
 		echo ${UNAME_MACHINE}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
 	esac
@@ -777,10 +781,7 @@
 i*:CYGWIN*:*)
 	echo ${UNAME_MACHINE}-pc-cygwin
 	exit ;;
-i*:MINGW*:*)
-	echo ${UNAME_MACHINE}-pc-mingw32
-	exit ;;
-i*:MSYS_NT-*:*:*)
+*:MINGW*:*)
 	echo ${UNAME_MACHINE}-pc-mingw32
 	exit ;;
 i*:windows32*:*)
@@ -790,12 +791,15 @@
 i*:PW*:*)
 	echo ${UNAME_MACHINE}-pc-pw32
 	exit ;;
-x86:Interix*:[345]*)
-	echo i586-pc-interix${UNAME_RELEASE}
-	exit ;;
-EM64T:Interix*:[345]*)
-	echo x86_64-unknown-interix${UNAME_RELEASE}
-	exit ;;
+*:Interix*:[3456]*)
+	case ${UNAME_MACHINE} in
+	x86) 
+		echo i586-pc-interix${UNAME_RELEASE}
+		exit ;;
+	EM64T | authenticamd)
+		echo x86_64-unknown-interix${UNAME_RELEASE}
+		exit ;;
+	esac ;;
 [345]86:Windows_95:* | [345]86:Windows_98:* | [345]86:Windows_NT:*)
 	echo i${UNAME_MACHINE}-pc-mks
 	exit ;;
@@ -831,6 +835,9 @@
 arm*:Linux:*:*)
 	echo ${UNAME_MACHINE}-unknown-linux-gnu
 	exit ;;
+avr32*:Linux:*:*)
+	echo ${UNAME_MACHINE}-unknown-linux-gnu
+	exit ;;
 cris:Linux:*:*)
 	echo cris-axis-linux-gnu
 	exit ;;
@@ -947,6 +954,9 @@
 x86_64:Linux:*:*)
 	echo x86_64-unknown-linux-gnu
 	exit ;;
+xtensa:Linux:*:*)
+	echo xtensa-unknown-linux-gnu
+	exit ;;
 i*86:Linux:*:*)
 	# The BFD linker knows what the default object file format is, so
 	# first see if it will tell us. cd to the root directory to prevent
@@ -989,7 +999,7 @@
 	LIBC=gnulibc1
 	# endif
 	#else
-	#if defined(__INTEL_COMPILER) || defined(__PGI) || defined(__sun)
+	#if defined(__INTEL_COMPILER) || defined(__PGI) || defined(__SUNPRO_C) || defined(__SUNPRO_CC)
 	LIBC=gnu
 	#else
 	LIBC=gnuaout
@@ -1205,6 +1215,15 @@
 SX-6:SUPER-UX:*:*)
 	echo sx6-nec-superux${UNAME_RELEASE}
 	exit ;;
+SX-7:SUPER-UX:*:*)
+	echo sx7-nec-superux${UNAME_RELEASE}
+	exit ;;
+SX-8:SUPER-UX:*:*)
+	echo sx8-nec-superux${UNAME_RELEASE}
+	exit ;;
+SX-8R:SUPER-UX:*:*)
+	echo sx8r-nec-superux${UNAME_RELEASE}
+	exit ;;
 Power*:Rhapsody:*:*)
 	echo powerpc-apple-rhapsody${UNAME_RELEASE}
 	exit ;;
diff -u poldi-0.3.0/config.sub poldi-0.3.0/config.sub
--- poldi-0.3.0/config.sub
+++ poldi-0.3.0/config.sub
@@ -1,9 +1,10 @@
 #! /bin/sh
 # Configuration validation subroutine script.
 #   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
+#   2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation,
+#   Inc.
 
-timestamp='2006-02-23'
+timestamp='2007-01-18'
 
 # This file is (in principle) common to ALL GNU software.
 # The presence of a machine in this file suggests that SOME GNU software
@@ -240,15 +241,16 @@
 	| alpha | alphaev[4-8] | alphaev56 | alphaev6[78] | alphapca5[67] \
 	| alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] | 

Bug#353532: FTBFS (alpha): va_list abuse

2007-05-01 Thread Joachim Breitner
Hi,

thanks for the patch. The upstream author, Moritz Schulte, is getting
PTS mails, so I think he’ll have received the patch. Right Moritz?

Greetings,
Joachim


Am Dienstag, den 01.05.2007, 00:07 -0700 schrieb Steve Langasek:
 tags 353532 patch
 thanks
 
 Hi Joachim,
 
 As Falk identified when this bug was filed, the current behavior is abuse of
 the vsyslog() function which causes a build failure on alpha due to that
 arch's implementation of va_list.  There is no reason to call vsyslog() with
 a NULL ap argument, syslog() does what's wanted here.
 
 I've prepared a porter NMU to fix this bug in poldi.  The patch to fix this
 is attached, and should be applied upstream.  The NMU will be uploaded to
 incoming shortly.
 
 Thanks,
-- 
Joachim nomeata Breitner
Debian Developer
  [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata




Bug#353532: FTBFS (alpha): va_list abuse

2006-02-19 Thread Falk Hueffner
Package: poldi
Version: 0.3.0-1
Severity: important
Justification: fails to build from source

poldi fails to build on Alpha:
[...]
if alpha-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../..  -I../../intl  -fPIC  
-Wall -g -O2 -Wall -MT logging.o -MD -MP -MF .deps/logging.Tpo -c -o 
logging.o logging.c; \
then mv -f .deps/logging.Tpo .deps/logging.Po; else rm -f 
.deps/logging.Tpo; exit 1; fi
logging.c: In function 'set_file_fd':
logging.c:298: warning: assignment from incompatible pointer type
logging.c: In function 'do_logv':
logging.c:606: error: incompatible type for argument 3 of 'vsyslog'
make[4]: *** [logging.o] Error 1
make[4]: Leaving directory `/tmp/poldi-0.3.0/src/jnlib'

see full log at
http://buildd.debian.org/fetch.php?pkg=poldiarch=alphaver=0.3.0-2stamp=1140319236file=log

This is because of:

  vsyslog (syslog_priorities[JNLIB_LOG_INFO],
   fmt_prefix, NULL);

NULL is not a va_list. I'm unsure what this is supposed to do,
probably you can just use syslog instead.

Falk



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: alpha
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-rc4-dirty
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)


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