From: Michael Ellerman <michael@ellerman.id.au>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: Build regressions/improvements in v3.10-rc1 (um)
Date: Mon, 13 May 2013 22:15:52 +1000 [thread overview]
Message-ID: <1368447352.10679.0.camel@concordia> (raw)
In-Reply-To: <CAFLxGvyKANuy_vezO+E1aL3FzvdjiNgCD3j-BVGSyL_ne015Xw@mail.gmail.com>
On Mon, 2013-05-13 at 12:07 +0200, richard -rw- weinberger wrote:
> On Mon, May 13, 2013 at 11:54 AM, Michael Ellerman
> <michael@ellerman.id.au> wrote:
> >
> >
> > 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.
>
> 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
next prev parent reply other threads:[~2013-05-13 12:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 19:30 Build regressions/improvements in v3.10-rc1 Geert Uytterhoeven
2013-05-12 20:41 ` Geert Uytterhoeven
2013-05-12 20:42 ` Build regressions/improvements in v3.10-rc1 (sh) Geert Uytterhoeven
2013-05-12 20:44 ` Build regressions/improvements in v3.10-rc1 (cris) Geert Uytterhoeven
2013-05-14 12:06 ` Geert Uytterhoeven
2013-05-14 16:33 ` Jesper Nilsson
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (avr) Geert Uytterhoeven
2013-05-13 12:54 ` Hans-Christian Egtvedt
2013-05-13 13:00 ` Geert Uytterhoeven
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (h8300) Geert Uytterhoeven
2013-05-12 20:46 ` Build regressions/improvements in v3.10-rc1 (mips) Geert Uytterhoeven
2013-06-11 13:37 ` Markos Chandras
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (powerpc) Geert Uytterhoeven
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (um) Geert Uytterhoeven
2013-05-12 21:17 ` richard -rw- weinberger
2013-05-13 8:18 ` Geert Uytterhoeven
2013-05-13 9:54 ` Michael Ellerman
2013-05-13 10:02 ` Geert Uytterhoeven
2013-05-13 10:07 ` richard -rw- weinberger
2013-05-13 10:18 ` Geert Uytterhoeven
2013-05-13 10:20 ` richard -rw- weinberger
2013-05-15 2:48 ` Stephen Rothwell
2013-05-13 12:15 ` Michael Ellerman [this message]
2013-05-15 2:57 ` Stephen Rothwell
2013-05-15 6:50 ` Geert Uytterhoeven
2013-05-12 20:49 ` Build regressions/improvements in v3.10-rc1 (crypto/parisc) Geert Uytterhoeven
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (staging) Geert Uytterhoeven
2013-05-12 21:43 ` Greg KH
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (s390) Geert Uytterhoeven
2013-05-13 7:41 ` Heiko Carstens
2013-05-13 16:41 ` Ben Hutchings
2013-05-12 22:13 ` Build regressions/improvements in v3.10-rc1 Randy Dunlap
2013-05-13 8:37 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368447352.10679.0.camel@concordia \
--to=michael@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox