Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote: > Matthias Klose writes: > > For all ports besides alpha and hppa we plan to make GCC-4.3 the > > default compilers for lenny. > > amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch > reenabling the cld instruction when stringops are used; this patch is > neither in the gcc-4_3-branch or in the trunk. I will revert this > patch once a fixed kernel is found in testing and there's no patch > applied in the upstream sources to avoid shipping a GCC which differs > in code generation from upstream. Isn't it risky for partial upgrades from etch ? Shouldn't we wait for lenny+1 to revert this ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472334: gcc-4.3: FTBFS on hurd-i386 because of symbol list
Package: gcc-4.3 Version: 4.3.0-1 Severity: important Hello, gcc-4.3 currently FTBFS because of differing symbol lists: dpkg-gensymbols: warning: debian/libstdc++6/DEBIAN/symbols doesn't match completely debian/libstdc++6.symbols.hurd-i386 --- dpkg-gensymbols2oOICF 2008-03-23 13:51:10.772865000 + +++ dpkg-gensymbolsFGx4wG 2008-03-23 13:51:10.772865000 + @@ -432,10 +432,12 @@ [EMAIL PROTECTED] 4.3 [EMAIL PROTECTED] 4.3 [EMAIL PROTECTED] 4.3 + [EMAIL PROTECTED] 4.3.0-1 [EMAIL PROTECTED] 4.3 [EMAIL PROTECTED] 4.3 [EMAIL PROTECTED] 4.3 [EMAIL PROTECTED] 4.3 + [EMAIL PROTECTED] 4.3.0-1 [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 @@ -1212,8 +1214,10 @@ [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 - [EMAIL PROTECTED] 4.1.1-21 - [EMAIL PROTECTED] 4.1.1-21 + [EMAIL PROTECTED] 4.3.0-1 +#MISSING: 4.3.0-1# [EMAIL PROTECTED] 4.1.1-21 + [EMAIL PROTECTED] 4.3.0-1 +#MISSING: 4.3.0-1# [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 [EMAIL PROTECTED] 4.1.1-21 dh_makeshlibs: command returned error code 256 I guess that the [EMAIL PROTECTED] 4.3.0-1 [EMAIL PROTECTED] 4.3.0-1 symbols could just be added to libstdc++6.symbols.hurd-i386, but for the __pthread_mutex/pthread_mutex_t difference we will probably have to move them to linux/hurd-specific files. (I guess the difference is due to hurd-i386 using typedef struct __pthread_mutex pthread_mutex_t; in its pthread.h) Samuel -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18.8-xen (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages gcc-4.3 depends on: ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina ii cpp-4.3 4.3.0-1 The GNU C preprocessor ii gcc-4.3-base4.3.0-1 The GNU Compiler Collection (base ii libc6 2.7-6GNU C Library: Shared libraries ii libgcc1 1:4.3.0-1GCC support library ii libgomp14.3.0-1 GCC OpenMP (GOMP) support library Versions of packages gcc-4.3 recommends: ii libc6-dev 2.7-6 GNU C Library: Development Librari -- no debconf information -- Samuel Now I know someone out there is going to claim, "Well then, UNIX is intuitive, because you only need to learn 5000 commands, and then everything else follows from that! Har har har!" (Andy Bates in comp.os.linux.misc, on "intuitive interfaces", slightly defending Macs.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote: > On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote: > > Matthias Klose writes: > > > For all ports besides alpha and hppa we plan to make GCC-4.3 the > > > default compilers for lenny. > > > > amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch > > reenabling the cld instruction when stringops are used; this patch is > > neither in the gcc-4_3-branch or in the trunk. I will revert this > > patch once a fixed kernel is found in testing and there's no patch > > applied in the upstream sources to avoid shipping a GCC which differs > > in code generation from upstream. > > Isn't it risky for partial upgrades from etch ? Shouldn't we wait for > lenny+1 to revert this ? I second that, please don't revert the patch until lenny+1. FWIW I believe the release team as a whole wanted the patch to be kept as well, but I'll let the other members correct me if I'm wrong. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgppVczXzW84q.pgp Description: PGP signature
Bug#472334: gcc-4.3: FTBFS on hurd-i386 because of symbol list
Samuel Thibault writes: > Package: gcc-4.3 > Version: 4.3.0-1 > Severity: important > > Hello, > > gcc-4.3 currently FTBFS because of differing symbol lists: please recheck with updated files in the packaging repository. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
> On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote: > > On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote: > > > Matthias Klose writes: > > > > For all ports besides alpha and hppa we plan to make GCC-4.3 the > > > > default compilers for lenny. > > >=20 > > > amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch > > > reenabling the cld instruction when stringops are used; this patch is > > > neither in the gcc-4_3-branch or in the trunk. I will revert this > > > patch once a fixed kernel is found in testing and there's no patch > > > applied in the upstream sources to avoid shipping a GCC which differs > > > in code generation from upstream.=20 > >=20 > > Isn't it risky for partial upgrades from etch ? Shouldn't we wait for > > lenny+1 to revert this ? > > I second that, please don't revert the patch until lenny+1. FWIW I > believe the release team as a whole wanted the patch to be kept as well, > but I'll let the other members correct me if I'm wrong. that's fine with me, as long as - the release team commits to maintain this patch - the release team commits to check every bug report filed against gcc with an upstream build and report back to the Debian BTS - the release team shows that it is able to do so, and has done so in the past. IMO the current opinions "Isn't it risky", "I second that" only look for the risk of running an unfixed kernel (if at all), not of shipping a compiler diverting in code generation from upstream. It has been pointed out that this bug is known to affect one package, which is not needed for an upgrade. Are you aware of others? An user and an administrator can be warned on an upgrade if he runs an unfixed kernel. I'll keep the GCC default at 4.2 for amd64 and i386 until this is resolved. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291374: Non-Prescriptive Natural Solution
Be well hung, thick and muscular within just weeks. http://www.Hithergspots.com/ Satisfaction Matters Most -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of gcc-defaults_1.66_multi.changes
gcc-defaults_1.66_multi.changes uploaded successfully to localhost along with the files: g++_4.3.0-1_powerpc.deb gobjc++-multilib_4.3.0-1_powerpc.deb gpc_2.1-4.1.2-16_sparc.deb g++-multilib_4.3.0-1_powerpc.deb gobjc++_4.3.0-1_sparc.deb libgnatprj-dev_4.3-4_sparc.deb gnat_4.3-4_powerpc.deb g++-multilib_4.3.0-1_sparc.deb libgnatvsn-dev_4.3-4_sparc.deb gfortran_4.3.0-1_sparc.deb gij_4.3.0-1_sparc.deb libgcj-common_4.3.0-1_sparc.deb gcc-defaults_1.66.tar.gz cpp_4.3.0-1_sparc.deb gcj_4.3.0-1_sparc.deb gcc_4.3.0-1_powerpc.deb gpc_2.1-4.1.2-16_powerpc.deb g++_4.3.0-1_sparc.deb gobjc-multilib_4.3.0-1_powerpc.deb g77_3.4.6-35_powerpc.deb libgcj-bc_4.3.0-1_powerpc.deb gpc-doc_2.1-4.1.2-16_sparc.deb gcc_4.3.0-1_sparc.deb gnat_4.3-4_sparc.deb cpp_4.3.0-1_powerpc.deb gcc-multilib_4.3.0-1_powerpc.deb gfortran-multilib_4.3.0-1_sparc.deb gdc_4.1.2-16_powerpc.deb gij_4.3.0-1_powerpc.deb gfortran-multilib_4.3.0-1_powerpc.deb gobjc-multilib_4.3.0-1_sparc.deb gobjc++_4.3.0-1_powerpc.deb g77_3.4.6-35_sparc.deb gcc-multilib_4.3.0-1_sparc.deb gfortran_4.3.0-1_powerpc.deb gpc-doc_2.1-4.1.2-16_powerpc.deb libgcj-common_4.3.0-1_powerpc.deb gcc-defaults_1.66.dsc gobjc_4.3.0-1_powerpc.deb libgnatprj-dev_4.3-4_powerpc.deb gcj_4.3.0-1_powerpc.deb gdc_4.1.2-16_sparc.deb gobjc++-multilib_4.3.0-1_sparc.deb gobjc_4.3.0-1_sparc.deb libgnatvsn-dev_4.3-4_powerpc.deb libgcj-bc_4.3.0-1_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcc-defaults_1.66_multi.changes ACCEPTED
Accepted: cpp_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/cpp_4.3.0-1_powerpc.deb cpp_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/cpp_4.3.0-1_sparc.deb g++-multilib_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/g++-multilib_4.3.0-1_powerpc.deb g++-multilib_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/g++-multilib_4.3.0-1_sparc.deb g++_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/g++_4.3.0-1_powerpc.deb g++_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/g++_4.3.0-1_sparc.deb g77_3.4.6-35_powerpc.deb to pool/main/g/gcc-defaults/g77_3.4.6-35_powerpc.deb g77_3.4.6-35_sparc.deb to pool/main/g/gcc-defaults/g77_3.4.6-35_sparc.deb gcc-defaults_1.66.dsc to pool/main/g/gcc-defaults/gcc-defaults_1.66.dsc gcc-defaults_1.66.tar.gz to pool/main/g/gcc-defaults/gcc-defaults_1.66.tar.gz gcc-multilib_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gcc-multilib_4.3.0-1_powerpc.deb gcc-multilib_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gcc-multilib_4.3.0-1_sparc.deb gcc_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gcc_4.3.0-1_powerpc.deb gcc_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gcc_4.3.0-1_sparc.deb gcj_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gcj_4.3.0-1_powerpc.deb gcj_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gcj_4.3.0-1_sparc.deb gdc_4.1.2-16_powerpc.deb to pool/main/g/gcc-defaults/gdc_4.1.2-16_powerpc.deb gdc_4.1.2-16_sparc.deb to pool/main/g/gcc-defaults/gdc_4.1.2-16_sparc.deb gfortran-multilib_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gfortran-multilib_4.3.0-1_powerpc.deb gfortran-multilib_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gfortran-multilib_4.3.0-1_sparc.deb gfortran_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gfortran_4.3.0-1_powerpc.deb gfortran_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gfortran_4.3.0-1_sparc.deb gij_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gij_4.3.0-1_powerpc.deb gij_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gij_4.3.0-1_sparc.deb gnat_4.3-4_powerpc.deb to pool/main/g/gcc-defaults/gnat_4.3-4_powerpc.deb gnat_4.3-4_sparc.deb to pool/main/g/gcc-defaults/gnat_4.3-4_sparc.deb gobjc++-multilib_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gobjc++-multilib_4.3.0-1_powerpc.deb gobjc++-multilib_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gobjc++-multilib_4.3.0-1_sparc.deb gobjc++_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gobjc++_4.3.0-1_powerpc.deb gobjc++_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gobjc++_4.3.0-1_sparc.deb gobjc-multilib_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gobjc-multilib_4.3.0-1_powerpc.deb gobjc-multilib_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gobjc-multilib_4.3.0-1_sparc.deb gobjc_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/gobjc_4.3.0-1_powerpc.deb gobjc_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/gobjc_4.3.0-1_sparc.deb gpc-doc_2.1-4.1.2-16_powerpc.deb to pool/main/g/gcc-defaults/gpc-doc_2.1-4.1.2-16_powerpc.deb gpc-doc_2.1-4.1.2-16_sparc.deb to pool/main/g/gcc-defaults/gpc-doc_2.1-4.1.2-16_sparc.deb gpc_2.1-4.1.2-16_powerpc.deb to pool/main/g/gcc-defaults/gpc_2.1-4.1.2-16_powerpc.deb gpc_2.1-4.1.2-16_sparc.deb to pool/main/g/gcc-defaults/gpc_2.1-4.1.2-16_sparc.deb libgcj-bc_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/libgcj-bc_4.3.0-1_powerpc.deb libgcj-bc_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/libgcj-bc_4.3.0-1_sparc.deb libgcj-common_4.3.0-1_powerpc.deb to pool/main/g/gcc-defaults/libgcj-common_4.3.0-1_powerpc.deb libgcj-common_4.3.0-1_sparc.deb to pool/main/g/gcc-defaults/libgcj-common_4.3.0-1_sparc.deb libgnatprj-dev_4.3-4_powerpc.deb to pool/main/g/gcc-defaults/libgnatprj-dev_4.3-4_powerpc.deb libgnatprj-dev_4.3-4_sparc.deb to pool/main/g/gcc-defaults/libgnatprj-dev_4.3-4_sparc.deb libgnatvsn-dev_4.3-4_powerpc.deb to pool/main/g/gcc-defaults/libgnatvsn-dev_4.3-4_powerpc.deb libgnatvsn-dev_4.3-4_sparc.deb to pool/main/g/gcc-defaults/libgnatvsn-dev_4.3-4_sparc.deb Override entries for your package: cpp_4.3.0-1_powerpc.deb - optional interpreters cpp_4.3.0-1_sparc.deb - optional interpreters g++-multilib_4.3.0-1_powerpc.deb - optional devel g++-multilib_4.3.0-1_sparc.deb - optional devel g++_4.3.0-1_powerpc.deb - optional devel g++_4.3.0-1_sparc.deb - optional devel g77_3.4.6-35_powerpc.deb - optional devel g77_3.4.6-35_sparc.deb - optional devel gcc-defaults_1.66.dsc - source devel gcc-multilib_4.3.0-1_powerpc.deb - optional devel gcc-multilib_4.3.0-1_sparc.deb - optional devel gcc_4.3.0-1_powerpc.deb - optional devel gcc_4.3.0-1_sparc.deb - optional devel gcj_4.3.0-1_powerpc.deb - optional devel gcj_4.3.0-1_sparc.deb - optional devel gdc_4.1.2-16_powerpc.deb - optional devel gdc_4.1.2-16_sparc.deb - optional devel gfortran-multilib_4.3.0-1_powerpc.deb - standard devel gfortran-multilib_4.3.0-1_sparc.deb - standard devel gfortran_4.3.0-1_powerpc.deb - optional devel gfortran_4.3.0-1_sparc.deb - optional devel gij_4.3.0-1_powerpc.deb - optional devel gij_4.3.0-1_sparc.d
gcc-defaults override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): gfortran-multilib_4.3.0-1_powerpc.deb: package says priority is optional, override says standard. gfortran-multilib_4.3.0-1_sparc.deb: package says priority is optional, override says standard. gobjc++-multilib_4.3.0-1_powerpc.deb: package says priority is optional, override says standard. gobjc++-multilib_4.3.0-1_sparc.deb: package says priority is optional, override says standard. gobjc-multilib_4.3.0-1_powerpc.deb: package says priority is optional, override says standard. gobjc-multilib_4.3.0-1_sparc.deb: package says priority is optional, override says standard. gpc-doc_2.1-4.1.2-16_powerpc.deb: package says section is doc, override says devel. gpc-doc_2.1-4.1.2-16_sparc.deb: package says section is doc, override says devel. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
epidemic of "FTBFS with GCC-4.3"
The gcc-4.3 distribution removes backward compatible include files, pre-iso header files that a large number of legacy C++ packages rely on. I'm wondering why such a major disruption in backward compatibility wasn't reserved for gcc-5.0. And I'm also wondering why the gcc packagers at Debian can't simply re-introduce these include files. Is there some technical reason, some conflict in moving forward with C++ that rules out the kind of backward compatibility offered for years by libstdc++? As an upstream developer I've struggled for years to keep stable C++ frameworks compiling with each new release of gcc. But gcc-4.3 raises the bar in terms of backward incompatibility. Can the Debian gcc community be of some help here? Why do more than 300 packages have to be altered and re-tested solely for the offense of originating in the earlier days of C++? It seems an unwise conservation of community resources. Scott Johnston http://www.ivtools.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
* Pierre Habouzit: >> Isn't it risky for partial upgrades from etch ? Shouldn't we wait for >> lenny+1 to revert this ? > > I second that, please don't revert the patch until lenny+1. FWIW I > believe the release team as a whole wanted the patch to be kept as well, > but I'll let the other members correct me if I'm wrong. What about fixing the etch kernel? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#117563: Jump on her twin peaks
Watch Britney moan and cry in pleasure and ecstasy. http://www.alogigubm.com/ Stick To What Works -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 07:23:10PM +, Florian Weimer wrote: > * Pierre Habouzit: > > >> Isn't it risky for partial upgrades from etch ? Shouldn't we wait for > >> lenny+1 to revert this ? > > > > I second that, please don't revert the patch until lenny+1. FWIW I > > believe the release team as a whole wanted the patch to be kept as well, > > but I'll let the other members correct me if I'm wrong. > > What about fixing the etch kernel? Sigh, could we avoid the same discussion over and over, people are not supposed (we never asked it in the past, and I see no valid reason to do so) to update to the last stable point release before upgrading to stable+1. Moreover we support the fact that people use custom kernels, or even vanilla ones, that don't have the fix. FWIW both the kernel and gcc need to have the fix: - the kernel because it's easy to backport (the patch is almost a one liner IIRC) and that it's an important fix; - gcc because we don't expect people to have a fixed kernel for their lennies. THe _BEST_ example of that are buildd's that for now run etch (even some sarge not so long time ago) and have a sid chroot to build. Not keeping the CLD patch means that we break our own buildd infrastructure. Yay. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpT4gAFb51Ok.pgp Description: PGP signature
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 08:23:10PM +0100, Florian Weimer wrote: > What about fixing the etch kernel? The kernel will get fixed. Bastian -- Each kiss is as the first. -- Miramanee, Kirk's wife, "The Paradise Syndrome", stardate 4842.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 04:54:29PM +, Matthias Klose wrote: > > On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote: > > > Isn't it risky for partial upgrades from etch ? Shouldn't we wait for > > > lenny+1 to revert this ? > > > > I second that, please don't revert the patch until lenny+1. FWIW I > > believe the release team as a whole wanted the patch to be kept as well, > > but I'll let the other members correct me if I'm wrong. > > that's fine with me, as long as > > - the release team commits to maintain this patch > - the release team commits to check every bug report filed against >gcc with an upstream build and report back to the Debian BTS > - the release team shows that it is able to do so, and has done so >in the past. This will last up to the lenny release, and the toolchain is to be freezed next week. So I don't > IMO the current opinions "Isn't it risky", "I second that" only look > for the risk of running an unfixed kernel (if at all), not of shipping > a compiler diverting in code generation from upstream. I'm sure all of this is because of the CLD patch: 1,5Mgcc-4.2-4.2.3/debian/patches > It has been pointed out that this bug is known to affect one package, > which is not needed for an upgrade. Are you aware of others? Yes, any package that runs memset/memmove in a signal handler. I happened to do that on software at work, those are not open source, but I would fail to see why we should not support them properly. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpJD6aYxSmrE.pgp Description: PGP signature
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 07:41:59PM +, Pierre Habouzit wrote: > On Sun, Mar 23, 2008 at 04:54:29PM +, Matthias Klose wrote: > > > On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote: > > > > Isn't it risky for partial upgrades from etch ? Shouldn't we wait for > > > > lenny+1 to revert this ? > > > > > > I second that, please don't revert the patch until lenny+1. FWIW I > > > believe the release team as a whole wanted the patch to be kept as well, > > > but I'll let the other members correct me if I'm wrong. > > > > that's fine with me, as long as > > > > - the release team commits to maintain this patch > > - the release team commits to check every bug report filed against > >gcc with an upstream build and report back to the Debian BTS > > - the release team shows that it is able to do so, and has done so > >in the past. > > This will last up to the lenny release, and the toolchain is to be > freezed next week. So I don't ... ... think you'll have to support that patch actively for too long. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpcFAaXrR7z1.pgp Description: PGP signature
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
> THe _BEST_ example of that are buildd's that for now run etch (even > some sarge not so long time ago) and have a sid chroot to build. Not > keeping the CLD patch means that we break our own buildd infrastructure. > Yay. No, this is not an argument. If a buildd is used to build packages for more than one release then it needs to be updated once lenny is released. You just need to upgrade earlier. Don't get kernels on the buildds get security related updates anyway? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
> > IMO the current opinions "Isn't it risky", "I second that" only look > > for the risk of running an unfixed kernel (if at all), not of shipping > > a compiler diverting in code generation from upstream. > > I'm sure all of this is because of the CLD patch: > 1,5M gcc-4.2-4.2.3/debian/patches there's no patch affecting code generation besides the CLD patch which is not found upstream. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
> > This will last up to the lenny release, and the toolchain is to be > > freezed next week. So I don't ... > ... think you'll have to support that patch actively for too long. wrong, once released with the patch you'll get bug reports for the compiler with the patch applied. For every report you need to recheck with a compiler without this patch. If you do want to do that until lenny+1 is released, please go ahead. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
* Matthias Klose ([EMAIL PROTECTED]) [080323 21:39]: > > > This will last up to the lenny release, and the toolchain is to be > > > freezed next week. So I don't ... > > ... think you'll have to support that patch actively for too long. > > wrong, once released with the patch you'll get bug reports for the > compiler with the patch applied. For every report you need to recheck > with a compiler without this patch. If you do want to do that until > lenny+1 is released, please go ahead. So we just need an (reliable) volunteer who checks every bug report in the Lenny gcc-4.3 whether the same happens with unmodified upstream (or with gcc-snapshot), and add the result to the bug report? What other qualifications are necessary? Does one need to understand assembler? Or is being able to compile debian packages and enough time to burn enough? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472334: gcc-4.3: FTBFS on hurd-i386 because of symbol list
Matthias Klose, le Sun 23 Mar 2008 17:35:40 +0100, a écrit : > Samuel Thibault writes: > > Package: gcc-4.3 > > Version: 4.3.0-1 > > Severity: important > > > > Hello, > > > > gcc-4.3 currently FTBFS because of differing symbol lists: > > please recheck with updated files in the packaging repository. Compiles fine, thanks! Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?
On Sun, Mar 23, 2008 at 08:46:15PM +0100, Matthias Klose wrote: > > THe _BEST_ example of that are buildd's that for now run etch (even > > some sarge not so long time ago) and have a sid chroot to build. Not > > keeping the CLD patch means that we break our own buildd infrastructure. > > Yay. > No, this is not an argument. If a buildd is used to build packages for > more than one release then it needs to be updated once lenny is > released. You just need to upgrade earlier. Don't get kernels on the > buildds get security related updates anyway? You had said you would revert the patch as soon as a fixed kernel was "in lenny". Having a fixed kernel "in lenny" does not mean that lenny is released, and the buildds will not be upgraded immediately after lenny's release -- there are a lot of buildds, this is something that takes time to manage. And even if the buildds get upgraded, shipping the upstream gcc-4.3 as the default compiler for lenny means lenny would be unsuitable as a development platform for code that needs to run on any systems with kernels older than our own. That's not a good thing. It's still my opinion that if this gcc-4.3 is not going to be backwards-compatible with existing kernels for lenny, we're better off not making gcc-4.3 the default compiler on the affected archs. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Results for 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) libjava testsuite on alpha-unknown-linux-gnu
LAST_UPDATED: Native configuration is alpha-unknown-linux-gnu === libjava tests === Running target unix FAIL: TestClosureGC run FAIL: pr11951 run FAIL: natgetargssize.cc compilation FAIL: natgetlocalvartable.cc compilation FAIL: natgetstacktrace.cc compilation FAIL: natevents.cc compilation FAIL: natgetallthreads.cc compilation FAIL: natgeterrorname.cc compilation FAIL: natgetmethodname.cc compilation FAIL: Array_3 execution - source compiled test FAIL: Array_3 -findirect-dispatch execution - source compiled test FAIL: Array_3 -O3 execution - source compiled test FAIL: Array_3 -O3 -findirect-dispatch execution - source compiled test FAIL: G19990303_02 execution - source compiled test FAIL: G19990303_02 -findirect-dispatch execution - source compiled test FAIL: G19990303_02 -O3 execution - source compiled test FAIL: G19990303_02 -O3 -findirect-dispatch execution - source compiled test FAIL: Invoke_1 execution - source compiled test FAIL: Invoke_1 -findirect-dispatch execution - source compiled test FAIL: Invoke_1 -O3 execution - source compiled test FAIL: Invoke_1 -O3 -findirect-dispatch execution - source compiled test FAIL: PR218 output - source compiled test FAIL: PR218 -O3 output - source compiled test FAIL: StackTrace2 execution - source compiled test FAIL: StackTrace2 -findirect-dispatch execution - source compiled test FAIL: StackTrace2 -O3 execution - source compiled test FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test FAIL: Throw_2 execution - source compiled test FAIL: Throw_2 -findirect-dispatch execution - source compiled test FAIL: Throw_2 -O3 execution - source compiled test FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test FAIL: Throw_3 output - source compiled test FAIL: Throw_3 -findirect-dispatch output - source compiled test FAIL: Throw_3 -O3 output - source compiled test FAIL: Throw_3 -O3 -findirect-dispatch output - source compiled test FAIL: initexc execution - source compiled test FAIL: initexc -findirect-dispatch execution - source compiled test FAIL: initexc -O3 execution - source compiled test FAIL: initexc -O3 -findirect-dispatch execution - source compiled test FAIL: invokethrow execution - source compiled test FAIL: invokethrow -findirect-dispatch output - source compiled test FAIL: invokethrow -O3 execution - source compiled test FAIL: invokethrow -O3 -findirect-dispatch output - source compiled test FAIL: pr83 -findirect-dispatch execution - source compiled test FAIL: pr83 -O3 -findirect-dispatch execution - source compiled test === libjava Summary === # of expected passes2464 # of unexpected failures45 # of untested testcases 30 Target: alpha-linux-gnu gcc version 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) Compiler version: 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) libjava Platform: alpha-unknown-linux-gnu configure flags: linux gnu,g BOOT_CFLAGS= Build Dependencies: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=--== ii binutils 2.18.1~cvs20080103-1 The GNU assembler, linker and binary utilities ii libc6.1 2.7-9GNU C Library: Shared libraries Patches that Debian applied in this version: svn-updates: updates from the 4.3 branch upto 20080321. gcc-textdomain: Set gettext's domain and textdomain to the versioned package name. gcc-driver-extra-langs: Add options and specs for languages that are not built from a source (but built from separate sources). gcc-hash-style-both: Link using --hash-style=both (alpha, amd64, ia64, i386, powerpc, ppc64, s390, sparc) libstdc++-pic: Build and install libstdc++_pic.a library. libstdc++-doclink: adjust hrefs to point to the local documentation libobjc-gc-link: Link libobjc_gc with libgcjgc_convenience.la. libjava-stacktrace: libgcj: Lookup source file name and line number in separated debug files found in /usr/lib/debug libjava-subdir: - Set the libjava sublibdir to /usr/lib/gcj-4.3 - Set the default libgcj database dir to /var/lib/gcj-4.3 libjava-jnipath: - Add /usr/lib/jni to java.library.path. - When running the i386 binaries on amd64, look in - /usr/lib32/gcj-x.y and /usr/lib32/jni instead. libjava-sjlj: Don't try to use _Unwind_Backtrace on SJLJ targets. See bug #387875, #388505, GCC PR 29206. libjava-rpath: - Link ecjx with -rpath \$(dbexecdir) libjava-jar: gjar: support @ arguments. libjava-soname: Bump the libgcj soversion. libjava-xulrunner1.9: Add configure check for xulrunner-1.9. libjava-realloc-leak: Don't leak upon failed realloc (taken from the trunk). libffi
Results for 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) testsuite on alpha-unknown-linux-gnu
LAST_UPDATED: Native configuration is alpha-unknown-linux-gnu === libffi tests === Running target unix === libffi Summary === # of expected passes1389 # of unsupported tests 10 === libgomp tests === Running target unix FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer (internal compiler error) FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer (test for excess errors) UNRESOLVED: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer compilation failed to produce executable FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-loops (internal compiler error) FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-loops (test for excess errors) UNRESOLVED: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-loops compilation failed to produce executable FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions (internal compiler error) FAIL: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions (test for excess errors) UNRESOLVED: libgomp.fortran/threadprivate3.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions compilation failed to produce executable FAIL: libgomp.fortran/threadprivate3.f90 -O3 -g (internal compiler error) FAIL: libgomp.fortran/threadprivate3.f90 -O3 -g (test for excess errors) UNRESOLVED: libgomp.fortran/threadprivate3.f90 -O3 -g compilation failed to produce executable === libgomp Summary === # of expected passes1715 # of unexpected failures8 # of unresolved testcases 4 === libstdc++ tests === Running target unix FAIL: abi_check XPASS: 26_numerics/headers/cmath/c99_classification_macros_c.cc (test for excess errors) === libstdc++ Summary === # of expected passes4932 # of unexpected failures1 # of unexpected successes 1 # of expected failures 59 # of unsupported tests 326 Target: alpha-linux-gnu gcc version 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) === g++ tests === Running target unix FAIL: g++.dg/ext/cleanup-10.C execution test FAIL: g++.dg/ext/cleanup-11.C execution test FAIL: g++.dg/ext/cleanup-8.C execution test FAIL: g++.dg/ext/cleanup-9.C execution test FAIL: g++.dg/torture/pr35526.C -O1 (internal compiler error) FAIL: g++.dg/torture/pr35526.C -O1 (test for excess errors) FAIL: g++.dg/torture/pr35526.C -O2 (internal compiler error) FAIL: g++.dg/torture/pr35526.C -O2 (test for excess errors) FAIL: g++.dg/torture/pr35526.C -O3 -fomit-frame-pointer (internal compiler error) FAIL: g++.dg/torture/pr35526.C -O3 -fomit-frame-pointer (test for excess errors) FAIL: g++.dg/torture/pr35526.C -O3 -g (internal compiler error) FAIL: g++.dg/torture/pr35526.C -O3 -g (test for excess errors) FAIL: g++.dg/torture/pr35526.C -Os (internal compiler error) FAIL: g++.dg/torture/pr35526.C -Os (test for excess errors) === g++ Summary === # of expected passes17393 # of unexpected failures14 # of expected failures 82 # of unsupported tests 139 /build/buildd/gcc-4.3-4.3.0/build/gcc/testsuite/g++/../../g++ version 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) === gcc tests === Running target unix FAIL: tmpdir-gcc.dg-struct-layout-1/t003 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: tmpdir-gcc.dg-struct-layout-1/t025 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/cleanup-10.c execution test FAIL: gcc.dg/cleanup-11.c execution test FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test FAIL: gcc.dg/pr17024-1.c (internal compiler error) FAIL: gcc.dg/pr17024-1.c (test for excess errors) FAIL: gcc.dg/pr28796-2.c (internal compiler error) FAIL: gcc.dg/pr28796-2.c (test for excess errors) UNRESOLVED: gcc.dg/pr28796-2.c compilation failed to produce executable FAIL: gcc.dg/pr33653.c scan-rtl-dump shorten "mem/v" FAIL: gcc.dg/struct-ret-3.c execution test === gcc Summary === # of expected passes45658 # of unexpected failures12 # of expected failures 91 # of unresolved testcases 1 # of untested testcases 35 # of unsupported tests 330 /build/buildd/gcc-4.3-4.3.0/build/gcc/xgcc version 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) === gfortran tests === Running target unix FAIL: gfortran.dg/default_format_1.f90 -O0 execution test FAIL: gfortran.dg/default_format_1.f90 -O1 execution test FAIL: gfortran.dg/default_format_1.f90 -O2 execution test FAIL: gfortran.dg/default_format_1.f90 -O3 -fomit-frame-pointer execution test FAIL: gfortran.dg/default_format_1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test FAIL: gfortran.dg/defaul
Results for 4.4.0 20080323 (experimental) [trunk revision 133461] (Debian 20080323-1) testsuite on i486-pc-linux-gnu
LAST_UPDATED: Sun Mar 23 14:12:16 UTC 2008 (revision 133461) Target: i486-linux-gnu gcc version 4.4.0 20080323 (experimental) [trunk revision 133461] (Debian 20080323-1) === acats tests === === acats Summary === # of expected passes2315 # of unexpected failures0 Native configuration is i486-pc-linux-gnu === g++ tests === Running target unix WARNING: Could not compile g++.dg/compat/struct-layout-1 generator === g++ Summary for unix === # of expected passes17411 # of expected failures 82 # of unsupported tests 88 Running target unix/-fstack-protector WARNING: Could not compile g++.dg/compat/struct-layout-1 generator === g++ Summary for unix/-fstack-protector === # of expected passes17411 # of expected failures 82 # of unsupported tests 88 Running target unix/-m64 WARNING: Could not compile g++.dg/compat/struct-layout-1 generator === g++ Summary for unix/-m64 === # of expected passes17321 # of expected failures 82 # of unsupported tests 120 === g++ Summary === # of expected passes52143 # of expected failures 246 # of unsupported tests 296 /scratch/packages/gcc/snap/gcc-snapshot-20080323/build/gcc/testsuite/g++/../../g++ version 4.4.0 20080323 (experimental) [trunk revision 133461] (Debian 20080323-1) === gcc tests === Running target unix WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Found latch edge" 5 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Merged latch edges" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "4 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "3 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "2 loops found" 1 === gcc Summary for unix === # of expected passes49013 # of unexpected failures5 # of expected failures 164 # of untested testcases 35 # of unsupported tests 376 Running target unix/-fstack-protector FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (internal compiler error) FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors) WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Found latch edge" 5 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Merged latch edges" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "4 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "3 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "2 loops found" 1 === gcc Summary for unix/-fstack-protector === # of expected passes49012 # of unexpected failures7 # of expected failures 164 # of untested testcases 35 # of unsupported tests 376 Running target unix/-m64 WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution,-fprofile-use -D_PROFILE_USE FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Found latch edge" 5 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "Merged latch edges" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "4 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "3 loops found" 2 FAIL: gcc.dg/tree-ssa/loop-25.c scan-tree-dump-times profile "2 loops found" 1 FAIL: gcc.misc-tests/linkage.c link === gcc Summary for unix/-m64 === # of expected passes48872 # of unexpected failures7 # of expected failures 163 # of unresolved testcases 1 # of untested testcases 35 # of unsupported tests 488 === gcc Summary === # of expected passes146897 # of unexpected failures19 # of expected failures 491 # of unresolved testcases 1 # of untested testcases 105 # of unsupported tests 1240 /scratch/packages/gcc/snap/gcc-snapshot-20080323/build/gcc/xgcc version 4.4.0 20080323 (experimental) [trunk revision 133461] (Debian 20080323-1) === gfortran tests === Running target unix FAIL: gfortran.dg/stat_1.f90 -O0 execution test FAIL: gfortran.dg/stat_1.f90 -O1 execution test FAIL: gfortran.dg/stat_1.f90 -O2 execution test FAIL: gfortran.dg/stat_1.f90 -O3 -fomit-frame-pointer execution test FAIL: gfortran.dg/stat_1.f90 -O3 -fomit-frame
Results for 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) libjava testsuite on powerpc-unknown-linux-gnu
LAST_UPDATED: Target: powerpc-linux-gnu gcc version 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) Native configuration is powerpc-unknown-linux-gnu === libjava tests === Running target unix === libjava Summary for unix === # of expected passes2550 Running target unix/-fstack-protector === libjava Summary for unix/-fstack-protector === # of expected passes2550 === libjava Summary === # of expected passes5100 Compiler version: 4.3.1 20080321 (prerelease) (Debian 4.3.0-2) libjava Platform: powerpc-unknown-linux-gnu configure flags: linux gnu,g BOOT_CFLAGS= Build Dependencies: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===--== ii binutils 2.18.1~cvs20080103-1 The GNU assembler, linker and binary utilities ii libc6 2.7-9 GNU C Library: Shared libraries Patches that Debian applied in this version: svn-updates: updates from the 4.3 branch upto 20080321. gcc-textdomain: Set gettext's domain and textdomain to the versioned package name. gcc-driver-extra-langs: Add options and specs for languages that are not built from a source (but built from separate sources). gcc-hash-style-both: Link using --hash-style=both (alpha, amd64, ia64, i386, powerpc, ppc64, s390, sparc) libstdc++-pic: Build and install libstdc++_pic.a library. libstdc++-doclink: adjust hrefs to point to the local documentation libobjc-gc-link: Link libobjc_gc with libgcjgc_convenience.la. libjava-stacktrace: libgcj: Lookup source file name and line number in separated debug files found in /usr/lib/debug libjava-subdir: - Set the libjava sublibdir to /usr/lib/gcj-4.3 - Set the default libgcj database dir to /var/lib/gcj-4.3 libjava-jnipath: - Add /usr/lib/jni to java.library.path. - When running the i386 binaries on amd64, look in - /usr/lib32/gcj-x.y and /usr/lib32/jni instead. libjava-sjlj: Don't try to use _Unwind_Backtrace on SJLJ targets. See bug #387875, #388505, GCC PR 29206. libjava-rpath: - Link ecjx with -rpath \$(dbexecdir) libjava-jar: gjar: support @ arguments. libjava-soname: Bump the libgcj soversion. libjava-xulrunner1.9: Add configure check for xulrunner-1.9. libjava-realloc-leak: Don't leak upon failed realloc (taken from the trunk). libffi-configure: Add --enable-libffi option to toplevel configure script pr28102: Apply proposed fix for PR target/28102. alpha-no-ev4-directive: boehm-gc-getnprocs: boehm-gc/pthread_support.c (GC_get_nprocs): Use sysconf as fallback. note-gnu-stack: Add .note.GNU-stack sections for gcc's crt files, libffi and boehm-gc Taken from FC. arm-unbreak-eabi-armv4t: Fix armv4t build on ARM libjava-armel-ldflags: Adjust libjava extra_ldflags for armel. pr24170: Fix PR libgcj/24170. pr28322: Fix PR other/28322, GCC new warnings and compatibility. gcc-i386-emit-cld: Emit cld instruction when stringops are used (i386). libssp-gnu: GNU/k*BSD support cpu-default-i486: set default 32bit ix86 architecture to i486 multiarch-include: biarch-include.dpatch Adds biarch include directories /usr/local/include/-linux-gnu /usr/include/-linux-gnu to the system include paths, depending on 32/64 bit mode. gcc-ice-hack: Retry the build on an ice, save the calling options and preprocessed source when the ice is reproducible. libjava-disable-static: Disable building the static libjava. gcc-ice-apport: Report an ICE to apport (if apport is available and the environment variable GCC_NOAPPORT is not set) libjava-nobiarch-check: For biarch builds, disable the testsuite for the non-default architecture for runtime libraries, which are not built by default (libjava). config-ml: disable some biarch libraries for biarch builds powerpc-biarch: enable biarch for 32 bit compiler Counting all warnings, there are 0 warnings in stage3 of this bootstrap. Number of warnings per file: Number of warning types: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356316: We Have Done All The Research for You
Be a tiger in bed and show her a real animal time. http://www.asestio.com/ Re: The truth about orgasms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340651: Define your masculine identity
Great experiences in bed start with this. http://www.sonstui.com/ Re: Coming over -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406550: Premier DVD és DivX filmek
Szia! Az ország legnagyobb warez letöltőhelye vár mindenkit! több 100 Premier film közül választhatsz, de megtalálhatod kedvenc játékaid, sorozataid is... több terra kiváló minőségű warezt találhatsz nálunk, profin, crc és egyéb hiba nélkül, megbízható sávszélességgel tölthetsz le. Válaszd ki a listából a kívánt filmet, programot és egy SMS elküldésével tölts le annyi adatot, amennyit csak tudsz, a meghatározott időn belül. Gyere és tölts akár ingyen is!!! http://kexx.netipar.hu ui.: Amennyiben megzavarta nyugalmadat levelünk, elnézésed kérjük érte.
