From: Jens Axboe <jaxboe@fusionio.com>
To: Bruce Cran <bruce@cran.org.uk>
Cc: Filip Sneppe <filip.sneppe@gmail.com>, fio@vger.kernel.org
Subject: Re: [BUG] [PATCH] Undefined symbols: "_posix_memalign" on Mac OS X
Date: Mon, 25 Apr 2011 20:51:42 +0200 [thread overview]
Message-ID: <4DB5C2BE.6030809@fusionio.com> (raw)
In-Reply-To: <4DB55E3C.1040305@fusionio.com>
On 2011-04-25 13:42, Jens Axboe wrote:
> On 2011-04-23 12:06, Bruce Cran wrote:
>> On Sat, 23 Apr 2011 05:57:26 +0200
>> Filip Sneppe <filip.sneppe@gmail.com> wrote:
>>
>>> (I am not subscribed to this list, nor am I a Unix developer).
>>>
>>> I wanted to give fio a try on my OS X 10.5.8 machine, but
>>> this is the error I received when compiling:
>>>
>>> CC helpers.o
>>> CC engines/posixaio.o
>>> DEP depend
>>> CC fio
>>> Undefined symbols:
>>> "_posix_memalign", referenced from:
>>> _thread_main in fio.o
>>> ld: symbol(s) not found
>>> collect2: ld returned 1 exit status
>>> make: *** [fio] Error 1
>>>
>>> After some googling, I learned that OS X doesn't
>>> provide _posix_memalign, and that apparently it's not
>>> needed on this platform. I "fixed" my compile problem with the
>>> attached patch. You may find it useful to write a better fix for this.
>>
>> I think Apple have added it in 10.6, but obviously fio needs to run on
>> older versions too.
>
> Solaris has a helper, too. Does 10.6 have memalign or another
> alternative function?
We only use it for io_u allocations outside of places where we do have
posix_memalign() support. I just added a simpler malloc() wrapper that
aligns for that purpose, so we don't use posix_memalign() in the core
code anymore.
--
Jens Axboe
prev parent reply other threads:[~2011-04-25 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 3:57 [BUG] [PATCH] Undefined symbols: "_posix_memalign" on Mac OS X Filip Sneppe
2011-04-23 9:42 ` Filip Sneppe
2011-04-23 10:06 ` Bruce Cran
2011-04-25 11:42 ` Jens Axboe
2011-04-25 18:51 ` Jens Axboe [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=4DB5C2BE.6030809@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=bruce@cran.org.uk \
--cc=filip.sneppe@gmail.com \
--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 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.