On Tue, Jan 08, 2008 at 04:21:04PM +0530, Kamalesh Babulal wrote:
> Sam Ravnborg wrote:
> > On Mon, Jan 07, 2008 at 02:18:27PM +0530, Kamalesh Babulal wrote:
> >> Hi,
> >>
> >> The make allyesconfig build fails on x86_64 (AMD box) with the following
> >> error
> >>
> >>   CHK     include/linux/version.h
> >>   CHK     include/linux/utsrelease.h
> >>   CALL    scripts/checksyscalls.sh
> >>   CHK     include/linux/compile.h
> >>   CHK     include/linux/version.h
> >> make[2]: `scripts/unifdef' is up to date.
> >> make[2]: *** No rule to make target `|', needed by `asm-generic'.  Stop.
> >> make[1]: *** [headers_install] Error 2
> >> make: *** [vmlinux] Error 2
> > 
> > Which make version are you using - it looks like a make bug.
> > Did this occur with an older kernel or has this behaviour just started?
> > 
> > To get further you can disable "headers check" in kernel hacking menu
> > but we need to find out why it fails for you.
> > 
> > Note: '|' is used to say that a prerequisite is 'order only' in
> > scripts/Makefile.headersinst
> > 
> >     Sam
> Hi Sam,
> 
> After disabling the headers_check, the build failure is not seen,
> i tried compiling 2.6.24-rc{2,3,4,5,6,7} all of these have this failure.
> And when i tried compiling 2.6.23 with allyesconfig i got the following
> error
> 
>   SYSCALL arch/x86_64/vdso/vdso.so
> /usr/bin/ld: section .data [ffffffffff700900 -> ffffffffff700917] overlaps 
> section .plt [ffffffffff7008e4 -> ffffffffff700903]
> collect2: ld returned 1 exit status
> make[1]: *** [arch/x86_64/vdso/vdso.so] Error 1
> make: *** [arch/x86_64/vdso] Error 2
No clue why you see this?

> 
> # make --version
> GNU Make version 3.79.1

The "orders only" facility were added in GNU make 3.80 so that explains the
bug you see in first place.
We should try to avoid this use since we do not require make 3.80 yet.


        Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to