I believe this problem is fixed by commit
ffc015bea26f24d862e7e877d907fbe1ab9a9967. I was able to build a grafted
'hello' for i686-linux, and it worked correctly.
Can you try it and report back?
Mark
Mark H Weaver writes:
> The problem is that glibc-CVE-2017-1000366-pt2.patch introduces a
> reference to 'strcspn' in rtld.c. This causes the glibc build system to
> automatically add 'rtld-strcspn.os' and 'rtld-strcspn-c.os' to the list
> of objects to be built. When 'rtld-strcspn-c.os' is bui
Mark H Weaver writes:
> Ricardo Wurmus writes:
>
>> Since commit 665d6a59161769e10b52ffcbcd5cd2db22f32681 I have to build
>> glibc from source. Unfortunately, this fails with the following error:
>>
>> …
>> i686-guix-linux-gnu-gcc ../sysdeps/i386/i686/multiarch/strcspn-c.c -c
>> -std=gnu11 -fg
On Sun, Jun 25, 2017 at 10:30:10PM +0200, Ludovic Courtès wrote:
> Mark H Weaver skribis:
> > In order to guard against users unwittingly using old software with
> > unpatched security flaws, "guix package -u" should issue a warning if
> > any packages in the profile that match the provided patter
Mark H Weaver writes:
> Ricardo Wurmus writes:
>
>> Since commit 665d6a59161769e10b52ffcbcd5cd2db22f32681 I have to build
>> glibc from source. Unfortunately, this fails with the following error:
>>
>> …
>> i686-guix-linux-gnu-gcc ../sysdeps/i386/i686/multiarch/strcspn-c.c -c
>> -std=gnu11 -fg
Ricardo Wurmus writes:
> Since commit 665d6a59161769e10b52ffcbcd5cd2db22f32681 I have to build
> glibc from source. Unfortunately, this fails with the following error:
>
> …
> i686-guix-linux-gnu-gcc ../sysdeps/i386/i686/multiarch/strcspn-c.c -c
> -std=gnu11 -fgnu89-inline -O2 -Wall -Werror -W
I'm not entirely sure this is the right place to report this
bug. If I should report this bug elsewhere, please direct me.
When I indent the `emacs-which-key' package definition in
gnu/packages/emacs.scm using `indent-region', the description gets
indented wrongly. The "(or as many as space allow
Mark H Weaver skribis:
> In order to guard against users unwittingly using old software with
> unpatched security flaws, "guix package -u" should issue a warning if
> any packages in the profile that match the provided patterns are not
> found in the set of available packages.
Fixed in a1b46bdc0
Since commit 665d6a59161769e10b52ffcbcd5cd2db22f32681 I have to build
glibc from source. Unfortunately, this fails with the following error:
--8<---cut here---start->8---
…
i686-guix-linux-gnu-gcc ../sysdeps/i386/i686/multiarch/strcspn-c.c -c
-std=gnu11 -fgnu8
On Sun, Jun 25, 2017 at 12:55:51PM +0200, Marius Bakke wrote:
> Leo Famulari writes:
> > Subject: [PATCH] gnu: grub: Disable a flaky test.
> >
> > * gnu/packages/bootloaders.scm (grub)[arguments]: Add 'disable-flaky-test'
> > phase
> > and run the tests in parallel.
>
> LGTM.
Thanks for the rev
I agree, let's wait for guidance from the upstream GCC and GLIBC developers.
Original Message
From: Marius Bakke
Sent: June 25, 2017 6:41:06 AM EDT
To: Danny Milosavljevic , 27...@debbugs.gnu.org
Subject: bug#27429: Stack clash (CVE-2017-1000366 etc); -fstack-check
Danny Milos
Leo Famulari writes:
> On Fri, Jun 23, 2017 at 03:30:10PM -0400, Leo Famulari wrote:
>> On Sat, Jun 03, 2017 at 12:54:46AM +0200, Ludovic Courtès wrote:
>> > FAIL: grub_cmd_set_date
>>
>> > All in all, I’m tempted to think this has to do with running the tests
>> > in parallel.
>> >
>> > As a s
Danny Milosavljevic writes:
> Hi,
>
> what do you all think of rebuilding the world with "-fstack-check" (either
> now or later on) ?
>
> That would make gcc emit code to always grow the stack in a way that it
> certainly touches each 4 KiB (parametrizable by
> STACK_CHECK_PROBE_INTERVAL_EXP)
Hi,
what do you all think of rebuilding the world with "-fstack-check" (either now
or later on) ?
That would make gcc emit code to always grow the stack in a way that it
certainly touches each 4 KiB (parametrizable by STACK_CHECK_PROBE_INTERVAL_EXP)
page on the way.
I think that would be the
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> I just tried to update my GuixSD system to commit
>> c57b56722f6c167c5a285f47802047de85a356ae on master. "guix system build"
>> failed with the following error:
>>
>> guix system: error: profile contains conflicting entries for
white white writes:
> Yes , I will try on another machine.
> I use ext4.
> I use Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz.
> Maybe :
> " CPU: 0 PID: 1 Comm: init /not tainted 4.11.0-gnu #1"
> There is a "Call Trace" after that and a couple of information relating to
> it .
> I think it's beca
16 matches
Mail list logo
