Bug#103568: gcc-3.0_3.0.ds9-4(unstable): fails to build from source

2001-07-04 Thread James Troup
Package: gcc-3.0
Version: 3.0.ds9-4
Severity: serious

Help?

| Automatic build of gcc-3.0_3.0.ds9-4 on vore by sbuild/sparc 1.159
| Build started at 20010704-1955
| **

[...]

| ** Using build dependencies supplied by package:
| Build-Depends: m4, autoconf (>= 2.13), libtool, gawk, dejagnu (>= 1.4), 
bzip2, binutils (>= 2.10.1), debhelper (>= 3.0.25), gperf (>= 2.7-3), bison, 
flex, gettext, texinfo, zlib1g-dev, libgc5-dev [!avr !hurd-i386 !m68k]
| Build-Depends-Indep: doxygen, graphviz, sharutils
| Build-Conflicts: mawk, libgcc0, libgcc300

[...]

| /build/buildd/gcc-3.0-3.0.ds9/build/gcc/xgcc 
-B/build/buildd/gcc-3.0-3.0.ds9/build/gcc/ -B/usr/sparc-linux/bin/ 
-B/usr/sparc-linux/lib/ -isystem /usr/sparc-linux/include -shared 
.libs/libgcj.la-3.o -Wl,--whole-archive ../libffi/.libs/libfficonvenience.a 
./libltdl/.libs/libltdlc.a -Wl,--no-whole-archive  
-L/build/buildd/gcc-3.0-3.0.ds9/build/sparc-linux/libjava 
../libffi/.libs/libfficonvenience.a -lpthread ./libltdl/.libs/libltdlc.a -ldl   
-lc  -Wl,-soname -Wl,libgcj.so.2 -o .libs/libgcj.so.2.0.0
| /usr/bin/ld: .libs/libgcj.so.2.0.0: undefined versioned symbol name 
__register_frame_info@@GLIBC_2.0
| /usr/bin/ld: failed to set dynamic section sizes: Bad value
| collect2: ld returned 1 exit status
| make[5]: *** [libgcj.la] Error 1

A complete build log can be found at
http://vore.debian.org/~buildd/logs/gcc-3.0_3.0.ds9-4_20010704-1955

-- 
James




Processed: Re: Bug#101223: Undefined reference to 'cout'

2001-07-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> severity 101223 normal
Bug#101223: Undefined reference to 'cout'
Severity set to `normal'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)




Bug#103468: libgcj2: gij links to itself

2001-07-04 Thread Robert Bihlmeyer
[bug was a bit overzealous to send the report -- here's the --verbose edition]

~# ls -l /usr/bin/gij
lrwxrwxrwx1 root root   21 Jul  4 11:34 /usr/bin/gij -> 
/etc/alternatives/gij
~# ls -l /etc/alternatives/gij
lrwxrwxrwx1 root root   12 Jul  4 11:34 /etc/alternatives/gij 
-> /usr/bin/gij

The following patch to the postinst should be applied. Note that some
maintainer script should also remove the faulty /usr/bin/gij
alternative (current prerm only removes /usr/bin/gij-3.0)

diff -u libgcj2.postinst~ libgcj2.postinst
--- libgcj2.postinst~   Wed Jul  4 15:51:35 2001
+++ libgcj2.postinstWed Jul  4 15:51:35 2001
@@ -1,7 +1,7 @@
 #! /bin/sh
 
 update-alternatives \
---install /usr/bin/gij gij /usr/bin/gij 300 \
+--install /usr/bin/gij gij /usr/bin/gij-3.0 300 \
 --slave /usr/share/man/man1/gij.1.gz gij.1.gz 
/usr/share/man/man1/gij-3.0.1.gz
 
 # Automatically added by dh_installdocs


-- 
Robbe




Bug#101223: Undefined reference to 'cout'

2001-07-04 Thread Gordon Sadler
severity 101223 normal
thanks

I see your point. It's not a packaging bug, and after moving the v3 ABI
.so and .a files to lib/gcc-lib/... it all works much better now.

I still think  gcc should be changed to generate a commandline for
collect2 that places -L$prefix/$gcclibdir before all other -L either
specified or implied by various environment variables. Unless someone
can give an example of when g++ 2.95.x would ever want to use a
different libstdc++ than the one it was built with? It should always
come first, or am I missing something?

On Wed, Jul 04, 2001 at 01:17:22AM +0200, Matthias Klose wrote:
> Gordon Sadler writes:
>  > Note below the order of the -L args. /usr/lib/gcc-lib/i386-linux/2.95.4
>  > comes last... Shouldn't it be first? Maybe a change to the specs? It so
>  > happens I have gcc-3 and libstdc++-v3 installed in /usr/local, so I can
>  > compile this on a few ways:
> 
> Ok, then gcc-2.95 picks the libstdc++.so (from gcc-3.0) from /usr/local and
> cannot find the symbol because it's mangled in another way?
> 
> This situation only occurs, if you have another libstdc++ in the link
> path, that is not compatible with the linker used. So the error should
> not occur, if you move the libstdc++.so (gcc-3.0's libstdc++) link
> into the compiler specific libdir. Correct?
> 
> I'd like to downgrade the report, because this is a situation that
> does not exist with the Debian g++-2.95 and g++-3.0 packages.
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 

-- 
Gordon Sadler





Bug#103468: libgcj2: gij links to itself

2001-07-04 Thread Robert Bihlmeyer
Package: libgcj2
Version: 1:3.0-4
Severity: normal

gij links to itself

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux hoss 2.4.4-fcaps-hoss #1 Fri May 25 19:29:24 CEST 2001 
i686 unknown

Versions of the packages libgcj2 depends on:
ii  libc6  2.2.3-6GNU C Library: Shared libraries and Timezone
ii  libgcc13.0-4  GCC support library.
ii  zlib1g 1.1.3-15   compression library - runtime




Processed: package has been removed, fix in newer version. can you close the bug?

2001-07-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 79984 gcc-3.0
Bug#79984: [fixed in gcc-2.97] wrong Standards-Version: field in debian/control
Bug reassigned from package `libgcj' to `gcc-3.0'.

> reassign 68560 gcc-3.0
Bug#68560: [fixed in gcc-2.97] PATCH: debian build problem: $(ENV)
Bug reassigned from package `libgcj0' to `gcc-3.0'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)




Bug#101878: marked as done (please remove ia64 gcc-defaults .deb's)

2001-07-04 Thread Debian Bug Tracking System
Your message dated Wed, 04 Jul 2001 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#101878: fixed
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.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 22 Jun 2001 07:04:12 +
>From [EMAIL PROTECTED] Fri Jun 22 02:04:12 2001
Return-path: <[EMAIL PROTECTED]>
Received: from merulo.external.hp.com (merulo.debian.org) 
[:::192.25.206.12] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15DKzE-0007Wi-00; Fri, 22 Jun 2001 02:04:12 -0500
Received: from winfree.gag.com [192.133.104.8] 
by merulo.debian.org with esmtp (Exim 3.22 1 (Debian))
id 15DKpq-00035B-00; Fri, 22 Jun 2001 00:54:30 -0600
Received: by winfree.gag.com (Postfix, from userid 1000)
id 58B5124C43; Fri, 22 Jun 2001 00:30:26 -0600 (MDT)
To: [EMAIL PROTECTED]
Subject: please remove ia64 gcc-defaults .deb's
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 22 Jun 2001 00:30:26 -0600 (MDT)
From: [EMAIL PROTECTED] (Bdale Garbee)
Delivered-To: [EMAIL PROTECTED]

Package: ftp.debian.org
Severity: serious

We have decided to try and release ia64 with woody using the 2.96+patches
version of gcc that is still the default in most of the IA-64 community, with
3.0 available as an option.  This means we need to "downgrade" the .deb files
derived from gcc-defaults.  While we're at it, we're cleaning up the set of 
.deb files delivered to reflect the pieces we're actually building now.

So, please remove the following from the archive:

pool/main/g/gcc-defaults/chill_2.95.3-7_ia64.deb
pool/main/g/gcc-defaults/cpp_3.0-3_ia64.deb
pool/main/g/gcc-defaults/g++_3.0-3_ia64.deb
pool/main/g/gcc-defaults/g77_3.0-3_ia64.deb
pool/main/g/gcc-defaults/gcc_3.0-3_ia64.deb
pool/main/g/gcc-defaults/gcj_3.0-3_ia64.deb
pool/main/g/gcc-defaults/gobjc_3.0-3_ia64.deb
pool/main/g/gcc-defaults/gpc_2.95.3-7_ia64.deb

Once you're done, we'll upload gcc-defaults products versioned 2.96-1.

This bug made release-critical since it must be resolved before woody release,
hopefully much sooner than that.  :-)

Thanks!

Bdale

---
Received: (at 101878-close) by bugs.debian.org; 4 Jul 2001 07:55:10 +
>From [EMAIL PROTECTED] Wed Jul 04 02:55:10 2001
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [:::206.246.226.45] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15HhV5-0005nS-00; Wed, 04 Jul 2001 02:55:07 -0500
Received: from rmurray by auric.debian.org with local (Exim 3.12 1 (Debian))
id 15HhNP-0006rx-00; Wed, 04 Jul 2001 03:47:11 -0400
From: Debian Archive Maintenance <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Melanie: $Revision: 1.14 $
Subject: Bug#101878: fixed
Message-Id: <[EMAIL PROTECTED]>
Sender: Ryan Murray <[EMAIL PROTECTED]>
Date: Wed, 04 Jul 2001 03:47:11 -0400
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 chill | 1:2.95.3-7 | ia64
   cpp |2:3.0-5 | ia64
   g++ |2:3.0-5 | ia64
   g77 |2:3.0-5 | ia64
   gcc |2:3.0-5 | ia64
   gcj |2:3.0-5 | ia64
 gobjc |2:3.0-5 | ia64
   gpc | 1:2.95.3-7 | ia64

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTE

Processed: your mail

2001-07-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 101878 gcc-defaults
Bug#101878: please remove ia64 gcc-defaults .deb's
Bug reassigned from package `ftp.debian.org' to `gcc-defaults'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)