Re: Build regressions/improvements in v3.10-rc1 (um)

[Michael Ellerman <michael@ellerman.id.au>]

Geert Uytterhoeven <geert@linux-m68k.org> wrote:

>On Sun, May 12, 2013 at 11:17 PM, richard -rw- weinberger
><richard.weinberger@gmail.com> wrote:
>> On Sun, May 12, 2013 at 10:47 PM, Geert Uytterhoeven
>> <geert@linux-m68k.org> 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.

cheers

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.