Processing of gcj-4.2_4.2.1-3_amd64.changes
gcj-4.2_4.2.1-3_amd64.changes uploaded successfully to localhost along with the files: gcj-4.2-base_4.2.1-3_amd64.deb gcj-4.2_4.2.1-3_amd64.deb gij-4.2_4.2.1-3_amd64.deb libgcj8-1_4.2.1-3_amd64.deb libgcj8-1-awt_4.2.1-3_amd64.deb gappletviewer-4.2_4.2.1-3_amd64.deb libgcj8-dev_4.2.1-3_amd64.deb libgcj8-dbg_4.2.1-3_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcj-4.2_4.2.1-3_amd64.changes ACCEPTED
Accepted: gappletviewer-4.2_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/gappletviewer-4.2_4.2.1-3_amd64.deb gcj-4.2-base_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/gcj-4.2-base_4.2.1-3_amd64.deb gcj-4.2_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/gcj-4.2_4.2.1-3_amd64.deb gij-4.2_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/gij-4.2_4.2.1-3_amd64.deb libgcj8-1-awt_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/libgcj8-1-awt_4.2.1-3_amd64.deb libgcj8-1_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/libgcj8-1_4.2.1-3_amd64.deb libgcj8-dbg_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/libgcj8-dbg_4.2.1-3_amd64.deb libgcj8-dev_4.2.1-3_amd64.deb to pool/main/g/gcj-4.2/libgcj8-dev_4.2.1-3_amd64.deb Override entries for your package: gappletviewer-4.2_4.2.1-3_amd64.deb - optional utils gcj-4.2-base_4.2.1-3_amd64.deb - optional libs gcj-4.2_4.2.1-3_amd64.deb - optional devel gij-4.2_4.2.1-3_amd64.deb - optional devel libgcj8-1-awt_4.2.1-3_amd64.deb - optional libs libgcj8-1_4.2.1-3_amd64.deb - optional libs libgcj8-dbg_4.2.1-3_amd64.deb - extra libdevel libgcj8-dev_4.2.1-3_amd64.deb - optional libdevel Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438504: info
Hi Martin, On Tue, Aug 21, 2007 at 07:55:17PM +0200, Martin Michlmayr wrote: >I can reproduce this with: > >/home/tbm/src/linux-2.6-2.6.21/debian/build/build-powerpc-none-powerpc >(sid)971:[EMAIL PROTECTED]: ..build-powerpc-none-powerpc] gcc-4.1 -nostdinc >-isystem /usr/lib/gcc/powerpc-linux-gnu/4.1.3/include -D__KERNEL__ -Iinclude >-include include/linux/autoconf.h -Iarch/powerpc -Iarch/powerpc/include -Wall >-Os -Iarch/powerpc-Idrivers/scsi -DMODULE -D"KBUILD_STR(s)=#s" >-D"KBUILD_BASENAME=KBUILD_STR(aic79xx_core)" >-D"KBUILD_MODNAME=KBUILD_STR(aic79xx)" -c -o >drivers/scsi/aic7xxx/.tmp_aic79xx_core.o drivers/scsi/aic7xxx/aic79xx_core.c >In file included from include/linux/aio.h:5, > from include/linux/sched.h:260, > from include/linux/blkdev.h:4, > from drivers/scsi/aic7xxx/aic79xx_osm.h:46, > from drivers/scsi/aic7xxx/aic79xx_core.c:44: >include/linux/workqueue.h: In function ‘cancel_delayed_work’: >include/linux/workqueue.h:203: warning: dereferencing type-punned pointer will >break strict-aliasing rules >In file included from drivers/scsi/aic7xxx/aic79xx_core.c:45: >drivers/scsi/aic7xxx/aic79xx_inline.h: In function ‘ahd_setup_data_scb’: >drivers/scsi/aic7xxx/aic79xx_inline.h:305: warning: dereferencing type-punned >pointer will break strict-aliasing rules >drivers/scsi/aic7xxx/aic79xx_core.c: In function ‘ahd_alloc_scbs’: >drivers/scsi/aic7xxx/aic79xx_core.c:6074: warning: dereferencing type-punned >pointer will break strict-aliasing rules >drivers/scsi/aic7xxx/aic79xx_core.c:6107: warning: dereferencing type-punned >pointer will break strict-aliasing rules >drivers/scsi/aic7xxx/aic79xx_core.c:6144: warning: dereferencing type-punned >pointer will break strict-aliasing rules >drivers/scsi/aic7xxx/aic79xx_core.c: In function ‘ahd_init’: >drivers/scsi/aic7xxx/aic79xx_core.c:6370: warning: dereferencing type-punned >pointer will break strict-aliasing rules >drivers/scsi/aic7xxx/aic79xx_core.c: At top level: >drivers/scsi/aic7xxx/aic79xx_core.c:9493: internal compiler error: >Segmentation fault >Please submit a full bug report, >with preprocessed source if appropriate. >See http://gcc.gnu.org/bugs.html> for instructions. >For Debian GNU/Linux specific bug reporting instructions, >see . > >Unfortunately, I cannot reproduce it with gcc-4.1 from current SVN, so >I'm not sure what to do about this. Which svn repository are you referring to? I would also like to give it a try. Well, if the current svn repository makes it to Sid, then this bug would be considered as fixed, wouldn't it? Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys & Net Admin signature.asc Description: Digital signature
Bug#438504: please help investigate potential gcc / kernel ICE on powerpc32 machines in lenny/sid.
Le mardi 21 août 2007 à 13:28 +0200, Sven Luther a écrit : > On Tue, Aug 21, 2007 at 01:25:32PM +0200, xavier grave wrote: > > Le mardi 21 août 2007 à 11:34 +0200, Sven Luther a écrit : > > > Hi, ... > > > > > > I ask for volunteers to help investigate the bug > > > > Hi, > > > > I have a debian unstable 32 bits (dual 1GHz G4) here at work, but no > > time for tests, I can create you an account on it if you want. > > What else do you need ? Do you want me to debootstrap some distributio > We have tested it on a powerbook and a mpc8349e-mitx board, but it seems > they don't believe in me or something, so what is really needed is an > independent test and confirmation. > > Could you do : > > apt-get build-dep linux-2.6 > apt-get source linux-2.6 > cd linux-2.6-2.6.22 > dpkg-buildpackage -rfakeroot -us -uc -B It worked here without PB. Here are some infos : ipnnarval:~/test_bug/linux-2.6-2.6.22# dpkg -l | grep gcc ii gcc 4:4.1.2-3 The GNU C compiler ii gcc-2.95 1:2.95.4-27The GNU C compiler ii gcc-3.2 1:3.2.3-9 The GNU C compiler ii gcc-3.2-base 1:3.2.3-9 The GNU Compiler Collection (base package) ii gcc-3.3 1:3.3.6-15 The GNU C compiler ii gcc-3.3-base 1:3.3.6-15 The GNU Compiler Collection (base package) ii gcc-3.4 3.4.6-6The GNU C compiler ii gcc-3.4-base 3.4.6-6The GNU Compiler Collection (base package) ii gcc-4.0 4.0.3-7The GNU C compiler ii gcc-4.0-base 4.0.3-7The GNU Compiler Collection (base package) ii gcc-4.0-locales 4.0.3-8The GNU C compiler (native language support files) ii gcc-4.1 4.1.2-15 The GNU C compiler ii gcc-4.1-base 4.1.2-15 The GNU Compiler Collection (base package) ii gcc-4.2-base 4.2.1-4The GNU Compiler Collection (base package) ii libgcc1 1:4.2.1-4 GCC support library Do you want me to do more tests ? xavier signature.asc Description: Ceci est une partie de message numériquement signée
Bug#426376: gcc-4.1: On EMT64/AMD64 platform warning are getting weird
Hello Martin,
Martin Michlmayr <[EMAIL PROTECTED]> wrote on 21/08/2007 19:50:32:
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2007-05-28 12:57]:
> > Package: gcc-4.1
> > Version: 4.1.1-21
> > Severity: important
> >
> > $ cat test.c
> > int f() { foo; }
> >
> > $ gcc -c test.c
> > test.c: In function â:
> > test.c:1: error: â undeclared (first use in this function)
>
> Do you still see this with current gcc-4.1? Because I don't.
This seems to be fixed now. Maybe some other upgrade triggered this bug to
off ?
/Xavier
Bug#438504: info
* Aurélien GÉRÔME <[EMAIL PROTECTED]> [2007-08-22 09:36]: > >Unfortunately, I cannot reproduce it with gcc-4.1 from current SVN, so > >I'm not sure what to do about this. > > Which svn repository are you referring to? I would also like to give > it a try. The GCC SVN repository, svn://gcc.gnu.org/svn/gcc/branches/gcc-4_1-branch > Well, if the current svn repository makes it to Sid, then this bug > would be considered as fixed, wouldn't it? Possibly, but maybe it's caused by a Debian-specific patch. -- Martin Michlmayr http://www.cyrius.com/
Bug#426376: marked as done (gcc-4.1: On EMT64/AMD64 platform warning are getting weird)
Your message dated Wed, 22 Aug 2007 11:00:05 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426376: gcc-4.1: On EMT64/AMD64 platform warning are
getting weird
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)
--- Begin Message ---
Package: gcc-4.1
Version: 4.1.1-21
Severity: important
$ cat test.c
int f() { foo; }
$ gcc -c test.c
test.c: In function â:
test.c:1: error: â undeclared (first use in this function)
test.c:1: error: (Each undeclared identifier is reported only once
test.c:1: error: for each function it appears in.)
This kind of errors appears only on x86_64 only, same code on x86 only
give
this output :
$ gcc -c test.c
test.c: In function 'f':
test.c:1: error: 'foo' undeclared (first use in this function)
test.c:1: error: (Each undeclared identifier is reported only once
test.c:1: error: for each function it appears in.)
/Xavier
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gcc-4.1 depends on:
ii binutils2.17-3 The GNU assembler, linker and
bina
ii cpp-4.1 4.1.1-21 The GNU C preprocessor
ii gcc-4.1-base4.1.1-21 The GNU Compiler Collection
(base
ii libc6 2.3.6.ds1-13 GNU C Library: Shared
libraries
ii libgcc1 1:4.1.1-21 GCC support library
ii libssp0 4.1.1-21 GCC stack smashing protection
libr
Versions of packages gcc-4.1 recommends:
ii libc6-dev 2.3.6.ds1-13 GNU C Library: Development
Librari
pn libmudflap0-dev(no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2007-08-22 10:31]:
> > Do you still see this with current gcc-4.1? Because I don't.
> This seems to be fixed now. Maybe some other upgrade triggered this bug to
> off ?
Seems like it. Let's close the bug.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
Processed: [bts-link] source package gcc-4.1
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #429657 > # * http://gcc.gnu.org/PR33142 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 429657 + fixed-upstream Bug#429657: gcc-4.1: optimisation bug abs() in nested if Tags were: upstream Tags added: fixed-upstream > usertags 429657 + status-RESOLVED resolution-FIXED Bug#429657: gcc-4.1: optimisation bug abs() in nested if There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package gcc-4.1
# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #429657 # * http://gcc.gnu.org/PR33142 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 429657 + fixed-upstream usertags 429657 + status-RESOLVED resolution-FIXED thanks
