Re: ntfs-3g: Does it build?

[Kei Kebreau <kei@openmailbox.org>]

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi Kei,
>
> I think the empty line except for the whitespace is the only important line - see below. The number of spaces is different.
>
> diff --git a/gnu/packages/patches/ntfs-3g-CVE-2017-0358.patch b/gnu/packages/patches/ntfs-3g-CVE-2017-0358.patch
> index 6edd676e3..dfaeca080 100644
> --- a/gnu/packages/patches/ntfs-3g-CVE-2017-0358.patch
> +++ b/gnu/packages/patches/ntfs-3g-CVE-2017-0358.patch
> @@ -12,7 +12,7 @@ diff -ur ntfs-3g.old/src/lowntfs-3g.c ntfs-3g/src/lowntfs-3g.c
>  +      char *env = (char*)NULL;
>         struct timespec req = { 0, 100000000 };   /* 100 msec */
>         fuse_fstype fstype;
> -        
> +         
>         if (!stat(cmd, &st) && !geteuid()) {
>                 pid = fork();
>                 if (!pid) {

Indeed. It looks like diff adds an extra space at the beginning of code
lines to leave space for the + and - signs. Applying the patch let
ntfs-3g build again on my side. Was there any change for you using the
patch I just sent?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]