linux-kernel - Re: [PATCH] MIPS: VDSO: Fix build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5666C8B2.2030402@cogentembedded.com>
Date:	Tue, 8 Dec 2015 15:10:26 +0300
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	Qais Yousef <qais.yousef@...tec.com>, linux-mips@...ux-mips.org
Cc:	alex@...x-smith.me.uk, linux-kernel@...r.kernel.org,
	ralf@...ux-mips.org
Subject: Re: [PATCH] MIPS: VDSO: Fix build error

Hello.

On 12/8/2015 1:11 PM, Qais Yousef wrote:

> Commit ebb5e78cc634 (MIPS: Initial implementation of a VDSO) introduced a build
> error.

    scripts/checkpatch.pl now enforces certain format for the commit citing -- 
you also need to enclose the summary in "".

> For MIPS VDSO to be compiled it requires binutils version 2.25 or above but the
> check in the Makefile had inverted logic causing it to be compiled in if binutils
> is below 2.25.
>
> This fixes the following compilation error:
>
> CC      arch/mips/vdso/gettimeofday.o
> /tmp/ccsExcUd.s: Assembler messages:
> /tmp/ccsExcUd.s:62: Error: can't resolve `_start' {*UND* section} - `L0' {.text section}
> /tmp/ccsExcUd.s:467: Error: can't resolve `_start' {*UND* section} - `L0' {.text section}
> make[2]: *** [arch/mips/vdso/gettimeofday.o] Error 1
> make[1]: *** [arch/mips/vdso] Error 2
> make: *** [arch/mips] Error 2
>
> Signed-off-by: Qais Yousef <qais.yousef@...tec.com>
[...]

MBR, Sergei

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/