Bug#179128: Reference bug...

2003-01-31 Thread Joel Baker
This is *almost* certainly related to bug #178325 (LIBC_DEV value for
libc12), but I don't see any obvious reason for it to be failing like
this; the patch simply mimics and continues the prior pattern of testing
in a cascade fashion for various things, before bailing to a default of
libc6-dev, and I'm not at all sure why the following lines are not
functioning in an equivalent manner:

ifeq ($(DEB_HOST_ARCH), $(findstring $(DEB_HOST_ARCH),alpha ia64))
ifeq ($(DEB_HOST_ARCH), $(findstring $(DEB_HOST_ARCH),netbsd-i386)) 
-- 
Joel Baker <[EMAIL PROTECTED]>


pgpxE0kT0Qt2D.pgp
Description: PGP signature


Re: GCC 3.3, GCC 3.4

2003-01-31 Thread Matthias Klose
[going to vacation for three weeks, therefore trimmed the CCs]

Zack Weinberg writes:
> Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> 
> > Zack Weinberg <[EMAIL PROTECTED]> writes:
> >
> > | Benjamin Kosnik <[EMAIL PROTECTED]> writes:
> > | >
> > | > I've versioned the runtimes assuming that 3.3 will not break the 3.2
> > | > ABI, and that 3.4 will. Lacking clear guidance on what to do, I think
> > | > this was an ok decision.
> > | 
> > | There are groups out there, such as the LSB (Linux Standard Base)
> > | effort, who are working on the assumption that the 3.2 ABI will
> > | *never* be changed again.
> >
> > I believe the agreement was that the 3.2 and 3.3 won't be changed for
> > the 3.2.x and 3.3.x series.
> >
> > But that agreement does not export to higher versions.  People reading
> > more into that agreement should be advised to coordinate/ask people
> > workiing the C++ ABI and GCC/g++.
> 
> I'm relaying this to the LSB working group in charge of C++ and also
> to the Debian gcc team -- Debian is presently in the process of
> transitioning to the 3.2 ABI and I am pretty sure they also were
> operating under the assumption that it would not change ever again.

well, we are getting used to transitions ;-) Last time I checked the
LSB list mentioned by Benjamin, I couldn't find any activity on the
C++ issues.

What I read from the gcc lists, I am under the impression that 3.3
doesn't change the ABI from the 3.2 series. Two ABI transitions in
three months would really hurt. My plan is to make 3.3 the default
compiler at least on some architectures, when it's released.




Bug#179128: libstdc++5-dev: depends on libc12-dev, which only NetBSD has

2003-01-31 Thread Matthias Klose
Aaron M. Ucko writes:
> libstdc++5-dev seems to have gained a dependency on libc12-dev, which
> AFAICT only exists on Debian GNU/NetBSD; could you please
> conditionalize it accordingly?
> 
> Likewise for libgcj3-dev and libffi2-dev.

I should not test on hppa only, when i386 specific changes are going
in. i386-linux is the only architecture affected. Ryan Murray already
fixed this in CVS.




Bug#179161: [fixed in snapshot 20030105] lcdproc_0.4.3-12(mipsel) regression from 2.95

2003-01-31 Thread Ryan Murray
Package: gcc-3.2
Version: 1:3.2.2-0pre7
Severity: important

There was an error while trying to autobuild your package:

> Automatic build of lcdproc_0.4.3-12 on repeat.rfc822.org by sbuild/mipsel 
> 1.170
> Build started at 20030111-2236

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 3.0.0), automake, autoconf2.13, texinfo, 
> libncurses5-dev

[...]

>  The following central src deps are (probably) missing:
>   liblircclient-dev

[...]

> gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I./.. -I../..-Wall -O3 -c lcdm001.c
> lcdm001.c: In function `lcdm001_vbar':
> lcdm001.c:485: internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[4]: *** [lcdm001.o] Error 1
> make[4]: Leaving directory `/build/buildd/lcdproc-0.4.3/server/drivers'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/buildd/lcdproc-0.4.3/server'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/lcdproc-0.4.3'
> make[1]: *** [all-recursive-am] Error 2
> make[1]: Leaving directory `/build/buildd/lcdproc-0.4.3'
> make: *** [build-stamp] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=mipsel&pkg=lcdproc&ver=0.4.3-12

Preprocessed source to follow.




a problem with building ocaml on sparc with gcc 3.2 ...

2003-01-31 Thread Sven Luther
Hello, ...

I encounter this problem when building ocaml with gcc 3.2 on sparc :

boot/ocamlrun boot/ocamlc -nostdlib -I boot  -linkall -o ocaml.tmp 
toplevel/toplevellib.cma toplevel/topstart.cmo
make[1]: *** [ocaml] Bus error
make[1]: Leaving directory `/home/luther/ocaml-3.06'
make: *** [build-stamp] Error 2


Well, you may say that this is an ocaml problem and has nothing to do
with gcc, but with gcc 2.95, it works fine, and the boot/ocamlrun and
boot/ocamlc executables are the first ones, built with gcc from c
sources.

I contacted upstream about it, but got no reply so far, and well, since
gcc 3.2 is now our official gcc, i think it is important that this is
solved.

I know nothing about sparcs, nor the gcc internals, but in order to
investigate this more deeply, could someone give me a hint of what is
causing this Bus error (well, not what is causing the problem in this
precise case, altough that would be fine too, but what is causing it in
general) so i know what i am looking for in the source code.

Notice, that ocamlc builds fine with gcc 3.2 on all the other arches, if
i am not wrong.

Thanks in advance for any help you may give me.

Friendly,

Sven Luther




Re: GCC 3.3, GCC 3.4

2003-01-31 Thread Mark Mitchell

--On Thursday, January 30, 2003 04:52:41 PM -0800 Zack Weinberg 
<[EMAIL PROTECTED]> wrote:

I'm relaying this to the LSB working group in charge of C++ and also
to the Debian gcc team -- Debian is presently in the process of
transitioning to the 3.2 ABI and I am pretty sure they also were
operating under the assumption that it would not change ever again.
I know that we will change the C++ ABI a little bit more.  Here are
the two areas that I know are buggy, and are buggy in ways that affect
correctness:
- Name mangling
 Due to not being able to know exactly what's a dependent name and
 what's not, there are some (obscure) cases involving templates where
 we cannot really produce the right name given what we have now.
 These cases are sufficiently odd that I'm not sure anyone will ever
 run into them in real code.  For example, I doubt they come up in
 V3.
- Object layout
 For the most part, these are bugs involving empty class conflicts.  As
 far as I know, we've fixed all of these -- I do not know of any more
 and I know we've looked pretty hard, in various ways.  There is also at
 least one bug involving virtual bases that might be somewhat more common.
I think the thing to do is wait until we are very confident that we've
finally nailed the name mangling issues and until the V3 people they've
nailed the runtime issues and then change the defaults.  I don't know
much about the runtime side, but on the compiler side, I expect that
few people will notice.
To some extent, I think there's a communication issue.  We (rightly) take
seriously *any* ABI change, but some are a lot more serious than others.
These are more like "If you have more than 32 parameters to a
function, and 14 of them are floats, and 18 are long doubles, and you
use varargs, then we quite match the spec" than "the size of int
will be now be 5" or "floating point values will now be passed on the
stack."
If we just said "this new version fixes a bug where two empty classes
of the same type can end up at the same address", people probably
wouldn't worry much -- but saying "we're breaking the C++ ABI" makes
them worry.  Both perspectives are correct: they should worry, but not
*too* much.
--
Mark Mitchell[EMAIL PROTECTED]
CodeSourcery, LLChttp://www.codesourcery.com



Processing of gcc-3.2_3.2.2ds7-0pre8_i386.changes

2003-01-31 Thread Archive Administrator
gcc-3.2_3.2.2ds7-0pre8_i386.changes uploaded successfully to localhost
along with the files:
  gcc-3.2_3.2.2ds7-0pre8.dsc
  gcc-3.2_3.2.2ds7-0pre8.diff.gz
  cpp-3.2-doc_3.2.2-0pre8_all.deb
  libstdc++5-doc_3.2.2-0pre8_all.deb
  g77-3.2-doc_3.2.2-0pre8_all.deb
  gnat-3.2-doc_3.2.2-0pre8_all.deb
  gpc-2.1-3.2-doc_3.2.2.20021128-0pre8_all.deb
  gcc-3.2-doc_3.2.2-0pre8_all.deb
  gcc-3.2-base_3.2.2-0pre8_i386.deb
  libgcc1_3.2.2-0pre8_i386.deb
  cpp-3.2_3.2.2-0pre8_i386.deb
  protoize_3.2.2-0pre8_i386.deb
  fixincludes_3.2.2-0pre8_i386.deb
  gobjc-3.2_3.2.2-0pre8_i386.deb
  libobjc1_3.2.2-0pre8_i386.deb
  gij-3.2_3.2.2-0pre8_i386.deb
  libgcj-common_3.2.2-0pre8_i386.deb
  libgcj3_3.2.2-0pre8_i386.deb
  gcj-3.2_3.2.2-0pre8_i386.deb
  libgcj3-dev_3.2.2-0pre8_i386.deb
  fastjar_3.2.2-0pre8_i386.deb
  libffi2_3.2.2-0pre8_i386.deb
  libffi2-dev_3.2.2-0pre8_i386.deb
  g++-3.2_3.2.2-0pre8_i386.deb
  libstdc++5_3.2.2-0pre8_i386.deb
  libstdc++5-dev_3.2.2-0pre8_i386.deb
  libstdc++5-pic_3.2.2-0pre8_i386.deb
  libstdc++5-dbg_3.2.2-0pre8_i386.deb
  libg2c0_3.2.2-0pre8_i386.deb
  g77-3.2_3.2.2-0pre8_i386.deb
  gnat-3.2_3.2.2-0pre8_i386.deb
  libgnat3.15a_3.2.2-0pre8_i386.deb
  gpc-2.1-3.2_3.2.2.20021128-0pre8_i386.deb
  gcc-3.2_3.2.2-0pre8_i386.deb

Greetings,

Your Debian queue daemon




gcc-3.2_3.2.2ds7-0pre8_i386.changes REJECTED

2003-01-31 Thread Debian Installer

Rejected: gcc-3.2_3.2.2ds7-0pre8.dsc refers to gcc-3.2_3.2.2ds7.orig.tar.gz, 
but I can't find it in the queue or in the pool.


===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.

Your rejected files are in incoming/REJECT/.  (Some may also be in
incoming/ if your .changes file was unparsable.)  If only some of the
files need to repaired, you may move any good files back to incoming/.
Please remove any bad files from incoming/REJECT/.




gcc-3.2_3.2.2ds7-0pre8_i386.changes ACCEPTED

2003-01-31 Thread Debian Installer

Accepted:
cpp-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre8_all.deb
cpp-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre8_i386.deb
fastjar_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre8_i386.deb
fixincludes_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre8_i386.deb
g++-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre8_i386.deb
g77-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre8_all.deb
g77-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre8_i386.deb
gcc-3.2-base_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2-base_3.2.2-0pre8_i386.deb
gcc-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/gcc-3.2-doc_3.2.2-0pre8_all.deb
gcc-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2-0pre8_i386.deb
gcc-3.2_3.2.2ds7-0pre8.diff.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.diff.gz
gcc-3.2_3.2.2ds7-0pre8.dsc
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.dsc
gcc-3.2_3.2.2ds7.orig.tar.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7.orig.tar.gz
gcj-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcj-3.2_3.2.2-0pre8_i386.deb
gij-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gij-3.2_3.2.2-0pre8_i386.deb
gnat-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/gnat-3.2-doc_3.2.2-0pre8_all.deb
gnat-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gnat-3.2_3.2.2-0pre8_i386.deb
gobjc-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gobjc-3.2_3.2.2-0pre8_i386.deb
gpc-2.1-3.2-doc_3.2.2.20021128-0pre8_all.deb
  to pool/main/g/gcc-3.2/gpc-2.1-3.2-doc_3.2.2.20021128-0pre8_all.deb
gpc-2.1-3.2_3.2.2.20021128-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gpc-2.1-3.2_3.2.2.20021128-0pre8_i386.deb
libffi2-dev_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libffi2-dev_3.2.2-0pre8_i386.deb
libffi2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libffi2_3.2.2-0pre8_i386.deb
libg2c0_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libg2c0_3.2.2-0pre8_i386.deb
libgcc1_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libgcc1_3.2.2-0pre8_i386.deb
libgcj-common_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libgcj-common_3.2.2-0pre8_i386.deb
libgcj3-dev_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libgcj3-dev_3.2.2-0pre8_i386.deb
libgcj3_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libgcj3_3.2.2-0pre8_i386.deb
libgnat3.15a_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libgnat3.15a_3.2.2-0pre8_i386.deb
libobjc1_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libobjc1_3.2.2-0pre8_i386.deb
libstdc++5-dbg_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libstdc++5-dbg_3.2.2-0pre8_i386.deb
libstdc++5-dev_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libstdc++5-dev_3.2.2-0pre8_i386.deb
libstdc++5-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/libstdc++5-doc_3.2.2-0pre8_all.deb
libstdc++5-pic_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libstdc++5-pic_3.2.2-0pre8_i386.deb
libstdc++5_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/libstdc++5_3.2.2-0pre8_i386.deb
protoize_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/protoize_3.2.2-0pre8_i386.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 179128 


Thank you for your contribution to Debian.




Bug#179128: marked as done (libstdc++5-dev: depends on libc12-dev, which only NetBSD has)

2003-01-31 Thread Debian Bug Tracking System
Your message dated Fri, 31 Jan 2003 16:49:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#179128: fixed in gcc-3.2 1:3.2.2ds7-0pre8
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 31 Jan 2003 01:20:45 +
>From [EMAIL PROTECTED] Thu Jan 30 19:20:44 2003
Return-path: <[EMAIL PROTECTED]>
Received: from 216-15-37-107.c3-0.161-ubr3.lnh-161.md.cable.rcn.com 
(ucko.debian.net) [216.15.37.107] (foobar)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18ePrH-00023X-00; Thu, 30 Jan 2003 19:20:43 -0600
Received: from amu by ucko.debian.net with local (Exim 3.36 #1 (Debian))
id 18ePrH-0006k5-00; Thu, 30 Jan 2003 20:20:43 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Aaron M. Ucko" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libstdc++5-dev: depends on libc12-dev, which only NetBSD has
X-Mailer: reportbug 2.10
Date: Thu, 30 Jan 2003 20:20:42 -0500
Message-Id: <[EMAIL PROTECTED]>
Sender: "Aaron M. Ucko" <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.6 required=5.0
tests=SPAM_PHRASE_00_01
version=2.41
X-Spam-Level: 

Package: libstdc++5-dev
Version: 1:3.2.2-0pre7
Severity: grave
Tags: sid
Justification: renders package unusable

libstdc++5-dev seems to have gained a dependency on libc12-dev, which
AFAICT only exists on Debian GNU/NetBSD; could you please
conditionalize it accordingly?

Likewise for libgcj3-dev and libffi2-dev.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux tux 2.4.20 #1 Wed Dec 25 15:38:48 EST 2002 i686
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages libstdc++5-dev depends on:
ii  g++-3.21:3.2.2-0pre6 The GNU C++ compiler
ii  gcc-3.2-base   1:3.2.2-0pre7 The GNU Compiler Collection (base 
ii  libc6-dev  2.3.1-10  GNU C Library: Development Librari
ii  libstdc++5 1:3.2.2-0pre7 The GNU Standard C++ Library v3

-- no debconf information


---
Received: (at 179128-close) by bugs.debian.org; 31 Jan 2003 21:53:04 +
>From [EMAIL PROTECTED] Fri Jan 31 15:53:04 2003
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18ej5s-0003Rb-00; Fri, 31 Jan 2003 15:53:04 -0600
Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian))
id 18ej2E-0007XE-00; Fri, 31 Jan 2003 16:49:18 -0500
From: Ryan Murray <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.29 $
Subject: Bug#179128: fixed in gcc-3.2 1:3.2.2ds7-0pre8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 31 Jan 2003 16:49:18 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
gcc-3.2, which is due to be installed in the Debian FTP archive:

cpp-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre8_all.deb
cpp-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre8_i386.deb
fastjar_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre8_i386.deb
fixincludes_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre8_i386.deb
g++-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre8_i386.deb
g77-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre8_all.deb
g77-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre8_i386.deb
gcc-3.2-base_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2-base_3.2.2-0pre8_i386.deb
gcc-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/gcc-3.2-doc_3.2.2-0pre8_all.deb
gcc-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2-0pre8_i386.deb
gcc-3.2_3.2.2ds7-0pre8.diff.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.diff.gz
gcc-3.2_3.2.2ds7-0pre8.dsc
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.dsc
gcc-3.2_3.2.2ds7.orig.tar.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7.orig.tar.gz
gcj-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcj-3.2_3.2.2-0pre8_i386.deb
gij-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gij-3.2_3.2.2-0pre8_i386.deb
gnat-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/gnat-3.2-doc_3.2.2-0pre8_all.deb
gnat-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2

Bug#179129: marked as done (libstdc++5-dev: Upgradeing broken.)

2003-01-31 Thread Debian Bug Tracking System
Your message dated Fri, 31 Jan 2003 16:49:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#179128: fixed in gcc-3.2 1:3.2.2ds7-0pre8
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 31 Jan 2003 01:22:01 +
>From [EMAIL PROTECTED] Thu Jan 30 19:22:01 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mailout05.sul.t-online.com [194.25.134.82] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18ePsX-00026n-00; Thu, 30 Jan 2003 19:22:01 -0600
Received: from fwd10.sul.t-online.de 
by mailout05.sul.t-online.com with smtp 
id 18ePsS-0004bT-00; Fri, 31 Jan 2003 02:21:56 +0100
Received: from localhost ([EMAIL PROTECTED]) by fmrl10.sul.t-online.com
with esmtp id 18ePsS-06Am4uC; Fri, 31 Jan 2003 02:21:56 +0100
Received: from hunger by localhost with local (Exim 3.36 #1 (Debian))
id 18ePsQ-0008E8-00; Fri, 31 Jan 2003 02:21:54 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Tobias Hunger <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libstdc++5-dev: Upgradeing broken.
X-Mailer: reportbug 2.10
Date: Fri, 31 Jan 2003 02:21:54 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Tobias Hunger <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.6 required=5.0
tests=SPAM_PHRASE_00_01
version=2.41
X-Spam-Level: 

Package: libstdc++5-dev
Version: 1:3.2.2-0pre6
Severity: grave
Justification: renders package unusable

Here's what I get when upgrading libstdc++5-dev:

Sorry, but the following packages have unmet dependencies:
  libstdc++5-dev: Depends: libc12-dev but it is not installable
E: Sorry, broken packages

I hope it's not just my mirror being out of sync:-)


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux c3po 2.4.20-my-686 #1 Fri Dec 13 02:28:11 CET 2002 i686
Locale: LANG=C, [EMAIL PROTECTED]

Versions of packages libstdc++5-dev depends on:
ii  g++-3.21:3.2.2-0pre6 The GNU C++ compiler
ii  gcc-3.2-base   1:3.2.2-0pre7 The GNU Compiler Collection (base 
ii  libc6-dev  2.3.1-10  GNU C Library: Development Librari
ii  libstdc++5 1:3.2.2-0pre7 The GNU Standard C++ Library v3

-- no debconf information


---
Received: (at 179128-close) by bugs.debian.org; 31 Jan 2003 21:53:04 +
>From [EMAIL PROTECTED] Fri Jan 31 15:53:04 2003
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18ej5s-0003Rb-00; Fri, 31 Jan 2003 15:53:04 -0600
Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian))
id 18ej2E-0007XE-00; Fri, 31 Jan 2003 16:49:18 -0500
From: Ryan Murray <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.29 $
Subject: Bug#179128: fixed in gcc-3.2 1:3.2.2ds7-0pre8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 31 Jan 2003 16:49:18 -0500
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
gcc-3.2, which is due to be installed in the Debian FTP archive:

cpp-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre8_all.deb
cpp-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre8_i386.deb
fastjar_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre8_i386.deb
fixincludes_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre8_i386.deb
g++-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre8_i386.deb
g77-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre8_all.deb
g77-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre8_i386.deb
gcc-3.2-base_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2-base_3.2.2-0pre8_i386.deb
gcc-3.2-doc_3.2.2-0pre8_all.deb
  to pool/main/g/gcc-3.2/gcc-3.2-doc_3.2.2-0pre8_all.deb
gcc-3.2_3.2.2-0pre8_i386.deb
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2-0pre8_i386.deb
gcc-3.2_3.2.2ds7-0pre8.diff.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.diff.gz
gcc-3.2_3.2.2ds7-0pre8.dsc
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7-0pre8.dsc
gcc-3.2_3.2.2ds7.orig.tar.gz
  to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds7.orig.tar.gz
gcj-3.2_3.2.2-0pre8_i386.deb
  

Bug#176081: libgcj.so.3.0.0 has non-PIC static code linked in

2003-01-31 Thread Jack Howarth
   This should be fixed upstream now...

http://gcc.gnu.org/ml/gcc-patches/2003-01/msg02409.html




Results for 3.3 20030129 (prerelease) testsuite on sparc-unknown-linux-gnu

2003-01-31 Thread Matthias Klose
LAST_UPDATED: Wed Jan 29 21:58:55 UTC 2003

Native configuration is sparc-unknown-linux-gnu

=== g++ tests ===


Running target unix
FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link 
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o execute 
FAIL: g++.dg/lookup/using2.C  (test for errors, line 28)
FAIL: g++.dg/lookup/using2.C  (test for errors, line 44)
FAIL: g++.dg/lookup/using2.C (test for excess errors)
FAIL: g++.dg/other/do1.C  (test for errors, line 11)
FAIL: g++.dg/other/do1.C (test for excess errors)
XPASS: g++.dg/parse/angle-bracket.C  (test for bogus messages, line 7)
FAIL: g++.dg/parse/angle-bracket.C (test for excess errors)
FAIL: g++.dg/template/typename3.C (test for excess errors)
FAIL: g++.dg/warn/Wunused-2.C  (test for warnings, line 5)
FAIL: g++.law/profile1.C  Execution test
XPASS: g++.other/init5.C  Execution test

=== g++ Summary ===

# of expected passes7847
# of unexpected failures10
# of unexpected successes   2
# of expected failures  90
# of unresolved testcases   2
# of untested testcases 22
# of unsupported tests  16
/build/buildd/gcc-snapshot-20030129/build/gcc/testsuite/../g++ version 3.3 
20030129 (prerelease)

=== g77 tests ===


Running target unix

=== g77 Summary ===

# of expected passes1644
# of unsupported tests  8
/build/buildd/gcc-snapshot-20030129/build/gcc/testsuite/../g77 version 3.3 
20030129 (prerelease)

=== gcc tests ===


Running target unix
FAIL: gcc.dg/cpp/Wunused.c (test for excess errors)
FAIL: gcc.dg/cpp/trad/Wunused.c (test for excess errors)
FAIL: gcc.dg/20021014-1.c execution test
FAIL: gcc.dg/duff-2.c (test for excess errors)
FAIL: gcc.dg/uninit-C.c (test for excess errors)

=== gcc Summary ===

# of expected passes20621
# of unexpected failures5
# of expected failures  67
# of unsupported tests  151
/build/buildd/gcc-snapshot-20030129/build/gcc/xgcc version 3.3 20030129 
(prerelease)

=== objc tests ===


Running target unix
FAIL: objc.dg/naming-1.m  (test for errors, line 20)
FAIL: objc.dg/naming-1.m (test for excess errors)
FAIL: objc.dg/naming-2.m  (test for errors, line 7)
FAIL: objc.dg/naming-2.m (test for excess errors)

=== objc Summary ===

# of expected passes1149
# of unexpected failures4
/build/buildd/gcc-snapshot-20030129/build/gcc/xgcc version 3.3 20030129 
(prerelease)

=== libjava tests ===


Running target unix
FAIL: PR1343 compilation from bytecode
FAIL: PR1343 -O compilation from bytecode
WARNING: program timed out.
FAIL: SyncTest execution - gij test
WARNING: program timed out.
FAIL: SyncTest execution - bytecode->native test
WARNING: program timed out.
FAIL: SyncTest execution - gij test
WARNING: program timed out.
FAIL: SyncTest -O execution - bytecode->native test

=== libjava Summary ===

# of expected passes2915
# of unexpected failures6
# of expected failures  16
# of untested testcases 16
=== libstdc++-v3 tests ===


Running target unix
XPASS: 22_locale/collate_byname.cc execution test
XPASS: 22_locale/collate_members_char.cc execution test
XPASS: 22_locale/collate_members_wchar_t.cc execution test
XPASS: 22_locale/ctype_is_char.cc execution test
XPASS: 22_locale/ctype_is_wchar_t.cc execution test
XPASS: 22_locale/members.cc execution test
XPASS: 22_locale/messages_byname.cc execution test
XPASS: 22_locale/messages_members_char.cc execution test
XPASS: 22_locale/moneypunct_byname.cc execution test
XPASS: 22_locale/moneypunct_members_char.cc execution test
XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test
XPASS: 22_locale/numpunct_byname.cc execution test
XPASS: 22_locale/numpunct_members_char.cc execution test
XPASS: 22_locale/numpunct_members_wchar_t.cc execution test
FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors)

=== libstdc++-v3 Summary ===

# of expected passes439
# of unexpected failures1
# of unexpected successes   14
# of expected failures  13

Compiler version: 3.3 20030129 (prerelease) 
Platform: sparc-unknown-linux-gnu
configure flags: --host=sparc-linux -v 
--enable-languages=c,c++,java,f77,objc,ada --prefix=/usr/lib/gcc-snapshot 
--infodir=/share/info --mandir=/share/man --enable-shared --with-system-zlib 
--enable-nls --enable-__cxa_atexit --without-included-gettext 
--enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib 
--with-cpp-install-dir=bin --enable-objc-gc
BOOT_CFLAGS=-O2 

Patches that Debian applied in this version:

gcc-m68k-config:
  2002-11-25  Andreas Schwab  <[EMAIL PROTECTED]>
  
* config.gcc (m68k-*-linux*): Don't set extra_parts and gnu_ld,
should come from the generic *-*-l

woody gcc-2.95 test suite failures

2003-01-31 Thread Pigeon
Hi,

Using apt-get --compile source to build gcc-2.95 on my woody system, I
find that the test suite results give around 1560 "unexpected
failures" for gcc.

Bad compilation? Don't think so. Running the testsuite on the
precompiled version in the woody .deb gives the same result.

I would appreciate being given some idea as to what is going on here,
please!

It is notable that it takes 5-10 minutes to run the tests on
20001226-1.c, at nice -15 on a 1.5GHz Athlon, and takes nearly 30Mb.

Since the logs generated are huge, I won't send anything in unless
requested to do so.

Thanks,

Pigeon




Bug#179298: gcj-3.2: provide "jar" command with gcj

2003-01-31 Thread Simon Richter
Package: gcj-3.2
Version: 1:3.2.2-0pre5
Severity: wishlist

Hi,

it would be cool if the gcj package somehow made sure that a "jar"
command was available, either by depending on the "fastjar" package or
with a small shell script that calls the Java implementation.

Usually, fastjar is part of the gcc package, so when creating Makefiles,
I'd think I can expect to find a "jar" binary along with "gcj" or
"javac"; however this is not currently true for Debian.

   Simon

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux phobos 2.4.19 #1 Mit Okt 30 13:10:27 CET 2002 i486
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Versions of packages gcj-3.2 depends on:
ii  gcc-3.21:3.2.2-0pre7 The GNU C compiler
ii  gcc-3.2-base   1:3.2.2-0pre7 The GNU Compiler Collection (base 
ii  java-common0.16  Base of all Java packages
ii  libc6  2.3.1-9   GNU C Library: Shared libraries an
ii  libgcc11:3.2.2-0pre7 GCC support library
ii  libgcj31:3.2.2-0pre7 Java runtime library for use with 
ii  libgcj3-dev1:3.2.2-0pre5 Java development headers and stati
ii  zlib1g 1:1.1.4-9 compression library - runtime

-- no debconf information