mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Zimny Lech <napohybelskurwysynom2010@gmail.com>
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
	Arnaud Lacombe <lacombar@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>, Michal Marek <mmarek@suse.cz>
Subject: Re: mmotm 2010-10-13-17-13 uploaded
Date: Thu, 14 Oct 2010 12:16:27 -0700	[thread overview]
Message-ID: <20101014121627.2405e99a.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTin1RjhDZp6w-jumRnZ1-Hx3zio7SrZtZqummok2@mail.gmail.com>

On Thu, 14 Oct 2010 12:26:45 +0200
Zimny Lech <napohybelskurwysynom2010@gmail.com> wrote:

> 2010/10/14  <akpm@linux-foundation.org>:
> > The mm-of-the-moment snapshot 2010-10-13-17-13 has been uploaded to
> 
> linux-next.patch breaks things
> 
>   GEN     /home/test/linux-2.6-obj/Makefile
>   HOSTCC  scripts/kconfig/zconf.tab.o
> In file included from scripts/kconfig/zconf.tab.c:2462:0:
> scripts/kconfig/lex.zconf.c:2425:7: error: conflicting types for 'zconf_curname'
> /home/test/linux-2.6-mm/scripts/kconfig/lkc.h:79:13: note: previous
> declaration of 'zconf_curname' was here
> scripts/kconfig/lex.zconf.c: In function 'zconf_curname':
> scripts/kconfig/lex.zconf.c:2427:2: warning: return discards
> qualifiers from pointer target type
> make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
> make[2]: *** [silentoldconfig] Error 2
> make[1]: *** No rule to make target `include/config/auto.conf', needed
> by `include/config/kernel.release'.  Stop.
> make: *** [sub-make] Error 2
> 

Something went wrong with the zconf_curname() constification.

lex scripts never seem to get along well with the build dependency
systems - did you try a `make mrproper' and a rebuild?


  reply	other threads:[~2010-10-14 19:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  0:13 akpm
2010-10-14  4:17 ` mmotm 2010-10-13-17-13 uploaded (staging/bcm) Randy Dunlap
2010-10-14 19:14   ` Greg KH
2010-10-14 20:38     ` Randy Dunlap
2010-10-14  4:29 ` mmotm 2010-10-13-17-13 uploaded (leds) Randy Dunlap
2010-10-14 11:38   ` Johannes Berg
2010-10-14 16:14     ` Randy Dunlap
2010-10-14 20:13       ` Johannes Berg
2010-10-14 20:32         ` Randy Dunlap
2010-10-26 10:14           ` Johannes Berg
2010-10-14 10:26 ` mmotm 2010-10-13-17-13 uploaded Zimny Lech
2010-10-14 19:16   ` Andrew Morton [this message]
2010-10-14 19:23     ` Zimny Lech
2010-10-14 20:06 ` mmotm 2010-10-13 - GSPCA SPCA561 webcam driver broken Valdis.Kletnieks
2010-10-15  8:45   ` Hans Verkuil
2010-10-15  9:05     ` Andrew Morton
2010-10-15 10:02       ` Hans Verkuil
2010-10-15 12:05         ` Mauro Carvalho Chehab
2010-10-15 12:23           ` Hans Verkuil
2010-10-18 19:00             ` Mauro Carvalho Chehab
2010-10-18 19:39               ` Hans Verkuil
2010-10-20 15:50 ` ptrace BUG [was: mmotm 2010-10-13-17-13 uploaded] Jiri Slaby
2010-10-20 15:52   ` Peter Zijlstra
2010-10-20 15:54   ` Frederic Weisbecker
2010-10-20 16:03     ` Jiri Slaby
2010-10-20 16:13       ` Peter Zijlstra
2010-10-20 17:29         ` Jiri Slaby
2010-10-21  7:34         ` Jiri Slaby
2010-10-21  7:40           ` Peter Zijlstra

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=20101014121627.2405e99a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=lacombar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=napohybelskurwysynom2010@gmail.com \
    --cc=sam@ravnborg.org \
    /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

Powered by JetHome