From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Subject: 2.6.18-rc1 build error (YACC): followup
Date: Fri, 7 Jul 2006 15:24:42 -0500 (CDT) [thread overview]
Message-ID: <20060707202442.DA2AFDBA1@gherkin.frus.com> (raw)
I wrote:
>$YACC now seems to be undefined when I do a "make bzImage" and the
>build process gets to drivers/scsi/aic7xxx/aicasm (with the aic7xxx
>driver configured as a built-in). As a workaround, it's possible to
>"cd" into the indicated directory and run "make" directly. Once the
>default build completes, restarting "make bzImage" from the kernel
>source root continues as expected.
Found it. The main "Makefile" has "MAKEFLAGS += -rR" uncommented as
of 2.6.18-rc1. The deleted comment about "possibly random breakage"
that used to be just above that line pretty much says it all :-).
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2006-07-07 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 20:24 Bob Tracy [this message]
2006-07-07 20:36 ` 2.6.18-rc1 build error (YACC): followup 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
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=20060707202442.DA2AFDBA1@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-kernel@vger.kernel.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