Bug#176629: gij-3.2: package incorrctly provides java1-runtime

2003-01-14 Thread Stephen Zander
Package: gij-3.2
Version: 1:3.2.2-0pre5
Severity: important

According to the Java policy, packages that provide java1-runtime must
support the the complete java runtime environment.  As gij fails to
provide the java.awt.* classes, the provides on this package is
incorrect.  Please remove it until such time as gij has support for
java.awt.*.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pooh 2.4.19 #2 Wed Sep 11 21:14:15 PDT 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gij-3.2 depends on:
ii  gcc-3.2-base   1:3.2.2-0pre5 The GNU Compiler Collection (base 
ii  libc6  2.3.1-9   GNU C Library: Shared libraries an
ii  libgcc11:3.2.2-0pre5 GCC support library
ii  libgcj31:3.2.2-0pre5 Java runtime library for use with 
ii  zlib1g 1:1.1.4-9 compression library - runtime

-- no debconf information





Bug#176629: gij-3.2: package incorrctly provides java1-runtime

2003-01-14 Thread Matthias Klose
Stephen Zander writes:
> Package: gij-3.2
> Version: 1:3.2.2-0pre5
> Severity: important
> 
> According to the Java policy, packages that provide java1-runtime must
> support the the complete java runtime environment.  As gij fails to
> provide the java.awt.* classes, the provides on this package is
> incorrect.  Please remove it until such time as gij has support for
> java.awt.*.

so which runtimes do have complete awt support at all? The provides
was added to build all packages which do not relay on all awt
functionality. I would have to search the bug report ... what does the
java policy say for these cases?





Bug#176629: gij-3.2: package incorrctly provides java1-runtime

2003-01-14 Thread Ben Burton

> > According to the Java policy, packages that provide java1-runtime must
> > support the the complete java runtime environment.

Well, AFAICT (looking at policy linked to www.debian.org), the Java policy
isn't particularly explicit.  Section 2.1 states:

  Java virtual machines must provide java-virtual-machine and depend on
  java-common. They can also provide the runtime environment that the package
  contains (java1-runtime and/or java2-runtime). If it does not provide the
  files itself it must depend on the needed runtime environment.

My understanding is that the free JVMs are in various states of support for
java1 and java2.  For instance (and I could be wrong), gij support most but
not all of java1, but also supports a fair amount of java2.  The supported
runtime environment for any given JVM is not at all black and white.

If we're going to follow the policy so pedantically that the only JVMs
supporting java1-runtime are those that fill the entirity of Sun's java1
spec, I'd say we've defeated the purpose of these virtual packages.

For instance, most of the Java apps I maintain require some level of runtime
classes, so I can't just depend on java-virtual-machine.  But they pretty
much run on most/all free JVMs, and I'd like to acknowledge that and allow
the user choice in which JVM they use.  Do I then have to Depend: gij | kaffe
| sablevm | orp | etc etc etc?

I'd really like this issue to be resolved on [EMAIL PROTECTED] before JVMs
start removing java1-runtime from their provides lists as requested by these
bug reports.

If AWT specifically is going to be a big problem, perhaps even a third
virtual package: java1-runtime, java1-awt-runtime, java2-runtime?

CCing this to #176628 since a similar bug seems to have been filed on
sablevm.

Ben.




Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)

2003-01-14 Thread Junichi Uekawa

Hi,


To ensure some locales are available, I think you can use LOCPATH,
and create locales locally, so that the following are available:
  de_DE ISO-8859-1
  en_US ISO-8859-1
  fr_FR ISO-8859-1


see /usr/sbin/locale-gen on how to generate these locale data.


regards,
junichi




RE: elfutils vs debian gcc

2003-01-14 Thread Jack Howarth
   In case anyone is interested Jakub responded on this compile warning
in elfutils. RedHat apparently is backporting support for the
visibility attribute directive from gcc 3.3 into their gcc 3.2. The
other options are to use gcc 3.3 itself or, easiest, to not use
-Werror when building elfutils with stock gcc 3.2.2.
   Jack




Login wird gesperrt

2003-01-14 Thread anwahlt
Title: Unbenanntes Dokument






  
   
 
 
  
   
 
Hallo Du, suchst Du einen Neuen Partner der dich liebevoll 

verwöhnt und alles für Dich macht?
  Dann bist Du bei uns richtig.
Wir sind der größte Kontaktmarkt im Internet.
Es sind ständig neue Frauen und Männer in unserer Datenbank 

vorhanden. Wir führen derzeit 60.000 Frauen und Männer.
Schau doch mal vorbei.
  Möchtest Du Sie kennenlehrnen dann BITTE 
HIER KLICKEN
 
  Mit freundlichen Grüßen 
Kontakt 2003
  







0933fOrv9-321PirK6142NeIs4-551EkxS5489uYUo3-486wrnJ7710zrBa1-928ODYA0014hDKF4-l73




Login wird gesperrt

2003-01-14 Thread anwahlt
Title: Unbenanntes Dokument






  
   
 
 
  
   
 
Hallo Du, suchst Du einen Neuen Partner der dich liebevoll 

verwöhnt und alles für Dich macht?
  Dann bist Du bei uns richtig.
Wir sind der größte Kontaktmarkt im Internet.
Es sind ständig neue Frauen und Männer in unserer Datenbank 

vorhanden. Wir führen derzeit 60.000 Frauen und Männer.
Schau doch mal vorbei.
  Möchtest Du Sie kennenlehrnen dann BITTE 
HIER KLICKEN
 
  Mit freundlichen Grüßen 
Kontakt 2003
  







9073rnoF8-647SxPl5233GByL9-906VYNG6290qlnj0-658sRil47




Bug#176117: optimization/9258: [3.2/3.3/3.4 regression] ICE in compensate_edge, at reg-stack.c:2589

2003-01-14 Thread Janis Johnson
The regression show up with this patch:

Sat Jun 23 01:23:59 CEST 2001  Jan Hubicka  <[EMAIL PROTECTED]>

  * flow.c (mark_set_1, attempt_auto_inc, mark_used_reg,
  try_pre_increment_1): compute REG_FREQ using bb->frequency.

  * regclass.c (loop_cost): Kill.
  (frequency): New global variable.
  (record_operand_costs): Replace loop_cost by frequency.
  (scan_one_insn): Likewise.
  (regclass): Likewise; set frequency according to bb->frequency.

  * flow.c (split_edge): Set frequency.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9258







Results for 3.2.2 20030109 (Debian prerelease) testsuite on sparc-unknown-linux-gnu

2003-01-14 Thread Matthias Klose
LAST_UPDATED: Thu Jan  9 20:28:35 UTC 2003

Native configuration is sparc-unknown-linux-gnu

=== g++ tests ===


Running target unix
FAIL: g++.law/profile1.C  Execution test
XPASS: g++.other/init5.C  Execution test

=== g++ Summary ===

# of expected passes7336
# of unexpected failures1
# of unexpected successes   1
# of expected failures  88
# of untested testcases 22
# of unsupported tests  5
/build/buildd/gcc-3.2-3.2.2ds4/build/gcc/testsuite/../g++ version 3.2.2 
20030109 (Debian prerelease)

=== g77 tests ===


Running target unix

=== g77 Summary ===

# of expected passes1452
# of unsupported tests  8
/build/buildd/gcc-3.2-3.2.2ds4/build/gcc/testsuite/../g77 version 3.2.2 
20030109 (Debian prerelease)

=== gcc tests ===


Running target unix
FAIL: gcc.dg/20021014-1.c execution test

=== gcc Summary ===

# of expected passes18493
# of unexpected failures1
# of expected failures  66
# of unsupported tests  111
/build/buildd/gcc-3.2-3.2.2ds4/build/gcc/xgcc version 3.2.2 20030109 (Debian 
prerelease)

=== objc tests ===


Running target unix

=== objc Summary ===

# of expected passes1035
# of expected failures  6
/build/buildd/gcc-3.2-3.2.2ds4/build/gcc/xgcc version 3.2.2 20030109 (Debian 
prerelease)

=== libjava tests ===


Running target unix

=== libjava Summary ===

# of expected passes2061
# of expected failures  18
# of untested testcases 14
=== libstdc++-v3 tests ===


Running target unix
FAIL: 22_locale/codecvt_members_char_char.cc execution test
FAIL: 22_locale/codecvt_members_wchar_t_char.cc execution test
FAIL: 22_locale/ctor_copy_dtor.cc execution test
FAIL: 22_locale/ctype_to_char.cc execution test
FAIL: 22_locale/ctype_to_wchar_t.cc execution test
FAIL: 22_locale/facet.cc execution test
FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
FAIL: 27_io/ostream_inserter_arith.cc execution test

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

# of expected passes425
# of unexpected failures8
# of expected failures  26

Compiler version: 3.2.2 20030109 (Debian prerelease) 
Platform: sparc-unknown-linux-gnu
configure flags: --host=sparc-linux -v 
--enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr 
--mandir=/usr/share/man --infodir=/usr/share/info 
--with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib 
--enable-nls --without-included-gettext --enable-__cxa_atexit 
--enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc
BOOT_CFLAGS=-O2 

Patches that Debian applied in this version:

gcc-names:
  versioned gcc names

gcc-version:
  Add "(Debian)" to the gcc version string

fastjar-doc:
  Add fastjar(1) and grepjar(1) documentation

libstdc++-incdir:
  Propagate gxx_include_dir to the libstdc++ subdirectory.

libstdc++-codecvt:
  libstdc++-v3/include/bits/codecvt_specializations.h: add missing qualifiers

libstdc++-pic:
  Build and install libstdc++_pic.a library.

libstdc++-doclink:
  link local libstdc++ documentation to local source-level documentation 

gcj-debian-policy:
  add /usr/share/java/repository to the classpath.

gcj-names:
  versioned gcj info names

gcj-without-rpath:
  don't define runtime link path for java binaries and libraries

gcj-manpage:
  Fix typo in gcj documentation.

gij-classpath:
  Add -cp and -classpath options for gij(1).

backport-java-6865:
  2002-06-09  Tom Tromey  <[EMAIL PROTECTED]>
  
* parse.y (method_header): Give error message in all cases.
Fixes PR java/6865.

libffi-install:
  Allows libffi to be installed

deb-protoize:
  build protoize/unprotoize by default

libobjc:
  Find header file for Boehm garbage collector.

g77-names:
  versioned g77 names

ada-missing-lib:
  Diable usage auf addr2line library (currently not packaged for Debian)

ada-link-lib:
  - Install the shared Ada libraries as '.so.1', not '.so' to conform
  to the Debian policy.
  - Don't include a runtime link path (-rpath), when linking binaries.

ada-gcc-name:
  use gcc-3.2 instead of gcc and gnatXXX-3.15 instead of gnatXXX
  as the command names.

reporting:
   --help gives hint to /usr/share/doc/debian/bug-reporting.txt

Counting all warnings,
there are 280 warnings in stage3 of this bootstrap.

Number of warnings per file:
223 SYSCALLS.c
 23 gcc/combine.c
 10 gcc/regclass.c
  4 ./intdoc.texi
  3 gcc/gcc.c
  2 gcc/fold-const.c
  2 gcc/crtstuff.c
  2 gcc/ada/a-except.adb
  1 gcc/sched-deps.c
  1 gcc/reload.c
  1 gcc/profile.c
  1 gcc/objc/lang-specs.h
  1 gcc/java/jvspec.c
  1 gcc/function.c
  1 gcc/emit-rtl.c
  1 gcc/cp/lang-specs.h
  1 gcc/cp/init.c
  1 gcc/cp/class.c
  1 gcc/ada/adain

Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)

2003-01-14 Thread Matthias Klose
Junichi Uekawa writes:
> 
> Hi,
> 
> 
> To ensure some locales are available, I think you can use LOCPATH,
> and create locales locally, so that the following are available:
>   de_DE ISO-8859-1
>   en_US ISO-8859-1
>   fr_FR ISO-8859-1
> 
> 
> see /usr/sbin/locale-gen on how to generate these locale data.

ok, it's no problem to generate the data, but I cannot find any
reference to LOCPATH. Any hints?

Thanks, Matthias




Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)

2003-01-14 Thread Junichi Uekawa
> > To ensure some locales are available, I think you can use LOCPATH,
> > and create locales locally, so that the following are available:
> >   de_DE ISO-8859-1
> >   en_US ISO-8859-1
> >   fr_FR ISO-8859-1
> > 
> > 
> > see /usr/sbin/locale-gen on how to generate these locale data.
> 
> ok, it's no problem to generate the data, but I cannot find any
> reference to LOCPATH. Any hints?

I couldn't find any reference to LOCPATH either, but 
setlocale seems to look at directories specified by LOCPATH
in addition to (or instead of) the standard location (/usr/lib/locale)


One example execution of LOCPATH=/tmp strace locale gives me:

.
.
open("/usr/lib/locale/ja.eucJP/LC_IDENTIFICATION", O_RDONLY) = -1 ENOENT (No 
such file or directory)
open("/tmp/ja.eucjp/LC_IDENTIFICATION", O_RDONLY) = -1 ENOENT (No such file or 
directory)
open("/usr/lib/locale/ja.eucjp/LC_IDENTIFICATION", O_RDONLY) = -1 ENOENT (No 
such file or directory)
open("/tmp/ja/LC_IDENTIFICATION", O_RDONLY) = -1 ENOENT (No such file or 
directory)
open("/usr/lib/locale/ja/LC_IDENTIFICATION", O_RDONLY) = -1 ENOENT (No such 
file or directory)
.
.


I also found out that it is mostly undocumented, but apparently is a 
standard feature pretty much known by those who do know, so 
documentation is probably very lacking.


regards,
junichi