From: Mike Gilbert <floppym@gentoo.org>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: [MERGE] Add a --disable-zfs configure flag.
Date: Sat, 04 Feb 2012 15:46:10 -0500 [thread overview]
Message-ID: <4F2D9912.5040702@gentoo.org> (raw)
In-Reply-To: <4F2D8FD8.40604@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2443 bytes --]
On 02/04/2012 03:06 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 04.02.2012 20:56, Mike Gilbert wrote:
>> I happen to have the ZFS libraries installed on my machine, but I don't
>> want my boot loader to use them. It seems to be broken for me at the
>> moment in any case.
>>
>> I'm new to bazaar and this is my first submission to this mailing list,
>> so please let me know if I've done something incorrectly.
> It's not maintainable to disable a feature every time we meet an issue
> with a part of code.
There is no maintenance burden here, just a one-time change to
configure.ac. The code already has the proper #ifdefs and whatnot.
Also, this goes beyond my own build issues. Having configure auto-detect
libraries with no way to manually override it creates an "automagic
dependency", which we hate over at Gentoo Linux. The following link has
a great explanation.
http://www.gentoo.org/proj/en/qa/automagic.xml
> Could you please detail on your issues?
I'm getting the following build failure:
gcc -DHAVE_CONFIG_H -I. -Wall -W -I./include -DGRUB_UTIL=1
-DGRUB_LIBDIR=\"/usr/local/lib/grub\"
-DLOCALEDIR=\"/usr/local/share/locale\" -DGRUB_MACHINE_PCBIOS=1
-DGRUB_MACHINE=I386_PC -DGRUB_TARGET_CPU_I386=1
-DGRUB_FILE=\"util/getroot.c\" -I. -I. -I. -I. -I./include -I./include
-I./grub-core/gnulib -I./grub-core/gnulib -Wno-undef
-Wno-sign-compare -Wno-unused -Wno-unused-parameter -MT
util/libgrubkern_a-getroot.o -MD -MP -MF
util/.deps-util/libgrubkern_a-getroot.Tpo -c -o
util/libgrubkern_a-getroot.o `test -f 'util/getroot.c' || echo
'./'`util/getroot.c
util/getroot.c:2384:1: error: unknown type name 'libzfs_handle_t'
util/getroot.c: In function 'fini_libzfs':
util/getroot.c:2389:3: warning: implicit declaration of function
'libzfs_fini' [-Wimplicit-function-declaration]
util/getroot.c: At top level:
util/getroot.c:2392:1: error: unknown type name 'libzfs_handle_t'
util/getroot.c: In function 'grub_get_libzfs_handle':
util/getroot.c:2397:7: warning: implicit declaration of function
'libzfs_init' [-Wimplicit-function-declaration]
util/getroot.c:2397:23: warning: assignment makes pointer from integer
without a cast [enabled by default]
I have the libzfs headers in /usr/include/libzfs, which is where the ZFS
on Linux build system puts them. My best guess is that it isn't finding
libzfs.h, but I haven't really dug in.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2012-02-04 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 19:56 [MERGE] Add a --disable-zfs configure flag Mike Gilbert
2012-02-04 20:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-04 20:46 ` Mike Gilbert [this message]
2012-02-04 21:41 ` Richard Laager
2012-02-04 22:13 ` Mike Gilbert
2012-02-04 22:36 ` Mike Gilbert
2012-02-05 1:12 ` Mike Gilbert
2012-02-05 3:40 ` Darik Horn
2012-02-05 5:44 ` Mike Gilbert
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=4F2D9912.5040702@gentoo.org \
--to=floppym@gentoo.org \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.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.