public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Bob Tracy <rct@gherkin.frus.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc1 build error (YACC): followup
Date: Sun, 09 Jul 2006 11:28:59 -0700	[thread overview]
Message-ID: <44B14AEB.2060902@zytor.com> (raw)
In-Reply-To: <20060709133844.GA6650@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Fri, Jul 07, 2006 at 04:54:34PM -0700, H. Peter Anvin wrote:
>> I propose the following as a global yacc rule; already used in usr/dash 
>> in the klibc tree, and which seems to work for both bison and BSD yacc:
>>
>> quiet_cmd_yacc = YACC    $@
>>       cmd_yacc = $(YACC) -d -o $@ $<
>>
>> $(obj)/%.c %(obj)/%.h: $(src)/%.y
>>         $(call cmd,yacc)
> klibc and the kernel does not share any rules today.
> And yacc is so special that it's not worth it only for yacc to start
> doing this.
> 
> In todays kernel build yacc is never used. For the few cases were output
> of yacc is needed the kernel include _shipped files. For dash we should
> maybe consider the same?
> 

Personally I consider that pretty silly.  yacc/bison is a standard, 
portable utility, and it isn't even architecture-dependent so there is 
no porting effort.

	-hpa

  reply	other threads:[~2006-07-09 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 20:24 2.6.18-rc1 build error (YACC): followup Bob Tracy
2006-07-07 20:36 ` Sam Ravnborg
2006-07-07 22:36 ` Sam Ravnborg
2006-07-07 23:54   ` H. Peter Anvin
2006-07-09 13:38     ` Sam Ravnborg
2006-07-09 18:28       ` H. Peter Anvin [this message]
2006-07-10 12:46         ` Bob Tracy

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=44B14AEB.2060902@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.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