From: randrianasulu@gmail.com
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Lin Ming <lin@ming.vg>, linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: 2.6.37-rc1 build failure
Date: Thu, 4 Nov 2010 12:16:05 +0000 [thread overview]
Message-ID: <201011041216.07206.randrianasulu@gmail.com> (raw)
In-Reply-To: <20101103213439.01d2062d.randy.dunlap@oracle.com>
В сообщении от Thursday 04 November 2010 04:34:39 Randy Dunlap написал(а):
> On Thu, 4 Nov 2010 03:34:16 +0000 randrianasulu@gmail.com wrote:
> > В сообщении от Wednesday 03 November 2010 02:05:07 Lin Ming написал(а):
> > > On Wed, Nov 3, 2010 at 1:32 PM, <randrianasulu@gmail.com> wrote:
> > > > Trying to make new kernel i run into this:
> > > >
> > > > CC arch/x86/lib/delay.o
> > > > AS arch/x86/lib/getuser.o
> > > > AS arch/x86/lib/putuser.o
> > > > CC arch/x86/lib/usercopy_32.o
> > > > AR arch/x86/lib/lib.a
> > > > LD vmlinux.o
> > > > MODPOST vmlinux.o
> > > > WARNING: modpost: Found 2 section mismatch(es).
> > > > To see full details build your kernel with:
> > > > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> > > > GEN .version
> > > > CHK include/generated/compile.h
> > > > UPD include/generated/compile.h
> > > > CC init/version.o
> > > > LD init/built-in.o
> > > > LD .tmp_vmlinux1
> > > > kernel/built-in.o: In function `free_event':
> > > > perf_event.c:(.text+0x66eb3): undefined reference to `irq_work_sync'
> > > > kernel/built-in.o: In function `perf_output_put_handle':
> > > > perf_event.c:(.text+0x680e1): undefined reference to `irq_work_queue'
> > > > kernel/built-in.o: In function `__perf_event_overflow':
> > > > perf_event.c:(.text+0x6a75e): undefined reference to `irq_work_queue'
> > > > make: *** [.tmp_vmlinux1] Ошибка 1
> > > >
> > > > kernel.org git master up to
> > > >
> > > > commit eb8abb927ae2fd1730e24ea94cd9527f3c086292
> > > > Author: Theodore Ts'o <tytso@mit.edu>
> > > > Date: Tue Nov 2 09:34:50 2010 -0400
> > > >
> > > > ext4: Remove useless spinlock in ext4_getattr()
> > > >
> > > >
> > > >
> > > > this is my .config
> > >
> > > I build with you .config, but no error.
> > >
> > > Maybe you can make distclean and re-build.
> > >
> > > Lin Ming
> >
> > No, same error.
> >
> > I'm using (Linux/GNU Binutils) 2.20.51.0.8.20100412 , gcc (GCC) 4.4.4 on
> > Slackware -current box (glibc-2.12.1-i486-2). Not sure what else i can do
> > for debugging this.
> > --
>
> The build fails for me with the given .config file.
> It's due to selects and depends, finally comes down to HAVE_PERF_EVENTS not
> being enabled for M386 or M486. Do you actually have a processor of that
> vintage?
No, i have AMD k7:
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 3
model name : AMD Duron(tm) Processor
stepping : 1
cpu MHz : 950.014
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up
bogomips : 1900.02
clflush size : 32
cache_alignment : 32
address sizes : 36 bits physical, 32 bits virtual
power management:
but i prefer to build kernel for i486 (i686 was giving me troubles on old k6-2
machine some time ago, and i used variant of this config for LiveCD,
sometimes for some QEMU tests ... i have real 486 box but it has too litle
memory , 4mb, for being useful.)
Thanks for figuring this out, i'll rebuild my kernel for i586 for now.
>
> We can probably fix the Kconfig files to prevent this build error...
>
> (Ingo: FYI)
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code
> ***
next prev parent reply other threads:[~2010-11-04 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 5:32 2.6.37-rc1 build failure randrianasulu
2010-11-03 2:05 ` Lin Ming
2010-11-04 3:34 ` randrianasulu
2010-11-04 4:34 ` Randy Dunlap
2010-11-04 12:16 ` randrianasulu [this message]
2010-11-10 12:59 ` Peter Zijlstra
2010-11-10 13:24 ` Ingo Molnar
2010-11-10 17:12 ` Randy Dunlap
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=201011041216.07206.randrianasulu@gmail.com \
--to=randrianasulu@gmail.com \
--cc=lin@ming.vg \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
/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