Skip to content

Conversation

@ColinIanKing
Copy link

DKMS SPL build failure occurs on a clean machine because the configure
script attempts to build a small test C program which fails to link
because libc-dev is not installed at that point even though gcc is
installed.

configure: error:
*** Please make sure the kmod spl devel package for your
*** distribution is installed then try again. If that fails you
*** can specify the location of the spl objects with the
*** '--with-spl-obj=PATH' option.

The most straight forward fix is to state that libc-dev is a dependency
so that it is installed first before SPL is built. Most DKMS builds
just require gcc and build directly against the kernel, but for SPL
we have this pre-build configure step which needs libc-dev.

Signed-off-by: Colin Ian King colin.king@canonical.com

DKMS SPL build failure occurs on a clean machine because the configure
script attempts to build a small test C program which fails to link
because libc-dev is not installed at that point even though gcc is
installed.

configure: error:
        *** Please make sure the kmod spl devel <kernel> package for your
        *** distribution is installed then try again.  If that fails you
        *** can specify the location of the spl objects with the
        *** '--with-spl-obj=PATH' option.

The most straight forward fix is to state that libc-dev is a dependency
so that it is installed first before SPL is built.  Most DKMS builds
just require gcc and build directly against the kernel, but for SPL
we have this pre-build configure step which needs libc-dev.

Signed-off-by: Colin Ian King <colin.king@canonical.com>
@dajhorn
Copy link
Member

dajhorn commented Jan 25, 2016

@ColinIanKing, I recall that libc-dev was excluded to satisfy Debian policy and some corner-case deployment scenarios. Give me a few days to search through old correspondence.

@dajhorn
Copy link
Member

dajhorn commented Feb 1, 2016

@ColinIanKing, is Canonical picking up PPA maintenance?

If I will be doing tail support for Precise and Trusty, then I want to minimize testing workload. Past that, I'm indifferent to tweaking things for Wily, especially things that might provide a better upgrade path to Xenial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants