| 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
| ||
|
Message-ID: <87txtkgrsw.fsf@mattleach.net> Date: Wed, 24 Oct 2012 10:09:19 +0100 From: Matthew Leach <matthew@...tleach.net> To: Richard Weinberger <richard@....at> Cc: linux-kernel@...r.kernel.org, Martin Pärtel <martin.partel@...il.com> Subject: Re: [REGRESSION] uml: signal.c build errors Hi Richard, Richard Weinberger <richard@....at> writes: > > Does this patch fix the issue? Your patch fixed the initial error, but I now get: CC arch/um/os-Linux/signal.o arch/um/os-Linux/signal.c:19:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:19:2: warning: (near initialization for ‘sig_info[5]’) [enabled by default] arch/um/os-Linux/signal.c:20:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:20:2: warning: (near initialization for ‘sig_info[8]’) [enabled by default] arch/um/os-Linux/signal.c:21:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:21:2: warning: (near initialization for ‘sig_info[4]’) [enabled by default] arch/um/os-Linux/signal.c:22:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:22:2: warning: (near initialization for ‘sig_info[28]’) [enabled by default] arch/um/os-Linux/signal.c:23:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:23:2: warning: (near initialization for ‘sig_info[7]’) [enabled by default] arch/um/os-Linux/signal.c:24:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:24:2: warning: (near initialization for ‘sig_info[11]’) [enabled by default] arch/um/os-Linux/signal.c:25:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:25:2: warning: (near initialization for ‘sig_info[29]’) [enabled by default] arch/um/os-Linux/signal.c:26:2: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:26:2: warning: (near initialization for ‘sig_info[26]’) [enabled by default] arch/um/os-Linux/signal.c:133:1: warning: initialization from incompatible pointer type [enabled by default] arch/um/os-Linux/signal.c:133:1: warning: (near initialization for ‘handlers[26]’) [enabled by default] CC arch/um/os-Linux/start_up.o arch/um/os-Linux/start_up.c: In function ‘check_coredump_limit’: arch/um/os-Linux/start_up.c:338:16: error: storage size of ‘lim’ isn’t known arch/um/os-Linux/start_up.c:339:2: error: implicit declaration of function ‘getrlimit’ [-Werror=implicit-function-declaration] arch/um/os-Linux/start_up.c:339:22: error: ‘RLIMIT_CORE’ undeclared (first use in this function) arch/um/os-Linux/start_up.c:339:22: note: each undeclared identifier is reported only once for each function it appears in arch/um/os-Linux/start_up.c:347:22: error: ‘RLIM_INFINITY’ undeclared (first use in this function) arch/um/os-Linux/start_up.c:338:16: warning: unused variable ‘lim’ [-Wunused-variable] cc1: some warnings being treated as errors make[1]: *** [arch/um/os-Linux/start_up.o] Error 1 make: *** [arch/um/os-Linux] Error 2 > Are you using glibc 2.17? I am using glibc 2.16 with gcc 4.7.2. Thanks, Matt -- 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/
Powered by blists - more mailing lists