From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-153702-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 01E2A1387AB
for <garchives@archives.gentoo.org>; Sat, 8 Feb 2014 18:07:40 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 5DD2BE0B11;
Sat, 8 Feb 2014 18:07:34 +0000 (UTC)
Received: from mail-yh0-f49.google.com (mail-yh0-f49.google.com [209.85.213.49])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 23B38E0B09
for <gentoo-user@lists.gentoo.org>; Sat, 8 Feb 2014 18:07:32 +0000 (UTC)
Received: by mail-yh0-f49.google.com with SMTP id t59so3703904yho.22
for <gentoo-user@lists.gentoo.org>; Sat, 08 Feb 2014 10:07:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:sender:date:message-id:subject:from:to:content-type;
bh=1y9ztaqaBRrAtyLtigFa30GBOJ+bi9uhF5dsAH1co1s=;
b=F0v9WNcDOpKfmLOQS8QJEHPnT/O9DxAet2bhR1lvY+WvyHikT+kLiqkM6TEVzeUJOu
6zkTmiOjq/hOVWfAPEpDmZuYXlzOKTvjlBEbF4lzOjfepK6K2EZ+TcKiIunycwM0/++K
7axC4NiN3fIMt4ilRjDS44kfji5jQd0VtQcS1YcSaunZ+WoXuefz4MOPP94tdeAzjJFa
pbI2yyNhpKHoql5qXTz2tC8Cm5fq4q6+vk70Rdzin3yBkpR0xxjxSXkfP9pl8hrMjTyy
pKHmwwYCVjigFM+Uk/fsImOE5K8V+cRxJkl6VCw0cziE0GECxrbI/2ihV3w8PWjcPetn
Zc6g==
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.236.129.198 with SMTP id h46mr17759307yhi.17.1391882851891;
Sat, 08 Feb 2014 10:07:31 -0800 (PST)
Sender: scotte.sandiego@gmail.com
Received: by 10.170.64.145 with HTTP; Sat, 8 Feb 2014 10:07:31 -0800 (PST)
Date: Sat, 8 Feb 2014 10:07:31 -0800
X-Google-Sender-Auth: 02juO4secILtOsmo12OZlRtnzBY
Message-ID: <CAJ7Ptmze4FZ4H4HZ5nAWvMLmoYQGa2tpuUEMaL4wmeyY8_RpGQ@mail.gmail.com>
Subject: [gentoo-user] Failure of zfs-kmod with 3.13.* kernel
From: Scott Ellis <scotte@warped.com>
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=20cf300e4eedf4bf8304f1e8fab0
X-Archives-Salt: 3e7f92d0-7700-4914-a625-29ab445c920c
X-Archives-Hash: 1715b54c9c89e23ed94c8b0bfc57b0de
--20cf300e4eedf4bf8304f1e8fab0
Content-Type: text/plain; charset=ISO-8859-1
When trying to build zfs-kmod against a a 3.13.[0|1|2] kernel, spl works
fine, but zfs fails. It looks like the issue is that the configure script
isn't doing quite the right check for bdi_setup_and_register, so
HAVE_BDI_SETUP_AND_REGISTER doesn't get defined, and then there's a
mismatch in the definitions between zfs and the kernel source. The
offending bit in the configure log looks to be:
configure:17996: checking whether bdi_setup_and_register() is available
configure:18024: cp conftest.c build && make modules -C /usr/src/linux
EXTRA_CFLAGS=-Werror
M=/var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build
/var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build/conftest.c:
In function 'main':
/var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build/conftest.c:91:25:
error: ignoring return value of 'bdi_setup_and_register', declared with
attribute warn_unused_result [-Werror=unused-result]
bdi_setup_and_register(NULL, NULL, 0);
^
Anyone else seeing this?
--20cf300e4eedf4bf8304f1e8fab0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>When trying to build zfs-kmod against a a 3.13.[0|1|2=
] kernel, spl works fine, but zfs fails. It looks like the issue is t=
hat the configure script isn't doing quite the right check for bdi_setu=
p_and_register, so HAVE_BDI_SETUP_AND_REGISTER doesn't get defined, and=
then there's a mismatch in the definitions between zfs and the kernel =
source. The offending bit in the configure log looks to be:<br>
<br><br>configure:17996: checking whether bdi_setup_and_register() is avail=
able<br>configure:18024: cp conftest.c build && make modules -C /us=
r/src/linux EXTRA_CFLAGS=3D-Werror M=3D/var/tmp/portage/sys-fs/=
zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build<br>
/var/tmp/portage/sys-fs/zfs-kmod-0.6.2-r3/work/zfs-zfs-0.6.2/build/conftest=
.c: In function ‘main’:<br>/var/tmp/portage/sys-fs/zfs-kmod-0.6=
.2-r3/work/zfs-zfs-0.6.2/build/conftest.c:91:25: error: ignoring return val=
ue of ‘bdi_setup_and_register’, declared with attribute warn_un=
used_result [-Werror=3Dunused-result]<br>
bdi_setup_and_register(NULL, NULL, 0);<br> &n=
bsp;  =
; ^<br><br></div>Anyone els=
e seeing this?<br></div>
--20cf300e4eedf4bf8304f1e8fab0--