Debian Bug report logs - #285186
FTBFS: powerpc

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Daniel Glassey <wdg@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: FTBFS: powerpc

Date: Sat, 11 Dec 2004 12:38:56 +0000

Package: wxwidgets2.5
Severity: important
Justification: fails to build from source

buildd failed to build for ppc

http://buildd.debian.org/fetch.php?&pkg=wxwidgets2.5&ver=2.5.3.2&arch=powerpc&stamp=1101373844&file=log&as=raw

./bk-deps g++ -c -o basedll_string.o  -D__WXGTK__       -I../src/regex
-DwxUSE_GUI=0 -DWXMAKINGDLL_BASE -DwxUSE_BASE=1 -fPIC -DPIC
-DGTK_NO_CHECK_CASTS -Ilib/wx/include/gtk2-unicode-release-2.5
-I../include -DXTHREADS -pthread -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/include/freetype2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/X11R6/include -O2 -pthread
-Wall ../src/common/string.cpp
../src/common/string.cpp: In member function `int
wxString::PrintfV(const 
   wxChar*, __va_list_tag*)':
   ../src/common/string.cpp:1826: error: cannot convert `__va_list_tag'
   to `void*' 
      for argument `1' to `void* memmove(void*, const void*, unsigned
      int)'
      make[1]: *** [basedll_string.o] Error 1

Regards,
Daniel

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.7-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Message #10 received at 285186@bugs.debian.org (full text, mbox, reply):

From: Johannes Mockenhaupt <jmockenhaupt@gmx.net>

To: 285186@bugs.debian.org

Subject: wxwidgets2.5: va_copy on ppc patch

Date: Fri, 24 Dec 2004 17:53:28 +0100

[Message part 1 (text/plain, inline)]

The configure script is buggy, more specifically, the test for va_copy.
Apply the attached patch and run autoconf to recreate a proper configure.
This is fixed in wxwidgets-cvs.
-- 
 3. The most fun you can have with your clothes on.

[wxwidgets2.5_va_copy_ppc-patch (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 285186@bugs.debian.org (full text, mbox, reply):

From: "Daniel J. Priem" <danielpriem@flexserv.de>

To: 285186@bugs.debian.org

Cc: control@bugs.debian.org

Subject: FTBFS: powerpc

Date: Tue, 01 Feb 2005 23:39:45 +0100

[Message part 1 (text/plain, inline)]

severity 285186 serious

Thanks

FTBFS is serious.

the patch included from 

Daniel Glassey

fixed it.
please upload a new package

Regards
Daniel

[signature.asc (application/pgp-signature, inline)]

Message #24 received at 285186@bugs.debian.org (full text, mbox, reply):

From: Micah Anderson <micah@debian.org>

To: 285186@bugs.debian.org

Subject: Any chance this will be fixed soon?

Date: Fri, 4 Feb 2005 16:07:41 -0600

[Message part 1 (text/plain, inline)]

I see that a patch has been submitted and confirmed to be working in
December, but this bug is still open. I've got a package in the system
that is being held up by wxwidgets2.5 not entering testing because of
these RC bugs (285186 and 287623).

Thanks!
Micah

[signature.asc (application/pgp-signature, inline)]

Message #29 received at 285186@bugs.debian.org (full text, mbox, reply):

From: Ron <ron@debian.org>

To: Micah Anderson <micah@debian.org>, 285186@bugs.debian.org

Subject: Re: Bug#285186: Any chance this will be fixed soon?

Date: Sat, 5 Feb 2005 23:47:27 +1030

Hi,

There are more (also important) bugs than this which need fixing before
this is a viable release.  wx2.5 should be held out of testing at this
stage while they are fixed so having this bug still open just saves me
filing a separate one to keep it out.  I can tag it pending if that
helps, but as has already been observed this is fixed in the cvs where
the next release will come from.

We've actually set a date for a 2.5.4 release upstream now, and I'm
hoping it will be more viable than this one was.  I would like to
see this enter testing, having it do so in time to make stable would be
icing on the cake, but at this stage these packages are barely out of
experimental and are mostly to give early adopters like yourself an
idea of how the package structure has changed since 2.4 etc.  If they
actually work for anyone other than me and the pgadmin team, that would
seem to be a bonus.

I don't consider them being kept out of testing as a 'hold up' at this
stage, but rather a fair assessment of their suitability to be frozen.

2.4 is stable and perfectly suited to a cd pressing.  2.5 on the other
hand has a good chance of both being obsolete and breaking binary
compatibility before you finished making the iso.

The next upload will close all existing rc bugs, and its chances at
getting to testing will then be up to natural selection again, with
a few more users to hopefully shake these things out a bit quicker
than happened this time around.

If there is something actually holding up development of your package,
do let me know and I'll see what can be pushed ahead, but if it is
'just' that its being kept out of testing and is broken on a couple
of arches, then wx has some bigger problems that need attention still
if fixing these is to have any net affect on that goal -- having a
different rc bug keep your package out of testing doesn't help much,
and I'm trying to avoid playing 'whack-a-mole' here while we're busy
working on stabilising big picture things upstream.

Sorry if that's not what you wanted to hear, but 2.5 is still very
much 'bleeding edge' by any honest assessment and it's taking us a
while to get everyone into the mindset that will see it stabilise.
If you need something more than that, let me know and we should
coordinate things with the other maintainers of dependent packages.

cheers,
Ron


On Fri, Feb 04, 2005 at 04:07:41PM -0600, Micah Anderson wrote:
> I see that a patch has been submitted and confirmed to be working in
> December, but this bug is still open. I've got a package in the system
> that is being held up by wxwidgets2.5 not entering testing because of
> these RC bugs (285186 and 287623).
> 
> Thanks!
> Micah

Message #36 received at 285186@bugs.debian.org (full text, mbox, reply):

From: Christian Perrier <bubulle@debian.org>

To: 285186@bugs.debian.org

Subject: More input about this FTBFS bug and the consequences for other packages

Date: Thu, 31 Mar 2005 08:33:06 +0200

I'd like to add a few input lines about this RC bug for wxwindows2.5.

I also have a package (poedit) being held out of testing because of
this RC bug in wxwindows2.5

However, when I decided to build it agains 2.5 and not 2.4, I first
considered that the version of poedit I have in testing is suitable
for release...and the extra features added by wxwindows 2.5 are not
release critical (indeed, building with 2.5 fixes a few longstanding
bugs in poedit, none of them being RC).

So, even if I would rather prefer seeing 2.5 enter testing, I
understand Ron's reasons and I support his plans.

If some other packages have important releases being held out of
testing because of requiring 2.5, they really should consider a fork
and build a version targeted at sarge, which can be built with 2.4.


-- 

Message #41 received at 285186@bugs.debian.org (full text, mbox, reply):

From: Harald Welte <laforge@netfilter.org>

To: 285186@bugs.debian.org

Subject: wxwidgets2.5 on ppc

Date: Mon, 18 Apr 2005 19:13:22 +0200

[Message part 1 (text/plain, inline)]

Hi!

I'm not very familiar with the debian development process, but for me it
is totally unacceptable to have an important package like wxwidgets2.5
(more and more other packages like gnuradio-2.5 are depending on it) in
a broken state for something like four months, if the fix is known and
it's a trivial four line patch to the configure.in file.

I'm talking about 'unstable' here, not testing.

Thanks for your attention.
-- 
- Harald Welte <laforge@netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[Message part 2 (application/pgp-signature, inline)]

Message #46 received at 285186-done@bugs.debian.org (full text, mbox, reply):

From: Ron <ron@debian.org>

To: Harald Welte <laforge@netfilter.org>, 285186-done@bugs.debian.org

Subject: Re: Bug#285186: wxwidgets2.5 on ppc

Date: Tue, 19 Apr 2005 11:55:22 +0930

On Mon, Apr 18, 2005 at 07:13:22PM +0200, Harald Welte wrote:
> Hi!
> 
> I'm not very familiar with the debian development process, but for me it
> is totally unacceptable to have an important package like wxwidgets2.5
> (more and more other packages like gnuradio-2.5 are depending on it) in
> a broken state for something like four months, if the fix is known and
> it's a trivial four line patch to the configure.in file.
> 
> I'm talking about 'unstable' here, not testing.

I don't mean to be rude, but its going to sound that way anyway,
if you find this unacceptable, go fix the goddamn bugs upstream
that made wx2.5 useless to most people, and wx 2.6 still unreleaseable.

I'm talking about something suitable for testing, not another crap
half release cluttering up unstable.  Please come up to speed on
the plot before drawing lines in the sand to suit just yourself.

Consider this a precursor for the report to ftp-admin that will
remove the wx2.5 packages.  2.6 is with us, ready or not, and
as soon as it actually builds from cvs, it will be uploaded.

Thanks for your patience.
Ron

Send a report that this bug log contains spam.