From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eudev+bounces-17-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 5D05713870D
	for <garchives@archives.gentoo.org>; Mon, 28 Jan 2013 14:42:21 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 1A5B021C009;
	Mon, 28 Jan 2013 14:42:20 +0000 (UTC)
Received: from mail-yh0-f52.google.com (mail-yh0-f52.google.com [209.85.213.52])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 8664421C009
	for <eudev@lists.gentoo.org>; Mon, 28 Jan 2013 14:42:19 +0000 (UTC)
Received: by mail-yh0-f52.google.com with SMTP id q46so400119yhf.11
        for <eudev@lists.gentoo.org>; Mon, 28 Jan 2013 06:42:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:x-enigmail-version:content-type;
        bh=RA2LuXREAJxPtDgnVSuvOqBmXjYYttCOYplVMXTz47U=;
        b=RC+8CU2UfGyJd/SwsBSINhzFSqcoWIsIMccnTWyTYrTnCbUKRiH8zXiaMQvA6ANtYj
         oteQYWH8lg94re1TF+IaUcTeog9MfkMgsad2yNyvIFewUJuouSuQU1CeQv5mSG5CemA6
         Vr6Ur+pR0pYADuY7Zl16uaisgkW4u//1ygzjrUXJCaJWT6rUMFJ3CHnXDejhwA3fcosU
         gl1/ZAK6l6sVm8IXGCuEeY2neOwXZOny43PkGX8GWXc0V0rVYrj35Pzdd8bY7XTrJZTc
         buVcStrEw7KhSw44mFs0O6Zsq30/8NKXUNs+t4NcCvOmZUYCdBizHOtQmP0nHiVRYdjv
         Xu3g==
X-Received: by 10.236.116.135 with SMTP id g7mr15084067yhh.85.1359384138627;
        Mon, 28 Jan 2013 06:42:18 -0800 (PST)
Received: from [192.168.2.5] (adsl-74-240-57-140.jan.bellsouth.net. [74.240.57.140])
        by mx.google.com with ESMTPS id z43sm10177121yhn.11.2013.01.28.06.42.16
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 28 Jan 2013 06:42:17 -0800 (PST)
Message-ID: <51068E47.5010502@gmail.com>
Date: Mon, 28 Jan 2013 08:42:15 -0600
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.1
Precedence: bulk
List-Post: <mailto:eudev@lists.gentoo.org>
List-Help: <mailto:eudev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:eudev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:eudev+subscribe@lists.gentoo.org>
List-Id: eudev mailing list <eudev.gentoo.org>
X-BeenThere: eudev@gentoo.org
X-BeenThere: eudev@lists.gentoo.org
MIME-Version: 1.0
To: eudev@lists.gentoo.org
Subject: Re: [eudev]  eudev-1_beta2-r1 fails configure
References: <5106070C.3080708@gmail.com> <51061185.4060709@gmail.com> <51067E8C.9000404@gentoo.org>
In-Reply-To: <51067E8C.9000404@gentoo.org>
X-Enigmail-Version: 1.5
Content-Type: multipart/alternative;
 boundary="------------060800060906020903010509"
X-Archives-Salt: 650ef2a5-5366-4f94-9126-1603afd0e37e
X-Archives-Hash: df9808306e98ff964c9bc54608f3cb1a

This is a multi-part message in MIME format.
--------------060800060906020903010509
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Ian Stakenvicius wrote:
> On 28/01/13 12:49 AM, Dale wrote:
> > Dale wrote:
> >> I just ran into this:
> >>
> >> checking for nl_langinfo... yes checking for rmdir... yes
> >> checking for setlocale... yes checking for socket... yes checking
> >> for stpcpy... yes checking for uname... yes checking for library
> >> containing clock_gettime... -lrt checking for library containing
> >> sqrt... -lm checking for gobject-introspection... yes checking
> >> whether unshare is declared... yes checking for GLIB... yes
> >> checking for gtkdoc-check... /usr/bin/gtkdoc-check checking for
> >> gtkdoc-rebase... /usr/bin/gtkdoc-rebase checking for
> >> gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf checking whether to build
> >> gtk-doc documentation... no checking for main in -lkmod... no
> >> configure: error: in
> >> `/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2':
> >> configure: error: --enable-libkmod was given, but test for kmod
> >> failed See `config.log' for more details
> >>
> >> !!! Please attach the following file when seeking support: !!!
> >> /var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2/config.log
> >>
> >>
> * ERROR: sys-fs/eudev-1_beta2-r1 failed (configure phase):
> >> * econf failed * * Call stack: * ebuild.sh, line 93:
> >> Called src_configure * environment, line 3608: Called
> >> econf 'ac_cv_search_cap_init='
> >> 'ac_cv_header_sys_capability_h=yes' 'DBUS_CFLAGS= ' 'DBUS_LIBS=
> >> ' '--with-rootprefix=/'
> >> '--docdir=/usr/share/doc/eudev-1_beta2-r1' '--libdir=/usr/lib64'
> >>
'--with-firmware-path=/usr/lib/firmware/updates:/usr/lib/firmware:/lib/firmware/updates:/lib/firmware'
> >>
> >>
> '--with-html-dir=/usr/share/doc/eudev-1_beta2-r1/html'
> >> '--with-rootlibdir=/lib64' '--exec-prefix=/'
> >> '--enable-split-usr' '--disable-gtk-doc' '--enable-gudev'
> >> '--enable-introspection' '--enable-keymap' '--enable-libkmod'
> >> '--enable-modules' '--disable-selinux' '--disable-static'
> >> '--disable-legacylib' * phase-helpers.sh, line 511: Called
> >> die * The specific snippet of code: * die
> >> "econf failed" * * If you need support, post the output of
> >> `emerge --info '=sys-fs/eudev-1_beta2-r1'`, * the complete build
> >> log and the output of `emerge -pqv '=sys-fs/eudev-1_beta2-r1'`. *
> >> The complete build log is located at
> >> '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/temp/build.log'. * The
> >> ebuild environment file is located at
> >> '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/temp/environment'. *
> >> Working directory:
> >> '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2' *
> >> S: '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2'
> >> root@fireball / #
> >>
> >>
> >> Can someone look this over and see if it is a bug or missed
> >> dependency? I'll do some checking here and report anything I
> >> find.
> >>
> >> Dale
> >>
> >> :-) :-)
> >>
>
> > OK. Did some thinking on this and since I am not a dev or a
> > ebuild writer, it took me a little bit. It seems eudev needs to
> > depend on kmod, not just the kmod USE flag. When I emerged kmod,
> > which removed module-init-tools, then eudev would update normally.
> > I had module-init-tools installed and it seems that the new eudev
> > missed it. I happened to recall reading something about this change
> > a coming on -dev.
>
> > So, someone may want to adjust the ebuild on this one. Portage
> > pointed out it needed the USE flag but seems to have missed the
> > package itself.
>
> > Dale
>
> > :-) :-)
>
>
>
> Hi Dale -- that's not actually true. This is the situation with eudev:
>
> 1 - USE="modutils" <-- this enables or disables all module loading
> support, no matter what the method. If enabled, anything that
> satisfies "virtual/modutils" will suffice for module loading support,
> including kmod[tools].
>
> 2 - USE="kmod" <-- this enables built-in support against libkmod, that
> is, no external programs are called to load modules.
>
>
> So per your config log above, USE="kmod" was set but for whatever
> reason kmod wasn't installed. However, you could have switched form
> m-i-t to kmod without adding USE="kmod" to eudev and everything would
> continue to work.
>
>

Well, it was portage that told me to set the kmod USE flag.  If portage
hadn't told me to set it, for whatever reason it thinks it needs it, I
wouldn't have set it.  As to why it wants it set, I don't know.  I was
just following the instructions it provided.  Was portage wrong, no
clue.  lol

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


--------------060800060906020903010509
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Ian Stakenvicius wrote:<br>
    <span style="white-space: pre;">&gt; On 28/01/13 12:49 AM, Dale
      wrote:<br>
      &gt; &gt; Dale wrote:<br>
      &gt; &gt;&gt; I just ran into this:<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt; checking for nl_langinfo... yes checking for
      rmdir... yes<br>
      &gt; &gt;&gt; checking for setlocale... yes checking for socket...
      yes checking<br>
      &gt; &gt;&gt; for stpcpy... yes checking for uname... yes checking
      for library<br>
      &gt; &gt;&gt; containing clock_gettime... -lrt checking for
      library containing<br>
      &gt; &gt;&gt; sqrt... -lm checking for gobject-introspection...
      yes checking<br>
      &gt; &gt;&gt; whether unshare is declared... yes checking for
      GLIB... yes<br>
      &gt; &gt;&gt; checking for gtkdoc-check... /usr/bin/gtkdoc-check
      checking for<br>
      &gt; &gt;&gt; gtkdoc-rebase... /usr/bin/gtkdoc-rebase checking for<br>
      &gt; &gt;&gt; gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf checking
      whether to build<br>
      &gt; &gt;&gt; gtk-doc documentation... no checking for main in
      -lkmod... no<br>
      &gt; &gt;&gt; configure: error: in<br>
      &gt; &gt;&gt;
      `/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2':<br>
      &gt; &gt;&gt; configure: error: --enable-libkmod was given, but
      test for kmod<br>
      &gt; &gt;&gt; failed See `config.log' for more details<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt; !!! Please attach the following file when seeking
      support: !!!<br>
      &gt; &gt;&gt;
      /var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2/config.log<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt;<br>
      &gt; * ERROR: sys-fs/eudev-1_beta2-r1 failed (configure phase):<br>
      &gt; &gt;&gt; * econf failed * * Call stack: * ebuild.sh, line 93:<br>
      &gt; &gt;&gt; Called src_configure * environment, line 3608:
      Called<br>
      &gt; &gt;&gt; econf 'ac_cv_search_cap_init='<br>
      &gt; &gt;&gt; 'ac_cv_header_sys_capability_h=yes' 'DBUS_CFLAGS= '
      'DBUS_LIBS=<br>
      &gt; &gt;&gt; ' '--with-rootprefix=/'<br>
      &gt; &gt;&gt; '--docdir=/usr/share/doc/eudev-1_beta2-r1'
      '--libdir=/usr/lib64'<br>
      &gt; &gt;&gt;
'--with-firmware-path=/usr/lib/firmware/updates:/usr/lib/firmware:/lib/firmware/updates:/lib/firmware'<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt;<br>
      &gt; '--with-html-dir=/usr/share/doc/eudev-1_beta2-r1/html'<br>
      &gt; &gt;&gt; '--with-rootlibdir=/lib64' '--exec-prefix=/'<br>
      &gt; &gt;&gt; '--enable-split-usr' '--disable-gtk-doc'
      '--enable-gudev'<br>
      &gt; &gt;&gt; '--enable-introspection' '--enable-keymap'
      '--enable-libkmod'<br>
      &gt; &gt;&gt; '--enable-modules' '--disable-selinux'
      '--disable-static'<br>
      &gt; &gt;&gt; '--disable-legacylib' * phase-helpers.sh, line 511:
      Called<br>
      &gt; &gt;&gt; die * The specific snippet of code: * die<br>
      &gt; &gt;&gt; "econf failed" * * If you need support, post the
      output of<br>
      &gt; &gt;&gt; `emerge --info '=sys-fs/eudev-1_beta2-r1'`, * the
      complete build<br>
      &gt; &gt;&gt; log and the output of `emerge -pqv
      '=sys-fs/eudev-1_beta2-r1'`. *<br>
      &gt; &gt;&gt; The complete build log is located at<br>
      &gt; &gt;&gt;
      '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/temp/build.log'. * The<br>
      &gt; &gt;&gt; ebuild environment file is located at<br>
      &gt; &gt;&gt;
      '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/temp/environment'. *<br>
      &gt; &gt;&gt; Working directory:<br>
      &gt; &gt;&gt;
      '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2' *<br>
      &gt; &gt;&gt; S:
      '/var/tmp/portage/sys-fs/eudev-1_beta2-r1/work/eudev-1_beta2'<br>
      &gt; &gt;&gt; root@fireball / #<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt; Can someone look this over and see if it is a bug or
      missed<br>
      &gt; &gt;&gt; dependency? I'll do some checking here and report
      anything I<br>
      &gt; &gt;&gt; find.<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt; Dale<br>
      &gt; &gt;&gt;<br>
      &gt; &gt;&gt; :-) :-)<br>
      &gt; &gt;&gt;<br>
      &gt;<br>
      &gt; &gt; OK. Did some thinking on this and since I am not a dev
      or a<br>
      &gt; &gt; ebuild writer, it took me a little bit. It seems eudev
      needs to<br>
      &gt; &gt; depend on kmod, not just the kmod USE flag. When I
      emerged kmod,<br>
      &gt; &gt; which removed module-init-tools, then eudev would update
      normally.<br>
      &gt; &gt; I had module-init-tools installed and it seems that the
      new eudev<br>
      &gt; &gt; missed it. I happened to recall reading something about
      this change<br>
      &gt; &gt; a coming on -dev.<br>
      &gt;<br>
      &gt; &gt; So, someone may want to adjust the ebuild on this one.
      Portage<br>
      &gt; &gt; pointed out it needed the USE flag but seems to have
      missed the<br>
      &gt; &gt; package itself.<br>
      &gt;<br>
      &gt; &gt; Dale<br>
      &gt;<br>
      &gt; &gt; :-) :-)<br>
      &gt;<br>
      &gt;<br>
      &gt;<br>
      &gt; Hi Dale -- that's not actually true. This is the situation
      with eudev:<br>
      &gt;<br>
      &gt; 1 - USE="modutils" &lt;-- this enables or disables all module
      loading<br>
      &gt; support, no matter what the method. If enabled, anything that<br>
      &gt; satisfies "virtual/modutils" will suffice for module loading
      support,<br>
      &gt; including kmod[tools].<br>
      &gt;<br>
      &gt; 2 - USE="kmod" &lt;-- this enables built-in support against
      libkmod, that<br>
      &gt; is, no external programs are called to load modules.<br>
      &gt;<br>
      &gt;<br>
      &gt; So per your config log above, USE="kmod" was set but for
      whatever<br>
      &gt; reason kmod wasn't installed. However, you could have
      switched form<br>
      &gt; m-i-t to kmod without adding USE="kmod" to eudev and
      everything would<br>
      &gt; continue to work.<br>
      &gt;<br>
      &gt;</span><br>
    <br>
    Well, it was portage that told me to set the kmod USE flag.&nbsp; If
    portage hadn't told me to set it, for whatever reason it thinks it
    needs it, I wouldn't have set it.&nbsp; As to why it wants it set, I
    don't know.&nbsp; I was just following the instructions it provided.&nbsp; Was
    portage wrong, no clue.&nbsp; lol <br>
    <br>
    Dale<br>
    <br>
    :-)&nbsp; :-) <br>
    <br>
    -- <br>
    I am only responsible for what I said ... Not for what you
    understood or how you interpreted my words!<br>
    <br>
  </body>
</html>

--------------060800060906020903010509--