Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?
* Adam Borowski <[EMAIL PROTECTED]> [2007-06-28 23:49]: > README.Debian says: > | You might also like to use a shell script to wrap up this > | funcationality, e.g. > | place in /usr/local/bin/gcc-snapshot and chmod +x it > but I see no reason why it couldn't simply be shipped in the package > outright. It's not like it invades anyone's namespace, etc. It would be > also consistent with all other gcc packages, all having the executable named > the same as the package. At least after having tested my stuff with gcc-4.2 > in the past, I didn't even suspect gcc-snapshot could be any different until > ./configure failed :p I know, it's like driving by memory, but in most > cases like this meeting people's assumptions is nice. > There's little reason to force people to some cut&paste work just to use > this package... doko, what do you think about this? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431045: g++-4.2: Template arguments to template functions not working
Package: g++-4.2
Version: 4.2-20070627-1
Severity: normal
I condensed the wfmath build failure with gcc-4.2 (#361815) into a small test
case:
frobnitz:/tmp# cat test.cc
#include
template class container>
int sum(const container& x) {
int result = 0;
for (typename container::const_iterator i = x.begin(); i != x.end();
i++) result += *i;
return result;
}
int test() {
std::vector x;
return sum(x);
}
frobnitz:/tmp# g++-4.1 -c test.cc
frobnitz:/tmp# g++-4.2 -c test.cc
test.cc: In function 'int test()':
test.cc:12: error: no matching function for call to 'sum(std::vector >&)'
frobnitz:/tmp# /usr/lib/gcc-snapshot/bin/g++ -c test.cc
test.cc: In function 'int test()':
test.cc:12: error: no matching function for call to 'sum(std::vector >&)'
--
Daniel Schepler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431045: More self-contained test case
Here's another variant of the test case not depending on the standard library:
template class A { public: T x1; U x2; };
template class container_with_x1>
int f(const container_with_x1& y) {
return y.x1;
}
int g() {
A y;
return f(y);
}
I guess on further reflection it's not quite clear whether this should work.
However, it does work with g++-4.1 but not with g++-4.2 or gcc-snapshot.
--
Daniel Schepler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428814: [powerpc] error: initializer element is not constant
severity 428814 critical
quit
On Thu, Jun 14, 2007 at 02:27:49PM +0200, Falk Hueffner wrote:
> Gerrit Pape <[EMAIL PROTECTED]> writes:
> > On a current Debian/powerpc sid system:
> >
> > $ cat >ttt.c < > static const double d[] = { 1.0l/6/1/2, -1.0l/30/3/4 };
> > int main() { return 0; }
> > EOT
> > $ gcc-4.1 ttt.c
> > ttt.c:1: error: initializer element is not constant
> > ttt.c:1: error: (near initialization for 'd[0]')
> > ttt.c:1: error: initializer element is not constant
> > ttt.c:1: error: (near initialization for 'd[1]')
>
> This is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26374
The dietlibc FTBFS because of this.
gcc-4.2 4.2-20070627-1 has the same problem, is there a workaround?
Thanks, Gerrit.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#428814: [powerpc] error: initializer element is not constant
Processing commands for [EMAIL PROTECTED]: > severity 428814 critical Bug#428814: [powerpc] error: initializer element is not constant Severity set to `critical' from `important' > quit 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]
Bug#431086: please support reverse cross build
Package: gcc-4.2 Version: 4.2-20070627-1 Severity: normal Tags: patch On Thu, 28 Jun 2007 14:47:55 +0200 Martin Michlmayr <[EMAIL PROTECTED]> wrote: > Throughout the development of GCC 4.2, we regularly recompiled the > entire Debian archive with development snapshots of GCC to make sure > that we'd end up with a reliable compiler. We have done regular > rebuilds on IA64 and AMD64, and we have tested almost every > architecture at some point during the development phase of 4.2 (the > exception being hppa and m68k, as well as non-Linux platforms). We > now have a compiler with relatively few known issues. One issue that arose during DebConf7 relates to an upstream behaviour of gcc that is not working inside the debian packaging code. Emdebian has been building cross-compiler toolchains for some time but in order to be able to build all Emdebian packages from source, we need to be able to cross build gcc, not to provide a cross compiler but to provide some core libraries - specifically libgcc1 and libstsdc++6-foo - cross built for a different host. e.g. Build=amd64|i386|powerpc Host=arm Target=arm compared to build=amd64|i386|powerpc host=amd64|i386|powerpc target=arm for a standard cross-compiler. As host==target this isn't a full canadian cross, more of a reverse cross. A normal arm-linux-gnu-gcc etc. toolchain is used to build these packages. The attached patches to debian/rules.defs and debian/rules2 provide support for these builds as well as outline support for a full canadian cross build. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.21-1-amd64 Debian Release: lenny/sid 500 unstablewww.linux.codehelp.co.uk 500 unstablewww.emdebian.org 500 unstableftp.uk.debian.org --- Package information. --- Depends (Version) | Installed ==-+-== gcc-4.2-base(= 4.2-20070627-1) | 4.2-20070627-1 cpp-4.2 (= 4.2-20070627-1) | 4.2-20070627-1 binutils (>= 2.17cvs20070426) | 2.17cvs20070426-8 libgcc1 (>= 1:4.2-20070627-1) | 1:4.2-20070627-1 libgomp1 (>= 4.2-20070627-1) | 4.2-20070627-1 libc6 (>= 2.5-5) | 2.5-11 -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ --- gcc-4.2.old/debian/rules.defs 2007-06-29 12:34:25.0 +0100 +++ gcc-4.2.cross/debian/rules.defs 2007-06-29 16:10:04.0 +0100 @@ -66,6 +66,28 @@ endif # --- +# full canadian +# typical cross-compiler +# reverse cross (built to run on the target) +# native +# +# build != host && host == target : reverse cross (REVERSE_CROSS == yes) +# build == host && host != target : typical cross (DEB_CROSS == yes) +# build != host && host != target : canadian (DEB_CROSS == yes) +# build == host && host == target : native +ifneq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) + ifneq ($(DEB_HOST_GNU_TYPE), $(DEB_TARGET_GNU_TYPE)) + DEB_CROSS = yes + else + REVERSE_CROSS = yes + endif + else + ifneq ($(DEB_HOST_GNU_TYPE), $(DEB_TARGET_GNU_TYPE)) + DEB_CROSS = yes + endif +endif + +# --- # which binary packages are built? # cross compiler support. If GCC_TARGET is set, then it's the architecture @@ -75,8 +97,7 @@ $(error GCC_TARGET value "$(GCC_TARGET)" is not a valid Debian architecture) endif -ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_TARGET_GNU_TYPE)) - DEB_CROSS = yes +ifdef DEB_CROSS # TP: Target Prefix. Used primarily as a prefix for cross tool # names (e.g. powerpc-linux-gcc). # TS: Target Suffix. Used primarily at the end of cross compiler @@ -700,6 +721,9 @@ ifdef DEB_CROSS with_check := disabled for cross compiler package endif +ifdef REVERSE_CROSS + with_check := disabled for reverse cross build +endif check_no_systems := hurd-i386 ifneq (, $(filter $(DEB_TARGET_GNU_SYSTEM),$(check_no_systems))) with_check := disabled for $(DEB_TARGET_GNU_SYSTEM) --- gcc-4.2.old/debian/rules2 2007-06-29 12:34:25.0 +0100 +++ gcc-4.2.cross/debian/rules2 2007-06-29 16:03:57.0 +0100 @@ -535,7 +535,9 @@ $(build_stamp): $(configure_stamp) $(build_locale_stamp) dh_testdir rm -f bootstrap-protocol +# DEB_CROSS is never set if REVERSE_CROSS is set and vice-versa. ifndef DEB_CROSS +ifndef REVERSE_CROSS ifeq ($(with_java),yes) ifeq ($(with_native_ecj),yes) : # prepare the standalone ecj jar @@ -608,6 +610,7 @@ ) 2>&1 | tee bootstrap-protocol s=`cat status`; rm -f status; test $$s -eq 0 endif +endif -chmod 755 $(srcdir)/contrib/warn_summary if [ -x $(srcdir)/contrib/warn_summary ]; then \ rm -f bootstrap-summary; \ pgpPpxrKiTnZM.pgp Description: PGP signature
Bug#431103: gnat from experimental is uninstallable
Package: gnat Version: 4.2.0-0 Severity: normal As the subject says: the version of gnat from experimental Depends on gnat-4.2, which is nowhere to be found, not even in NEW as far as I can tell. -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431045: Question about validity of wfmath template code
After analyzing a build failure of wfmath with gcc-4.2, I condensed the issue
it was having to the following test case:
template class A { public: T x1; U x2; };
template class container_with_x1>
int f(const container_with_x1& y) {
return y.x1;
}
int g() {
A y;
return f(y);
}
This code compiles with g++-4.1, but fails with g++-4.2 and the snapshot of
g++-4.3 currently in Debian's gcc-snapshot package. My question is: is this
valid code or not?
--
Daniel Schepler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcc-4.1 4.1.2-12 MIGRATED to testing
FYI: The status of the gcc-4.1 source package in Debian's testing distribution has changed. Previous version: 4.1.1ds2-21 Current version: 4.1.2-12 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gnat-4.1 4.1.2-8 MIGRATED to testing
FYI: The status of the gnat-4.1 source package in Debian's testing distribution has changed. Previous version: 4.1.1-22 Current version: 4.1.2-8 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package gcc-snapshot
# # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #430957 # * http://gcc.gnu.org/PR32540 # * remote status changed: (?) -> NEW usertags 430957 + status-NEW thanks
