public inbox for eudev@lists.gentoo.org
 help / color / mirror / Atom feed
* [eudev]  eudev-1_beta2-r1 fails configure
@ 2013-01-28  5:05 Dale
  2013-01-28  5:49 ` Dale
  0 siblings, 1 reply; 5+ messages in thread
From: Dale @ 2013-01-28  5:05 UTC (permalink / raw
  To: eudev

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

:-)  :-) 

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [eudev]  eudev-1_beta2-r1 fails configure
  2013-01-28  5:05 [eudev] eudev-1_beta2-r1 fails configure Dale
@ 2013-01-28  5:49 ` Dale
  2013-01-28 11:49   ` Anthony G. Basile
       [not found]   ` <51067E8C.9000404@gentoo.org>
  0 siblings, 2 replies; 5+ messages in thread
From: Dale @ 2013-01-28  5:49 UTC (permalink / raw
  To: eudev

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

:-)  :-) 

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [eudev]  eudev-1_beta2-r1 fails configure
  2013-01-28  5:49 ` Dale
@ 2013-01-28 11:49   ` Anthony G. Basile
       [not found]   ` <51067E8C.9000404@gentoo.org>
  1 sibling, 0 replies; 5+ messages in thread
From: Anthony G. Basile @ 2013-01-28 11:49 UTC (permalink / raw
  To: eudev

On 01/28/2013 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
>
> :-)  :-)
>
This was an oversight on our part.  We need a kmod? ( sys-apps/kmod )  
It was caught in bug #454386.

Thanks for the report!!  When/if this list gets busy, open bug reports 
rather than emailing because otherwise we'll forgot ... or at least I 
will :)  I can't search emails like I can bugzilla.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [eudev]  eudev-1_beta2-r1 fails configure
       [not found]   ` <51067E8C.9000404@gentoo.org>
@ 2013-01-28 14:42     ` Dale
       [not found]       ` <510691ED.1070800@gentoo.org>
  0 siblings, 1 reply; 5+ messages in thread
From: Dale @ 2013-01-28 14:42 UTC (permalink / raw
  To: eudev

[-- Attachment #1: Type: text/plain, Size: 4579 bytes --]

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!


[-- Attachment #2: Type: text/html, Size: 6843 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [eudev]  eudev-1_beta2-r1 fails configure
       [not found]       ` <510691ED.1070800@gentoo.org>
@ 2013-01-28 17:47         ` Dale
  0 siblings, 0 replies; 5+ messages in thread
From: Dale @ 2013-01-28 17:47 UTC (permalink / raw
  To: eudev

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

Ian Stakenvicius wrote:
> On 28/01/13 09:42 AM, Dale wrote:
> > Ian Stakenvicius wrote:
> >> [...] 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
>
>
> Yeah that was an issue with the way the flags were set in the virtual.
> That has now been fixed -- USE="kmod" is no longer forced on by
> virtual/udev.
>
>

Ahhh, ok.  I'm no guru but when I run into something, I'll post here,
including any work a rounds I find.  Sometimes I run into things that
are not really broken so I don't generally file roach reports unless I
know for sure.

Thanks for the good work tho.

Dale

:-)  :-)

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


[-- Attachment #2: Type: text/html, Size: 1973 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-01-28 17:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-28  5:05 [eudev] eudev-1_beta2-r1 fails configure Dale
2013-01-28  5:49 ` Dale
2013-01-28 11:49   ` Anthony G. Basile
     [not found]   ` <51067E8C.9000404@gentoo.org>
2013-01-28 14:42     ` Dale
     [not found]       ` <510691ED.1070800@gentoo.org>
2013-01-28 17:47         ` Dale

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox