Your message dated Thu, 02 Mar 2017 23:00:29 +
with message-id
and subject line Bug#856452: fixed in gcc-7 7-20170302-1
has caused the Debian Bug report #856452,
regarding gcc-7: allow disabling brig via nolang DEB_BUILD_OPTIONS
to be marked as done.
This means that you claim that the
gcc-7-source
Architecture: source amd64 all
Version: 7-20170302-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Description:
cpp-7 - GNU C preprocessor
fixincludes - Fix non-ANSI header files
g++-7 - GNU C++ compiler
g++-7
Your message dated Thu, 02 Mar 2017 23:00:29 +
with message-id
and subject line Bug#856042: fixed in gcc-7 7-20170302-1
has caused the Debian Bug report #856042,
regarding gnat: please use SOURCE_DATE_EPOCH for reproducible ALI timestamps
to be marked as done.
This means that you claim that
Your message dated Thu, 02 Mar 2017 23:00:29 +
with message-id
and subject line Bug#844367: fixed in gcc-7 7-20170302-1
has caused the Debian Bug report #844367,
regarding Debian local ada patches need an update for GCC 7
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package gcc-defaults
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.deb
Package: gcc-multilib
Version: 4:6.3.0-1
Reading the package description for gcc-multilib (or
g++-multilib)
"A dependency package on architectures with multilib support;
the package contains dependencies for the non-default
multilib architecture(s)."
I have no idea what this package is good for.
binary:gcc-7-offload-nvptx is NEW.
binary:libgomp-plugin-nvptx1 is NEW.
binary:gcc-7-offload-nvptx is NEW.
binary:libgomp-plugin-nvptx1 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
Open
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430
--- Comment #31 from Vincent Lefèvre ---
There's something I don't understand: Whether -Wuninitialized or
-Wmaybe-uninitialized is used, I don't see any difference in the behavior of
GCC between
[...]
if (bar (i)) {
baz (&j);
}
[...]
an
gcc-7_7-20170302-1_amd64.changes uploaded successfully to localhost
along with the files:
gcc-7_7-20170302-1.dsc
gcc-7_7-20170302.orig.tar.gz
gcc-7_7-20170302-1.diff.gz
cpp-7-dbgsym_7-20170302-1_amd64.deb
cpp-7_7-20170302-1_amd64.deb
fixincludes-dbgsym_7-20170302-1_amd64.deb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430
--- Comment #30 from Manuel López-Ibáñez ---
(In reply to Richard Biener from comment #29)
> What remains seems to be complaining that
>
> int i;
> foo (&i);
>
> doesn't warn. And we have another bug that
>
> int i;
> foo (&i);
> ..
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430
--- Comment #29 from Richard Biener ---
What remains seems to be complaining that
int i;
foo (&i);
doesn't warn. And we have another bug that
int i;
foo (&i);
... = i;
doesn't warn for the read from i.
I think both of these need a
>> I'm unable to install GCC7 on Debian 8/i386 with Experimental enabled.
>> Things worked well under x86_64; the issue seems to be limited to
>> i386.
>
> that's not a gcc-7 issue. please make sure that the dependent libraries are
> in sync.
My bad. I was under the impression Debian's package sy
Your message dated Thu, 2 Mar 2017 10:08:54 +0100
with message-id <91a3789c-a837-999a-b2ac-d195d05e9...@debian.org>
and subject line Re: Bug#856528: Unable to install GCC7 on Debian 8/i386 with
Experimental enabled
has caused the Debian Bug report #856528,
regarding Unable to install GCC7 on Debia
13 matches
Mail list logo
