On Tue, 13 Nov 2018 18:11:38 +0100
tu...@posteo.de wrote:
> Hi,
>
> I got a weird looking error while upgrading/recompiling nasm:
...
> F: fopen_wr
> S: deny
> P: /?
> A: /?
> R: /?
> C: /usr/bin/nasm /?
This is likely a nasm bug:
https://bugs.gentoo.org/670944
On Thu, Nov 15, 2018 at 6:20 AM wrote:
> Hi,
>
> its gone this evening while updateing...
Yeah the nasm update was backed out
Fri May 11 15:25:38 2018 >>> dev-lang/nasm-2.13.03-r1
Mon Nov 12 12:27:25 2018 >>> dev-lang/nasm-2.14
Wed Nov 14 16:31:50 2018 >>> dev-lang/nasm-2.13.03-r1
>
> That is odd. I tried inserting the IPV[4,6] .config entries by hand, but
> oldconfig removed them again.
>
I'd say those entries are deprecated and that shorewall will just need an
update to make it compatible with 4.19.
Hi,
its gone this evening while updateing...
Thanks a lot to all for the help!
Cheers
Meino
On 11/13 09:35, David Haller wrote:
> Hello,
>
> On Tue, 13 Nov 2018, tu...@posteo.de wrote:
> >I got a weird looking error while upgrading/recompiling nasm:
> >cmake -C
>
On Tuesday, 13 November 2018 08:06:03 GMT Adam Carter wrote:
> My .config hasnt changed, other than from setting the new options via make
> oldconfig;
>
> /usr/src/configs # grep CONFIG_NF_CONNTRACK_IP config-2018-10-29
> config-2018-11-13
> config-2018-10-29:CONFIG_NF_CONNTRACK_IPV4=y
>
On Thu, Nov 1, 2018 at 12:57 PM Adam Carter wrote:
> For me;
>
> Oct 25 15:34:51 phat kernel: fbcon: amdgpudrmfb (fb0) is primary device
> Oct 25 15:34:51 phat kernel: amdgpu: [powerplay]
> failed to send message 148 ret is 0
> Oct 25 15:34:51 phat kernel: amdgpu:
6 matches
Mail list logo
