Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Alasdair McWilliam
Package: rageircd Version: 2.0.0-2 Hi Marc, Apologies for not getting back to you sooner - I've been working hard. I've got around to the proper bug fix so bare with me. Firstly, replace all the current VA_COPY declaration statements in include/common.h with: #ifdef HAVE___VA_COPY #define

Bug#309196: Fwd: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Alasdair McWilliam
May 2005 14:43:06 BDTTo: Marc Haber [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: Re: Bug#307231: RageIRCd build failure on s390 Package: rageircdVersion: 2.0.0-2Hi Marc,Apologies for not getting back to you sooner - I've been working hard.I've got around to the proper bug fix so bare

Bug#307231: Fwd: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Alasdair McWilliam
See messages forwarded below. Sent to the wrong bug report in error.Begin forwarded message:From: Alasdair McWilliam [EMAIL PROTECTED]Date: 16 May 2005 14:45:15 BDTTo: Marc Haber [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: Fwd: Bug#307231: RageIRCd build failure on s390 Package: rageircdVersion

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Florian Weimer
* Alasdair McWilliam: Change to: AC_CHECK_FUNCS([times index rindex setlinebuf va_copy __va_copy]) va_copy is a macro, so this check won't work reliably. On Debian, it's safe to use va_copy unconditionally because it's part of GCC's stdarg.h header. -- To UNSUBSCRIBE, email to [EMAIL

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Marc Haber
Hi Alasdair, On Mon, May 16, 2005 at 04:21:15PM +0200, Florian Weimer wrote: * Alasdair McWilliam: Change to: AC_CHECK_FUNCS([times index rindex setlinebuf va_copy __va_copy]) va_copy is a macro, so this check won't work reliably. Florian usually knows what he is talking about, so I'd

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Florian Weimer
* Marc Haber: +#if defined(__GNUC__) || (defined(__powerpc__) defined(__FreeBSD__)) #define VA_COPY __va_copy +#elif defined(__powerpc__) defined(__NetBSD__) +#define VA_COPY va_copy #else #define VA_COPY(x, y) x = y #endif Would that be ok with both of you? __va_copy is provided

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Alasdair McWilliam
I expect you know more than me about this so I'll go with the patch you've given. Thanks for your input on this issue too it's really appreciated. :-) I'll re-fix the BLUEMOON branch tomorrow evening probably. Is it possible to close the other bug associated with rageircd as it's not really a

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Marc Haber
Hi, On Mon, May 16, 2005 at 10:19:08PM +0100, Alasdair McWilliam wrote: I expect you know more than me about this so I'll go with the patch you've given. Thanks. So I can upload the patched version to unstable, fixing the s390 issue? Is it possible to close the other bug associated with

Bug#309196: Bug#307231: RageIRCd build failure on s390

2005-05-16 Thread Alasdair McWilliam
Thanks. So I can upload the patched version to unstable, fixing the s390 issue? Yes :-) It is an issue which makes the current rageircd unsuitable for release with a stable version. We have missed sarge anyway, so the package wouldn't migrate from unstable to testing anyway. That bug report

Bug#307231: RageIRCd build failure on s390

2005-05-15 Thread Marc Haber
Thiemo Seufer suggests replacing the entire VA_COPY detection code with: #if defined(__GNUC__) || (defined(__powerpc__) defined(__FreeBSD__)) #define VA_COPY __va_copy #elif defined(__powerpc__) defined(__NetBSD__) #define VA_COPY va_copy #else #define VA_COPY(x, y) x = y #endif With that

Bug#307231: RageIRCd build failure on s390

2005-05-07 Thread Marc Haber
tags #307231 thanks On Sun, May 01, 2005 at 11:44:56PM +0100, Alasdair McWilliam wrote: The compile failure is in src/ircsprintf.c as follows. cc -g -Wall -O2 -export-dynamic -I../adns -I../include -I../zlib -c ircsprintf.c ircsprintf.c: In function `ircvsprintf': ircsprintf.c:29:

Bug#307231: RageIRCd build failure on s390

2005-05-07 Thread Alasdair McWilliam
tags #307231 thanks To help debugging you can configure with --enable-developer (either manually with ./configure or specified in config when it asks for additional arguments). This makes compile a bit more anally retentive and will complain at more things. Hehe. Alasdair On 7 May 2005, at

Bug#307231: RageIRCd build failure on s390

2005-05-02 Thread Alasdair McWilliam
Probably because I've made a wee booboo. ;-) 2.0.1 will be along quicker than planned as I was up until 3am doing lots of tweaking and fixing here and there. Give me a few days. (I've a better fix for the va_copy issue too, will use autoconf.) Thanks for responding Alasdair On 2 May 2005, at

Bug#307231: RageIRCd build failure on s390

2005-05-01 Thread Alasdair McWilliam
Package: rageircdVersion: 2.0.0-2HiI've checked the build logs for rageircd 2.0.0-2 in unstable and have noticed that the actual rageircd binary doesn't build on the s390 architecture. Hence I am reporting it here.The compile failure is in src/ircsprintf.c as follows.cc  -g -Wall -O2

Bug#307231: RageIRCd build failure on s390

2005-05-01 Thread Marc Haber
severity #307231 serious thanks Justification: hidden FTBFS Hi, On Sun, May 01, 2005 at 11:44:56PM +0100, Alasdair McWilliam wrote: I've checked the build logs for rageircd 2.0.0-2 in unstable and have noticed that the actual rageircd binary doesn't build on the s390 architecture. Hence