From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: xfs@oss.sgi.com, fstests@vger.kernel.org
Subject: Re: xfstests configure error with xfsprogs v4.5-rc1
Date: Mon, 22 Feb 2016 14:24:50 +1100 [thread overview]
Message-ID: <20160222032450.GF14668@dastard> (raw)
In-Reply-To: <20160222030304.GV11419@eguan.usersys.redhat.com>
On Mon, Feb 22, 2016 at 11:03:04AM +0800, Eryu Guan wrote:
> Hi,
>
> After upgrading to xfsprogs v4.5-rc1 version, xfstests failed to built
> because of configure error:
>
> checking xfs/xfs.h usability... no
> checking xfs/xfs.h presence... yes
> configure: WARNING: xfs/xfs.h: present but cannot be compiled
> configure: WARNING: xfs/xfs.h: check for missing prerequisite headers?
> configure: WARNING: xfs/xfs.h: see the Autoconf documentation
> configure: WARNING: xfs/xfs.h: section "Present But Cannot Be Compiled"
> configure: WARNING: xfs/xfs.h: proceeding with the compiler's result
> checking for xfs/xfs.h... no
>
> FATAL ERROR: cannot find a valid <xfs/xfs.h> header file.
> Run "make install-qa" from the xfsprogs source.
>
> and config.log showed:
>
> configure:4543: checking xfs/xfs.h usability
> configure:4543: ccache gcc -c -g -O2 conftest.c >&5
> In file included from /usr/include/xfs/xfs.h:37:0,
> from conftest.c:73:
> /usr/include/xfs/linux.h:145:1: error: unknown type name 'off64_t'
> typedef off64_t xfs_off_t;
> ^
> configure:4543: $? = 1
That would seem like a system library problem in that it doesn't
define off64_t through stdio.h. What distro are you compiling on?
Also, if you set _GNU_SOURCE, does it then compile? e.g. see
m4/package_libcdev.m4 for how to test whether code compiles under
certain defines.
If it does compile with _GNU_SOURCE being set, then all that needs
to be is to update the autoconf rule.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: xfstests configure error with xfsprogs v4.5-rc1
Date: Mon, 22 Feb 2016 14:24:50 +1100 [thread overview]
Message-ID: <20160222032450.GF14668@dastard> (raw)
In-Reply-To: <20160222030304.GV11419@eguan.usersys.redhat.com>
On Mon, Feb 22, 2016 at 11:03:04AM +0800, Eryu Guan wrote:
> Hi,
>
> After upgrading to xfsprogs v4.5-rc1 version, xfstests failed to built
> because of configure error:
>
> checking xfs/xfs.h usability... no
> checking xfs/xfs.h presence... yes
> configure: WARNING: xfs/xfs.h: present but cannot be compiled
> configure: WARNING: xfs/xfs.h: check for missing prerequisite headers?
> configure: WARNING: xfs/xfs.h: see the Autoconf documentation
> configure: WARNING: xfs/xfs.h: section "Present But Cannot Be Compiled"
> configure: WARNING: xfs/xfs.h: proceeding with the compiler's result
> checking for xfs/xfs.h... no
>
> FATAL ERROR: cannot find a valid <xfs/xfs.h> header file.
> Run "make install-qa" from the xfsprogs source.
>
> and config.log showed:
>
> configure:4543: checking xfs/xfs.h usability
> configure:4543: ccache gcc -c -g -O2 conftest.c >&5
> In file included from /usr/include/xfs/xfs.h:37:0,
> from conftest.c:73:
> /usr/include/xfs/linux.h:145:1: error: unknown type name 'off64_t'
> typedef off64_t xfs_off_t;
> ^
> configure:4543: $? = 1
That would seem like a system library problem in that it doesn't
define off64_t through stdio.h. What distro are you compiling on?
Also, if you set _GNU_SOURCE, does it then compile? e.g. see
m4/package_libcdev.m4 for how to test whether code compiles under
certain defines.
If it does compile with _GNU_SOURCE being set, then all that needs
to be is to update the autoconf rule.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-22 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 3:03 xfstests configure error with xfsprogs v4.5-rc1 Eryu Guan
2016-02-22 3:03 ` Eryu Guan
2016-02-22 3:24 ` Dave Chinner [this message]
2016-02-22 3:24 ` Dave Chinner
2016-02-22 8:00 ` Eryu Guan
2016-02-22 8:00 ` Eryu Guan
2016-02-22 10:16 ` Eryu Guan
2016-02-22 10:16 ` Eryu Guan
2016-02-22 21:58 ` Dave Chinner
2016-02-22 21:58 ` Dave Chinner
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=20160222032450.GF14668@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=xfs@oss.sgi.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.