From: Jens Axboe <axboe@kernel.dk>
To: "Neto,
Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>,
Stephen Cameron <stephenmcameron@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: YACC y.tab.c Usage: /usr/bin/yacc [options] filename
Date: Tue, 07 Oct 2014 08:55:43 -0600 [thread overview]
Message-ID: <5433FEEF.2070402@kernel.dk> (raw)
In-Reply-To: <D0597430.51EDC%Antonio.Jose.Rodrigues.Neto@netapp.com>
On 10/07/2014 08:44 AM, Neto, Antonio Jose Rodrigues wrote:
>
>
> On 10/7/14, 10:29 AM, "Jens Axboe" <axboe@kernel.dk> wrote:
>
>> On 10/07/2014 08:17 AM, Jens Axboe wrote:
>>>> Please see below:
>>>>
>>>> Nossa Senhora:fio neto$ make V=1 t/dedupe
>>>> gcc -std=gnu99 -Wwrite-strings -Wall -Wdeclaration-after-statement
>>>> -O3 -g
>>>> -ffast-math -D_GNU_SOURCE -include config-host.h -DBITS_PER_LONG=64
>>>> -DFIO_VERSION='"fio-2.1.13-31-g15e3"' -o t/dedupe -ll -lz -lm
>>>> -lpthread
>>>> -ldl
>>>> Undefined symbols for architecture x86_64:
>>>> "_yylex", referenced from:
>>>> _main in libl.a(libmain.o)
>>>> ld: symbol(s) not found for architecture x86_64
>>>> clang: error: linker command failed with exit code 1 (use -v to see
>>>> invocation)
>>>> make: *** [t/dedupe] Error 1
>>>>
>>>> Any idea how to fix it?
>>>
>>> It's only supported on Linux right now, it will be built automatically
>>> there. Not really a design problem, it's just that it has the Linux
>>> method for getting the size of a block device hard wired. I can fix that
>>> pretty quickly.
>>
>> I changed it to use the fio supplied blockdev_size(), so it should work
>> on all platforms now:
>>
>> http://git.kernel.dk/?p=fio.git;a=commit;h=d08a6886fa57f819682f05548d284a0
>> 79a99e77d
>>
>> Pull, make clean, and make again. Should work on OSX and others now.
>>
>> --
>> Jens Axboe
>>
>
> Hi Jens,
>
> This is neto from Brazil
>
> How are you?
>
> :-(
>
> Trying with the latest commit on my mac.
>
> CC lex.yy.o
> lex.yy.c:1231: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);
> ^
> 1 warning generated.
> CC y.tab.o
> CC parse.o
> CC mutex.o
> CC options.o
> CC lib/rbtree.o
> CC smalloc.o
> CC filehash.o
> CC profile.o
> CC debug.o
> CC lib/rand.o
> CC lib/num2str.o
> CC lib/ieee754.o
> CC crc/crc16.o
> CC crc/crc32.o
> CC crc/crc32c-intel.o
> CC crc/crc32c.o
> CC crc/crc64.o
> CC crc/crc7.o
> CC crc/fnv.o
> CC crc/md5.o
> CC crc/murmur3.o
> CC crc/sha1.o
> CC crc/sha256.o
> CC crc/sha512.o
> CC crc/test.o
> CC crc/xxhash.o
> CC engines/cpu.o
> CC engines/mmap.o
> CC engines/sync.o
> CC engines/null.o
> CC engines/net.o
> CC memalign.o
> CC server.o
> CC client.o
> CC iolog.o
> CC backend.o
> CC libfio.o
> CC flow.o
> CC cconv.o
> CC lib/prio_tree.o
> CC json.o
> CC lib/zipf.o
> CC lib/axmap.o
> CC lib/lfsr.o
> CC gettime-thread.o
> CC helpers.o
> CC lib/flist_sort.o
> CC lib/hweight.o
> CC lib/getrusage.o
> CC idletime.o
> CC td_error.o
> CC profiles/tiobench.o
> CC profiles/act.o
> CC io_u_queue.o
> CC filelock.o
> CC lib/tp.o
> CC lib/bloom.o
> CC engines/posixaio.o
> CC fio.o
> LINK fio
> CC t/stest.o
> CC t/log.o
> CC t/debug.o
> LINK t/stest
> CC t/ieee754.o
> LINK t/ieee754
> CC t/genzipf.o
> LINK t/genzipf
> CC t/axmap.o
> LINK t/axmap
> CC t/lfsr-test.o
> LINK t/lfsr-test
> CC t/dedupe.o
> t/dedupe.c:14:10: fatal error: 'linux/fs.h' file not found
> #include <linux/fs.h>
> ^
> 1 error generated.
> make: *** [t/dedupe.o] Error 1
> Nossa Senhora:fio neto$
t/dedupe should work now if you pull again. There's still some oddity
around the size_t - ignore that for now, it'll work, and we'll get it
sorted.
--
Jens Axboe
next prev parent reply other threads:[~2014-10-07 14:55 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 [this message]
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
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=5433FEEF.2070402@kernel.dk \
--to=axboe@kernel.dk \
--cc=Antonio.Jose.Rodrigues.Neto@netapp.com \
--cc=fio@vger.kernel.org \
--cc=stephenmcameron@gmail.com \
/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