linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-media@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 8 (docbook/media)
Date: Fri, 10 Jun 2011 09:04:31 -0700	[thread overview]
Message-ID: <4DF2408F.1010902@oracle.com> (raw)
In-Reply-To: <4DF235F0.9080209@redhat.com>

On 06/10/11 08:19, Mauro Carvalho Chehab wrote:
> Em 10-06-2011 12:04, Randy Dunlap escreveu:
>> On 06/10/11 05:47, Mauro Carvalho Chehab wrote:
>>> Hi Randy,
>>>
>>> Em 09-06-2011 20:37, Randy Dunlap escreveu:
>>>>
>>>> Big hint:  I see these errors not during "make htmldocs" but during a kernel code build
>>>> when CONFIG_BUILD_DOCSRC=y.
>>>>
>>>> Sorry, I should have mentioned this earlier.
>>>
>>> I couldn't reach any troubles there. Documentation build is stopping earlier.
>>> I'm using the -next tree for 20110610:
>>>
>>> $ make defconfig
>>> $ make CONFIG_BUILD_DOCSRC=y -j 16 Documentation/
>>
>>
>> Maybe that incantation does not set CONFIG_HEADERS_CHECK, which
>> CONFIG_BUILD_DOCSRC depends on.
>>
>> [build errors snipped]
>>
>>>
>>> Could you please send me your .config?
>>
>> yes, attached.
>>
> 
> Hmm... didn't work either. With your config:
> 
> [mchehab@buidmachine linux-next]$ make -j 16 Documentation/
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   HOSTCC  Documentation/networking/timestamping/timestamping
> Documentation/networking/timestamping/timestamping.c:45:30: error: linux/net_tstamp.h: No such file or directory
> Documentation/networking/timestamping/timestamping.c: In function ‘main’:
> Documentation/networking/timestamping/timestamping.c:331: error: storage size of ‘hwconfig’ isn’t known
> Documentation/networking/timestamping/timestamping.c:331: error: storage size of ‘hwconfig_requested’ isn’t known
> Documentation/networking/timestamping/timestamping.c:355: error: ‘SOF_TIMESTAMPING_TX_HARDWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:355: error: (Each undeclared identifier is reported only once
> Documentation/networking/timestamping/timestamping.c:355: error: for each function it appears in.)
> Documentation/networking/timestamping/timestamping.c:357: error: ‘SOF_TIMESTAMPING_TX_SOFTWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:359: error: ‘SOF_TIMESTAMPING_RX_HARDWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:361: error: ‘SOF_TIMESTAMPING_RX_SOFTWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:363: error: ‘SOF_TIMESTAMPING_SOFTWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:365: error: ‘SOF_TIMESTAMPING_SYS_HARDWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:367: error: ‘SOF_TIMESTAMPING_RAW_HARDWARE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:387: error: ‘HWTSTAMP_TX_ON’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:387: error: ‘HWTSTAMP_TX_OFF’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:390: error: ‘HWTSTAMP_FILTER_PTP_V1_L4_SYNC’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:390: error: ‘HWTSTAMP_FILTER_NONE’ undeclared (first use in this function)
> Documentation/networking/timestamping/timestamping.c:331: warning: unused variable ‘hwconfig_requested’
> Documentation/networking/timestamping/timestamping.c:331: warning: unused variable ‘hwconfig’
> make[3]: *** [Documentation/networking/timestamping/timestamping] Error 1
> make[2]: *** [Documentation/networking/timestamping] Error 2
> make[1]: *** [Documentation/networking] Error 2
> make: *** [Documentation/] Error 2
> 
> PS.: A full build against next is broken:
> $ make -j 27
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   CC      arch/x86/lib/memmove_64.o
> gcc: arch/x86/lib/memmove_64.c: No such file or directory
> gcc: no input files
> make[1]: *** [arch/x86/lib/memmove_64.o] Error 1
> make: *** [arch/x86/lib] Error 2
> make: *** Waiting for unfinished jobs....
> 
> My tree is on this commit:
> 
> commit c4c5f633751496147f2d846844aa084a1dbca0f4
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> Date:   Fri Jun 10 16:17:26 2011 +1000
> 
>     Add linux-next specific files for 20110610


Still fails on linux-next-20110610 for me.

Please try a full, clean build, not using only
$ make -j 16 Documentation/

$ mkdir doc64
$ cp -a config-r7970 doc64/.config
$ make O=doc64 oldconfig
$ make O=doc64 -j9 all
...
ls: cannot access /lnx/src/NEXT/linux-next-20110610/Documentation/DocBook/media/*/*.gif: No such file or directory
ls: cannot access /lnx/src/NEXT/linux-next-20110610/Documentation/DocBook/media/*/*.png: No such file or directory


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-06-10 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  6:10 linux-next: Tree for June 8 Stephen Rothwell
2011-06-08 19:52 ` linux-next: Tree for June 8 (docbook/media) Randy Dunlap
2011-06-09 19:25   ` Mauro Carvalho Chehab
2011-06-09 19:43     ` Mauro Carvalho Chehab
2011-06-09 20:32       ` Randy Dunlap
2011-06-09 23:32         ` Mauro Carvalho Chehab
2011-06-09 23:37           ` Randy Dunlap
2011-06-10 12:47             ` Mauro Carvalho Chehab
2011-06-10 15:04               ` Randy Dunlap
2011-06-10 15:19                 ` Mauro Carvalho Chehab
2011-06-10 16:04                   ` Randy Dunlap [this message]
2011-06-11  4:42                   ` Stephen Rothwell

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=4DF2408F.1010902@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).