From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
linuxppc-dev@ozlabs.org, jdl@jdl.com
Subject: Re: [PATCH] dtc: supply a definition for YYRHSLOC if there isn't one
Date: Thu, 17 Jul 2008 10:02:48 -0400 [thread overview]
Message-ID: <487F5108.9050207@windriver.com> (raw)
In-Reply-To: <20080717054713.GF21564@yookeroo.seuss>
David Gibson wrote:
> On Wed, Jul 16, 2008 at 01:53:57PM -0400, Paul Gortmaker wrote:
>
>> It seems that some machines, like a default RHEL4 install, will
>> not have a definition for YYRHSLOC, and that prevents building
>> dtc. This supplies what appears to be the standard definition
>> for it in the event that the host system does not have it defined.
>>
>
> I'm pretty uneasy about this, since it relies on knowing the internals
> of how bison manages its tokens. What version of bison is it in RHEL4
> that causes the trouble?
>
Right -- well, I trust your judgment on something like that more than
my own. The version in question is "bison (GNU Bison) 1.875c".
When I was digging around, the definitions all pretty much came back
with the one I'd used, but I do understand your concern.
> In fact I have a feeling that the extra 'file' field in YYLTYPE never
> gets used, which means we could just ditch our custom YYLLOC_DEFAULT
> definition, which would be a better idea, IMO, except that we'll
> probably want the file info back at some point.
>
> Ick.
>
Sorry to be the bearer of bad news :-) If you have an alternate fix that
you'd like me to test, I'd be happy to do so; I've still access to the old
machine on which the problem report was 1st bounced to me from. If I
tried to fix it in any other way than what I did, I'd probably hurt
myself...
Paul.
prev parent reply other threads:[~2008-07-17 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 17:53 [PATCH] dtc: supply a definition for YYRHSLOC if there isn't one Paul Gortmaker
2008-07-17 5:47 ` David Gibson
2008-07-17 14:02 ` Paul Gortmaker [this message]
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=487F5108.9050207@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.