All of lore.kernel.org
 help / color / mirror / Atom feed
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:29:21 -0600	[thread overview]
Message-ID: <5433F8C1.1030100@kernel.dk> (raw)
In-Reply-To: <5433F5FF.60508@kernel.dk>

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=d08a6886fa57f819682f05548d284a079a99e77d

Pull, make clean, and make again. Should work on OSX and others now.

-- 
Jens Axboe



  reply	other threads:[~2014-10-07 14:29 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 [this message]
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
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=5433F8C1.1030100@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 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.