Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751729Ab3EMMP4 (ORCPT ); Mon, 13 May 2013 08:15:56 -0400 Received: from ozlabs.org ([203.10.76.45]:32891 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751170Ab3EMMPz (ORCPT ); Mon, 13 May 2013 08:15:55 -0400 Message-ID: <1368447352.10679.0.camel@concordia> Subject: Re: Build regressions/improvements in v3.10-rc1 (um) From: Michael Ellerman To: richard -rw- weinberger Cc: Geert Uytterhoeven , Stephen Rothwell , Linux Kernel Development , User-mode Linux Kernel Development Date: Mon, 13 May 2013 22:15:52 +1000 In-Reply-To: References: <38896893-83c7-4eb4-848a-bb35663d945b@email.android.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.2-0ubuntu0.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3381 Lines: 74 On Mon, 2013-05-13 at 12:07 +0200, richard -rw- weinberger wrote: > On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman > wrote: > > > > > > Geert Uytterhoeven wrote: > > > >>On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger > >> wrote: > >>> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven > >>> wrote: > >>>> On Sun, 12 May 2013, Geert Uytterhoeven wrote: > >>>>> However, the full list of errors isn't that unmanageable, so I'm > >>following > >>>>> up with a digested list... > >>>> > >>>> arch/um/drivers/cow_user.c:216: error: implicit declaration of > >>function 'htobe32': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:249: error: implicit declaration of > >>function 'htobe64': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:303: error: implicit declaration of > >>function 'be32toh': 1 errors in 1 logs > >>>> arch/um/drivers/cow_user.c:330: error: implicit declaration of > >>function 'be64toh': 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: (Each undeclared > >>identifier is reported only once: 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:321: error: for each function it > >>appears in.): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:412: error: 'PTRACE_GETSIGINFO' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/skas/process.c:560: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: 'PTRACE_SETOPTIONS' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: (Each undeclared identifier > >>is reported only once: 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:245: error: for each function it appears > >>in.): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:246: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:303: error: 'PTRACE_SETOPTIONS' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> arch/um/os-Linux/start_up.c:304: error: 'PTRACE_O_TRACESYSGOOD' > >>undeclared (first use in this function): 1 errors in 1 logs > >>>> v3.10-rc1/um-i386/um-defconfig > >>>> Old host environment on kissb? > >>> > >>> This really looks like a host environment issue. > >>> PTRACE_O_TRACESYSGOOD for example is defined in > >>/usr/include/linux/ptrace.h > >> > >>Yep, just like e.g. htobe32(). > >> > >>Michael, Stephen: Any chance this can be fixed? > > > > Possibly. We're cross compiling these on powerpc so perhaps we need to update the cross compiler. > > Looks like you are the first man on planet earth who tries do build > UML/x86 on powerpc. :D :) It has given us some trouble over the years. I'll talk to Stephen tomorrow about it and see if we can get it working again. cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/