From: Jens Axboe <axboe@kernel.dk>
To: Gavin Martin <gavin_martin@xyratex.com>
Cc: fio@vger.kernel.org
Subject: Re: Unable to Configure latest build
Date: Fri, 12 Apr 2013 10:13:24 +0200 [thread overview]
Message-ID: <20130412081324.GL12244@kernel.dk> (raw)
In-Reply-To: <CANUChTygO-6HnaDU+eufAAtJoGCn9J0UgcEd16+7dgeOXa-92Q@mail.gmail.com>
On Fri, Apr 12 2013, Gavin Martin wrote:
> Hi Jens,
>
> I grabbed the 2.0.15 when it came out and it configured and compiled
> fine, but the latest one from today (12/04) displays errors when
> trying to configure.
>
> I'm not doing anything different to what I was doing for the previous
> builds. Just running ./configure, below is the output from
> config.log;
>
> # FIO configure log Fri Apr 12 08:25:30 BST 2013
> # Configured with: './configure'
> #
> gcc -D_GNU_SOURCE -include config-host.h -c -o
> /tmp/fio-conf-9434-20722-5490.o /tmp/fio-conf-27676-20722-14401.c
> /tmp/fio-conf-27676-20722-14401.c:2:2: error: #error __ANDROID__ not defined
> gcc -D_GNU_SOURCE -include config-host.h -c -o
> /tmp/fio-conf-9434-20722-5490.o /tmp/fio-conf-27676-20722-14401.c
> gcc -D_GNU_SOURCE -include config-host.h -c -o
> /tmp/fio-conf-9434-20722-5490.o /tmp/fio-conf-27676-20722-14401.c
> /tmp/fio-conf-27676-20722-14401.c:2:2: error: #error __i386__ not defined
> gcc -D_GNU_SOURCE -include config-host.h -c -o
> /tmp/fio-conf-9434-20722-5490.o /tmp/fio-conf-27676-20722-14401.c
> Compiling test case cross
> gcc -D_GNU_SOURCE -include config-host.h -o
> /tmp/fio-conf-3040-20722-23652.exe /tmp/fio-conf-27676-20722-14401.c
> Compiling test case endian
> gcc -D_GNU_SOURCE -include config-host.h -o
> /tmp/fio-conf-3040-20722-23652.exe /tmp/fio-conf-27676-20722-14401.c
> Compiling test case wordsize
> gcc -D_GNU_SOURCE -include config-host.h -DWORDSIZE=32 -o
> /tmp/fio-conf-3040-20722-23652.exe /tmp/fio-conf-27676-20722-14401.c
> /tmp/fio-conf-27676-20722-14401.c: In function �main�:
> /tmp/fio-conf-27676-20722-14401.c:5: error: size of array �type name�
> is negative
> Compiling test case wordsize
> gcc -D_GNU_SOURCE -include config-host.h -DWORDSIZE=64 -o
> /tmp/fio-conf-3040-20722-23652.exe /tmp/fio-conf-27676-20722-14401.c
> Compiling test case zlib
> gcc -D_GNU_SOURCE -include config-host.h -o
> /tmp/fio-conf-3040-20722-23652.exe /tmp/fio-conf-27676-20722-14401.c
> -lz
> /tmp/fio-conf-27676-20722-14401.c:1:18: error: zlib.h: No such file or directory
> /tmp/fio-conf-27676-20722-14401.c: In function �main�:
> /tmp/fio-conf-27676-20722-14401.c:4: error: �z_stream� undeclared
> (first use in this function)
> /tmp/fio-conf-27676-20722-14401.c:4: error: (Each undeclared
> identifier is reported only once
> /tmp/fio-conf-27676-20722-14401.c:4: error: for each function it appears in.)
> /tmp/fio-conf-27676-20722-14401.c:4: error: expected �;� before �stream�
> /tmp/fio-conf-27676-20722-14401.c:5: error: �stream� undeclared (first
> use in this function)
> /tmp/fio-conf-27676-20722-14401.c:5: error: �Z_OK� undeclared (first
> use in this function)
>
> This is on a SLES11 SP1 x86_64 machine, I don't know enough to see if
> I am doing something wrong, but it has worked on previous builds.
You need the zlib devel libraries installed, configure should have told
you that. Ala:
ERROR
ERROR: User requested feature zlib
ERROR: configure was not able to find it
ERROR
Configure failed, check config.log and/or the above output
Not sure what that package is called on SLES, but probably zlib-devel.
--
Jens Axboe
next prev parent reply other threads:[~2013-04-12 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 7:40 Unable to Configure latest build Gavin Martin
2013-04-12 8:13 ` Jens Axboe [this message]
2013-04-12 8:27 ` Gavin Martin
2013-04-12 8:42 ` Jens Axboe
2013-04-12 9:31 ` Gavin Martin
2013-04-12 9:46 ` Jens Axboe
2013-04-12 11:13 ` Jens Axboe
2013-04-12 11:31 ` Gavin Martin
2013-04-12 11:34 ` Jens Axboe
2013-04-12 12:17 ` Jens Axboe
2013-04-12 10:55 ` Greg Freemyer
2013-04-12 11:16 ` Gavin Martin
2013-04-14 10:01 ` Greg Freemyer
2013-04-14 11:47 ` Jens Axboe
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=20130412081324.GL12244@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=gavin_martin@xyratex.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.