iozone compilation failure with uclibc due to aio
Carmelo AMOROSO
carmelo.amoroso at st.com
Wed Dec 12 14:16:45 UTC 2012
On 10/12/2012 18.27, Rich Felker wrote:
> On Mon, Dec 10, 2012 at 05:43:54PM +0530, Madhu koriginja wrote:
>> Hi All,
>> I am facing compilation issue with the iozone compilation failure with
>> uclibc library.
>> I am using the uclibc 0.9.32 version, gcc 4.5 linaro toolchain.
>> The same code is compiling with the gcc 4.5 linaro toolchain and glibc
>> 2.14.
>> Please help me to resolve this issue. Please see the compilation error
>> below:
>>
>> [...]
>> arm-openwrt-linux-uclibcgnueabi-gcc -c -O3 -Dunix -Dlinux -DHAVE_ANSIC_C
>> -DASYNC_IO \
>> -D_LARGEFILE64_SOURCE -Os -pipe -march=armv7-a
>> -mtune=cortex-a9 -fno-caller-saves -fhonour-copts -msoft-float libasync.c
>> -o libasync.o
>> libasync.c:98:17: fatal error: aio.h: No such file or directory
>> compilation terminated.
>
> As far as I know, uClibc does not implemnt the AIO part of POSIX. Is
> there perhaps any way to make iozone use some fallback in place of
> AIO? It's not like POSIX AIO is a particularly well-designed API that
> anybody would actually WANT to use...
>
> If there's really no way around it, you could see if someone could
> help you getting AIO added to uClibc.
>
> Rich
FYI,
We (@ST) do use iozone on uClibc with the AIO support switched off w/o
problems.
So as Rich suggested, there is a way to use a fallback solution.
I guess that not passing -DASYNC_IO should make the trick.
Carmelo
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://lists.busybox.net/mailman/listinfo/uclibc
>
>
More information about the uClibc
mailing list