Bug#382627: Building a cross-compiler for ia64 fails

Package: gcc-4.1 Version: 4.1.1-5 Severity: minor Tags: patch Hi, I tried to build a cross-toolchain for ia64, but when compiling gcc I got a linker error (log is attached). After searching for some time I found that Herbert Pötzl had already written a patch to solve this problem. I talked to

Processed: [bts-link] source package gcc-4.0

Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package gcc-4.0 # 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

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

Processing of gcj-4.1_4.1.1-11j1_m68k.changes

gcj-4.1_4.1.1-11j1_m68k.changes uploaded successfully to localhost along with the files: gcj-4.1-base_4.1.1-11j1_m68k.deb gcj-4.1_4.1.1-11j1_m68k.deb gij-4.1_4.1.1-11j1_m68k.deb libgcj7-0_4.1.1-11j1_m68k.deb libgcj7-awt_4.1.1-11j1_m68k.deb libgcj-bc_4.1.1-11j1_m68k.deb

Processing of gcj-4.1_4.1.1-11j1_s390.changes

gcj-4.1_4.1.1-11j1_s390.changes uploaded successfully to localhost along with the files: gcj-4.1-base_4.1.1-11j1_s390.deb gcj-4.1_4.1.1-11j1_s390.deb gij-4.1_4.1.1-11j1_s390.deb libgcj7-0_4.1.1-11j1_s390.deb libgcj7-awt_4.1.1-11j1_s390.deb libgcj-bc_4.1.1-11j1_s390.deb

gcj-4.1_4.1.1-11j1_s390.changes ACCEPTED

Accepted: gappletviewer-4.1_4.1.1-11j1_s390.deb to pool/main/g/gcj-4.1/gappletviewer-4.1_4.1.1-11j1_s390.deb gcj-4.1-base_4.1.1-11j1_s390.deb to pool/main/g/gcj-4.1/gcj-4.1-base_4.1.1-11j1_s390.deb gcj-4.1_4.1.1-11j1_s390.deb to pool/main/g/gcj-4.1/gcj-4.1_4.1.1-11j1_s390.deb

gcj-4.1_4.1.1-11j1_m68k.changes ACCEPTED

Accepted: gappletviewer-4.1_4.1.1-11j1_m68k.deb to pool/main/g/gcj-4.1/gappletviewer-4.1_4.1.1-11j1_m68k.deb gcj-4.1-base_4.1.1-11j1_m68k.deb to pool/main/g/gcj-4.1/gcj-4.1-base_4.1.1-11j1_m68k.deb gcj-4.1_4.1.1-11j1_m68k.deb to pool/main/g/gcj-4.1/gcj-4.1_4.1.1-11j1_m68k.deb

gcj-4.1_4.1.1-11j1_amd64.changes ACCEPTED

Accepted: gappletviewer-4.1_4.1.1-11j1_amd64.deb to pool/main/g/gcj-4.1/gappletviewer-4.1_4.1.1-11j1_amd64.deb gcj-4.1-base_4.1.1-11j1_amd64.deb to pool/main/g/gcj-4.1/gcj-4.1-base_4.1.1-11j1_amd64.deb gcj-4.1_4.1.1-11j1_amd64.deb to pool/main/g/gcj-4.1/gcj-4.1_4.1.1-11j1_amd64.deb

Welcome to Al-Manahel Newsletter List

The subscription of the email address: [EMAIL PROTECTED] To the mailing list: Al-Manahel Newsletter List is all set. Thanks for subscribing! Date of this subscription: Sat Aug 12 11:58:47 2006 Please save this email message for future reference.

Bug#382741: note.GNU-stack missing on powerpc

Package: gcc-4.1 Version: 4.1.1-5 Severity: important The note.GNU-stack and PT_GNU_STACK stuff apears to be missing on PowerPC. This contributes to insecurity on powerpc. After this gets fixed, the whole damn system needs to be rebuilt. I don't know where to request that. -- To UNSUBSCRIBE,

Bug#382746: powerpc libgcc writes code to the stack

Package: gcc-4.1 Version: 4.1.1-5 Severity: important __trampoline_setup in /lib/libgcc_s.so.1 puts code on the stack. This contributes to insecurity on powerpc. A half-way fix is to mmap a page for this evil crud. This still violates good practice, needing the OS to allow either write+execute

Bug#382748: broken -msecure-plt and -mbss-plt on powerpc

Package: gcc-4.1 Version: 4.1.1-5 Severity: important The -msecure-plt and -mbss-plt options are ignored. This contributes to insecurity on powerpc. (checked via md5sum: not one bit of difference) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact

Bug#382748: BTW, bug 382748 requires new binaries

I forgot to point out: Once this is fixed, all powerpc packages need to be rebuilt ASAP. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]