Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1378398 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-04-14 04:20 +0200 |
| Last post | 2016-04-14 17:10 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
linux-next: build failure after merge of the tip tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-14 04:20 +0200
Re: linux-next: build failure after merge of the tip tree Arnaldo Carvalho de Melo <acme@redhat.com> - 2016-04-14 14:40 +0200
Re: linux-next: build failure after merge of the tip tree Michael Ellerman <mpe@ellerman.id.au> - 2016-04-14 15:00 +0200
Re: linux-next: build failure after merge of the tip tree Arnaldo Carvalho de Melo <acme@redhat.com> - 2016-04-14 17:10 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-04-14 04:20 +0200 |
| Subject | linux-next: build failure after merge of the tip tree |
| Message-ID | <rnF2V-2OB-1@gated-at.bofh.it> |
Hi all,
After merging the tip tree, today's linux-next build (powerpc64le perf)
failed like this:
make[3]: *** No rule to make target '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by '/home/sfr/next/perf/util/syscalltbl.o'. Stop.
(I build in /home/sfr/next/next with objects in /home/sfr/next/perf.)
Presumably caused by commit
1b700c997500 ("perf tools: Build syscall table .c header from kernel's syscall_64.tbl")
I have reverted that commit for today (which fixes my build problem but
may not be overall correct).
--
Cheers,
Stephen Rothwell
[toc] | [next] | [standalone]
| From | Arnaldo Carvalho de Melo <acme@redhat.com> |
|---|---|
| Date | 2016-04-14 14:40 +0200 |
| Message-ID | <rnOIV-1Cp-5@gated-at.bofh.it> |
| In reply to | #1378398 |
Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc64le perf)
> failed like this:
>
> make[3]: *** No rule to make target '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by '/home/sfr/next/perf/util/syscalltbl.o'. Stop.
>
> (I build in /home/sfr/next/next with objects in /home/sfr/next/perf.)
I'll check, should've been caught by a cross compiler build for ppc64le
I have in place :-\
minimal-ubuntu-x-ppc64el: Ok
But maybe not, as this requires audit-libs-devel and that is not present
on that minimal ubuntu x-compiler setup, sigh :-\
- Arnaldo
> Presumably caused by commit
>
> 1b700c997500 ("perf tools: Build syscall table .c header from kernel's syscall_64.tbl")
>
> I have reverted that commit for today (which fixes my build problem but
> may not be overall correct).
>
> --
> Cheers,
> Stephen Rothwell
[toc] | [prev] | [next] | [standalone]
| From | Michael Ellerman <mpe@ellerman.id.au> |
|---|---|
| Date | 2016-04-14 15:00 +0200 |
| Message-ID | <rnP2j-1K8-27@gated-at.bofh.it> |
| In reply to | #1378782 |
On Thu, 2016-04-14 at 09:35 -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu: > > Hi all, > > > > After merging the tip tree, today's linux-next build (powerpc64le perf) > > failed like this: > > > > make[3]: *** No rule to make target '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by '/home/sfr/next/perf/util/syscalltbl.o'. Stop. > > > > (I build in /home/sfr/next/next with objects in /home/sfr/next/perf.) > > I'll check, should've been caught by a cross compiler build for ppc64le > I have in place :-\ > > minimal-ubuntu-x-ppc64el: Ok > > But maybe not, as this requires audit-libs-devel and that is not present > on that minimal ubuntu x-compiler setup, sigh :-\ Hi acme, I have a jenkins which builds perf on ppc64le, but it only builds Linus' tree and linux-next. Which branch in your tree should I be building in order to catch problems like this, perf/core ? https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=perf/core cheers
[toc] | [prev] | [next] | [standalone]
| From | Arnaldo Carvalho de Melo <acme@redhat.com> |
|---|---|
| Date | 2016-04-14 17:10 +0200 |
| Message-ID | <rnR48-3Fm-89@gated-at.bofh.it> |
| In reply to | #1378815 |
Em Thu, Apr 14, 2016 at 10:55:47PM +1000, Michael Ellerman escreveu: > On Thu, 2016-04-14 at 09:35 -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu: > > > Hi all, > > > > > > After merging the tip tree, today's linux-next build (powerpc64le perf) > > > failed like this: > > > > > > make[3]: *** No rule to make target '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by '/home/sfr/next/perf/util/syscalltbl.o'. Stop. > > > > > > (I build in /home/sfr/next/next with objects in /home/sfr/next/perf.) > > > > I'll check, should've been caught by a cross compiler build for ppc64le > > I have in place :-\ > > > > minimal-ubuntu-x-ppc64el: Ok > > > > But maybe not, as this requires audit-libs-devel and that is not present > > on that minimal ubuntu x-compiler setup, sigh :-\ > > Hi acme, > > I have a jenkins which builds perf on ppc64le, but it only builds Linus' tree > and linux-next. > > Which branch in your tree should I be building in order to catch problems like > this, perf/core ? > > https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=perf/core yes, please, I use two normally, one for devel stuff, perf/core, and perf/urgent when sending stuff to the current merge window. I'll continue trying to get a local, more complete, cross compiler environment, need to look again at how that multiarch stuff is in debian... - Arnaldo
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web