Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Bruce Cran <bruce@cran.org.uk>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: YACC y.tab.c Usage: /usr/bin/yacc [options] filename
Date: Mon, 06 Oct 2014 16:34:09 -0600	[thread overview]
Message-ID: <543318E1.2070701@cran.org.uk> (raw)
In-Reply-To: <CADzpL0TJm=qM8UXFriQmH3t6c8BOHCJY7O-w+mtQspE-sLg4gg@mail.gmail.com>

On 10/6/2014 3:44 PM, Stephen Cameron wrote:
> I suspect that your version of yacc does not comprehend the --no-lines
> option (which we needed only in order to avoid a bug in some other
> versions of yacc).  From the usage message it does appear to
> understand both -d and -l though.
>
> Try changing the --no-lines option in the Makefile to -l instead, and
> see if that helps.

The same problem occurs on FreeBSD 10. After changing "--no-lines" to 
"-l" the build works, with the following warnings:

   YACC y.tab.c
     CC lex.yy.o
lex.yy.c:1245:3: warning: incompatible pointer types passing 'yy_size_t 
*' (aka 'unsigned long *') to parameter of type 'int *' 
[-Wincompatible-pointer-types]
                 YY_INPUT( 
(&YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
exp/expression-parser.l:31:25: note: expanded from macro 'YY_INPUT'
                 lexer_input((buffer), &(bytes_read), (bytes_requested))
                                       ^~~~~~~~~~~~~
exp/expression-parser.l:27:43: note: passing argument to parameter 
'nbytes' here
extern int lexer_input(char* buffer, int *nbytes, int buffersize);

-- 
Bruce

  parent reply	other threads:[~2014-10-06 22:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 21:12 YACC y.tab.c Usage: /usr/bin/yacc [options] filename Neto, Antonio Jose Rodrigues
2014-10-06 21:44 ` Stephen Cameron
     [not found]   ` <D05885C8.51DCC%Antonio.Jose.Rodrigues.Neto@netapp.com>
2014-10-06 22:04     ` Stephen Cameron
2014-10-06 22:10       ` Neto, Antonio Jose Rodrigues
2014-10-06 22:25         ` Stephen Cameron
2014-10-06 22:28           ` Neto, Antonio Jose Rodrigues
2014-10-06 22:31             ` Stephen Cameron
2014-10-07  1:18               ` Jens Axboe
2014-10-07  1:10           ` Jens Axboe
2014-10-07  1:26             ` Stephen Cameron
2014-10-07  2:18               ` Jens Axboe
2014-10-07 13:39                 ` Neto, Antonio Jose Rodrigues
2014-10-07 13:51                   ` Neto, Antonio Jose Rodrigues
2014-10-07 14:17                     ` Jens Axboe
2014-10-07 14:29                       ` Jens Axboe
2014-10-07 14:44                         ` Neto, Antonio Jose Rodrigues
2014-10-07 14:55                           ` Jens Axboe
2014-10-07 15:00                             ` Neto, Antonio Jose Rodrigues
2014-10-07 15:11                               ` Jens Axboe
2014-10-07 15:14                                 ` Neto, Antonio Jose Rodrigues
2014-10-07 14:16                   ` Jens Axboe
2014-10-06 22:34   ` Bruce Cran [this message]
2014-10-06 23:02     ` Stephen Cameron

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=543318E1.2070701@cran.org.uk \
    --to=bruce@cran.org.uk \
    --cc=fio@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