Source: glibc
Version: 2.26-6
Severity: important
Affects: gcc-8 glibc-2.26-*
User: debian-h...@lists.debian.org
Usertags: hurd
Hi,
glibc versions > 2.25-6 breaks all builds of gcc-8-*/gccgo on GNU/Hurd due to
that -fdump-go-spec is broken.
>From the buildd logs of gcc-8:
8-20180218-1 (sid)
Your message dated Mon, 26 Feb 2018 10:22:36 + (UTC)
with message-id <1165894864.8333533.1519640556...@mail.yahoo.com>
and subject line Apply for a Personal/Business Loan
has caused the Debian Bug report #28250,
regarding should libc force programs to check stdout/stderr/stdin for errors?
to be
Your message dated Mon, 26 Feb 2018 10:22:36 + (UTC)
with message-id <1165894864.8333533.1519640556...@mail.yahoo.com>
and subject line Apply for a Personal/Business Loan
has caused the Debian Bug report #28250,
regarding libc should cause programs which leave stuff in stdio to fail
to be marke
Hello,
Svante Signell, on lun. 26 févr. 2018 11:22:22 +0100, wrote:
> Attached is a diff of gen-sysinfo generated with glibc-2.26-6 and glibc-2.25-5
> installed: (edited to show only a subset of the diff)
Please send the whole file. There are always evil details in the corners
which do matter.
S
Processing commands for cont...@bugs.debian.org:
> reopen 28250
Bug #28250 {Done: Credible Finance } [libc6] should libc
force programs to check stdout/stderr/stdin for errors?
Bug #28251 {Done: Credible Finance } [libc6] libc should
cause programs which leave stuff in stdio to fail
Bug reopened
Svante Signell, on lun. 26 févr. 2018 11:49:46 +0100, wrote:
> Ok, here it is. Be prepared that there are duplicates tough, since the entries
> are generated in different order. (I've made a partial edit by moving around
> stuff, but that is not complete)
Rather than moving around by hand, please
Processing commands for cont...@bugs.debian.org:
> reopen 28251
Bug #28251 [libc6] libc should cause programs which leave stuff in stdio to fail
Bug #28250 [libc6] should libc force programs to check stdout/stderr/stdin for
errors?
Bug 28251 is not marked as done; doing nothing.
> thanks
Stopping
On Mon, 2018-02-26 at 11:52 +0100, Samuel Thibault wrote:
> Svante Signell, on lun. 26 févr. 2018 11:49:46 +0100, wrote:
> > Ok, here it is. Be prepared that there are duplicates tough, since the
> > entries
> > are generated in different order. (I've made a partial edit by moving around
> > stuff,
Control: reopen -1
Control: retitle -1 libc should unilaterally report buffered write error on
close
Debian Bug Tracking System writes ("Bug#28251 closed by Credible Finance
(reply to Credible Finance
) (Apply for a Personal/Business Loan)"):
> It has been closed by Credible Finance (reply to
Processing control commands:
> reopen -1
Bug #28251 [libc6] libc should cause programs which leave stuff in stdio to fail
Bug #28250 [libc6] should libc force programs to check stdout/stderr/stdin for
errors?
Bug 28251 is not marked as done; doing nothing.
> retitle -1 libc should unilaterally re
Processing control commands:
> reopen -1
Bug #28250 [libc6] libc should unilaterally report buffered write error on close
Bug #28251 [libc6] libc should unilaterally report buffered write error on close
Bug 28250 is not marked as done; doing nothing.
> retitle -1 perl can lose output due to stdio
Control: reopen -1
Control: retitle -1 perl can lose output due to stdio buffering
Control: found -1 5.20.2-3+deb8u9
Debian Bug Tracking System writes ("Bug#28250 closed by Credible Finance
(reply to Credible Finance
) (Apply for a Personal/Business Loan)"):
> It has been closed by Credible Fin
Svante Signell, on lun. 26 févr. 2018 11:22:22 +0100, wrote:
> creates a defect gen-sysinfo.go file when libc0.3 >= 2.26-* is installed.
A lot of cleanup has happened, yes. The question is what actually made
gcc-8 to break. Just looking at the diff of the build logs, there's
could not determine
13 matches
Mail list logo