reopen 479950
notfixed 479950 1.0.78-2
thanks
Upgrading my system to current sid overwrote my java alternative again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, May 07, 2008 at 12:04:44PM +0200, Matthias Klose wrote:
> > After upgrading my system, a java program failed to run because the java
> > alternative was overwritten from the previously selected sun java.
>
> maybe this works for the simple case, but how is it technically
> possible to keep
Package: java-gcj-compat
Version: 1.0.78-1
Severity: serious
Justification: Policy 10.7.3
*** Please type your report below this line ***
After upgrading my system, a java program failed to run because the java
alternative was overwritten from the previously selected sun java.
-- System Informat
Package: libgnatprj4.1
Version: 4.1.0-2
Severity: serious
Justification: Policy 2.5
priority standard libgnatprj4.1 depends on optional libgnat-4.1.
I don't think ada or ada libraries should be priority standard.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
AP
= 4.1.0-2); however:
Version of gcc-4.1-base on system is 4.1.0-1.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
--
To UNSUBSCRIBE, email to [EMAIL
Package: gcc-3.4
Version: 3.4.5-1
Severity: serious
Justification: no longer builds from source
gcc-3.4 failed to build on a sparc buildd, duplicated on my sparc pbuilder.
if [ x"`case '-O2 -g -O2 -m64 -g -O2 -D_GNU_SOURCE -fno-implicit-templates
-m64' in *-fpic* ) echo -fpic ;; * ) echo -fPI
Package: gcc-snapshot
Version: 20051124-1
Severity: serious
Justification: no longer builds from source
gcc-snapshot still fails to buid from source on sparc. Now the error is:
checking for unistd.h... (cached) yes
checking for int... yes
checking size of int... configure: error: cannot compute
Package: gcc-snapshot
Version: 20051122-1
Severity: serious
Justification: no longer builds from source
gcc-snapshot failed to build on a sparc buildd, duplicated on my sparc
pbuilder.
Running configure in multilib subdirs 64
pwd: /build/buildd/gcc-snapshot-20051122/build/sparc-linux-gnu/libiber
Package: gcc-2.95
Version: 1:2.95.4-23
Severity: serious
Justification: no longer builds from source
gcc-2.95 failed to build on a sparc buildd, duplicated on my sparc
pbuilder.
if [ -x debian/patches/sparc-gcc4-fix.dpatch ]; then true; else chmod +x
debian/patches/sparc-gcc4-fix.dpatch; fi
if
Distribution: unstable
Urgency: low
Maintainer: Debian GCC maintainers
Changed-By: Blars Blarson <[EMAIL PROTECTED]>
Description:
chill-2.95 - The GNU CHILL compiler
cpp-2.95 - The GNU C preprocessor
cpp-2.95-doc - Documentation for the GNU C preprocessor (cpp)
g++-2.95 - The GNU C++ co
package gcc-2.95
tags 326506 + patch
thanks
Attached is the NMU patch to fix these ftbfs bugs. It builds on sparc,
I'll test the build on i386 before uploading.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Micr
Package: gcc-4.0
Version: 4.0.1-9
Severity: serious
Justification: fails to build from source
gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
pbuilder. Possible reasons for this include timestamp scew, more
recent kernel version on my pbuilder, and more recent
build-dependanc
Package: gcc-2.95
Version: 1:2.95.4-22
Severity: serious
Justification: fails to build from source
gcc-2.95 fails to build in a current sparc sid pbuilder chroot. It
looks like it may be using gcc-4.0 to compile code that isn't clean
enough for gcc-4.0.
cc -c -DIN_GCC -DHAIFA-g -DHAVE_CO
Package: g++-4.0
Version: 4.0.1-2
Severity: important
mysql-dfsg-4.1 fails to build on sparc due to a g++ interinal compiler
error:
if g++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr\""
-DDATADIR="\"/var/lib/mysql\"" -DSHAREDIR="\"/usr/share/mysql\""
-DHAVE_CONFIG_H -I. -I. -I.. -I../innobase/
tainer cced.)
The -V problem may just be an unrelated error anyway.
The main error was in the later use of gcc to link programs, which
failed on building both strace and ncurses.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.htm
linker and bina
ii cpp-3.3 1:3.3.5-13 The GNU C preprocessor
ii gcc-3.3-base1:3.3.5-13 The GNU Compiler Collection (base
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.0-9
After upgrading the kernel on my sparc pbuilder to 2.6.8-6, (sarge
version) I retried the build and it succeeded.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard
Package: gcc-3.3
Version: 1:3.3.6-2
Severity: serious
Tags: sid
Justification: fails to build from source
gcc-3.3 fails to build from source on sparc, duplicated on my sparc
pbuilder. (With the segmenetation fault line having 16604 rather than
23793 on it.)
if grep '^[^-]' "needed-options" > /d
Package: gcc-3.4
Version: 3.4.3-12.1
Severity: serious
Tags: sid
Justification: fails to build from source
gcc-3.4 failed to build from source on the sparc buildd. The ldd
error looks like it may be a known kernel bug fixed in current sarge
kernels on sparc, but not yet on vore.
dh_shlibdeps -
Package: gcc-snapshot
Version: 20050227-1
Severity: serious
Tags: sid
Justification: fails to build from source
gcc-snapshot fails to build from source, duplicated on sparc pbuilder.
/gcc-snapshot/sparc-linux-gnu/bin/ -B/usr/lib/gcc-snapshot/sparc-linux-gnu/lib/
-isystem /usr/lib/gcc-snapshot/s
dependancy stage.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
ics/complex/13450.cc execution test
FAIL: 26_numerics/complex/complex_value.cc execution test
FAIL: 26_numerics/complex/pow.cc execution test
make[1]: *** [stamps/06-check-stamp] Terminated
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.
Unless I'm totally misreading the bug, the problem is gcc needs to
conflict with g++ versions that are incompatable with it. Shouldn't
this be reopened and reassigned to gcc?
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/
Package: g++-3.2
Version: 1:3.2.3-4
Severity: minor
Tags: sid
After deleting the g++-3.3 dangling symlink, I'm getting:
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/i386-linux-g++-3.2.1 is a dangling symlink
-- System Information:
Debian Release: testing/unstable
Architecture: i3
> .../libdb2_2%3a2.7.7.0-3.1_i386.deb) ...
> Unpacking replacement libdb2 ...
> Replacing files in old package libc6 ...
>
> I suggest you try reassigning the bug to libdb2.
>
> p.
>
The other lines wern't errors, and if you require the pack
bc.so.6: version `GLIBC_2.2' not found (required by
> > /lib/libdb.so.3)
>
> This is NOT the first bug, why does perl print the error message?
You are welcome to look through the logs in
http://www.blars.org/obfucsate/ and find an earlier falure to blame if
you can
26 matches
Mail list logo
