Flexible I/O Tester development
 help / color / mirror / Atom feed
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 11:46:30 +0200	[thread overview]
Message-ID: <20130412094630.GO12244@kernel.dk> (raw)
In-Reply-To: <CANUChTzQ8yhoyD5v8ZetpqDe_9TWmskeR=wi_o4nYHLSUb8Puw@mail.gmail.com>

On Fri, Apr 12 2013, Gavin Martin wrote:
> On 12 April 2013 09:42, Jens Axboe <axboe@kernel.dk> wrote:
> > On Fri, Apr 12 2013, Gavin Martin wrote:
> >> On 12 April 2013 09:13, Jens Axboe <axboe@kernel.dk> wrote:
> >> > 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
> >> >
> >>
> >> Thanks, this must be a new requirement as I have never needed it for
> >> previous builds.
> >
> > It is a new requirement. It's because I merged the gfio base into the
> > master branch, and gfio client/server uses compression for bigger
> > transmissions. It could be made optional, but zlib-devel should be
> > available on all platforms (I think). A decision will be made regarding
> > that before 2.0.16 (or 2.1, I think it'l be).
> >
> > --
> > Jens Axboe
> >
> 
> It seems that on Sles 11 SP1 it is not included as standard, zlib is
> installed, but not zlib-devel.  Doing a few google searches and it
> seems to be present in the SDK, I'll have a go at downloading that to
> see if it is part of that package.

The package should be a standard part of any develop part of a distro.
Not sure how SLES is done (I used to know :-), but I'd be surprised if
it wasn't directly available.

But sounds like it would be a good idea to turn zlib into a soft
requirement.

-- 
Jens Axboe


  reply	other threads:[~2013-04-12  9:46 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
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 [this message]
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=20130412094630.GO12244@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox