public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sys-power/nut-2.4.3-r2 fails to compile driver
Date: Thu, 15 Jul 2010 15:25:37 +0300	[thread overview]
Message-ID: <AANLkTikymKIOIADxbTjPGeceY_1JUvLWiOrJ_-LC00LQ@mail.gmail.com> (raw)
In-Reply-To: <4C3E88E4.3000509@gmail.com>

On 7/15/10, Dale <rdalek1967@gmail.com> wrote:
> Hi folks,
>
> I'm trying to upgrade nut to the latest stable version.  I have the
> driver set in make.conf and according to the website, it is the correct
> driver.  I also while searching around noticed I need to make sure I
> have the driver in /lib/nut and sure enough, it is there.  In make.conf
> I have this:
>
> NUT_DRIVERS="cyberpower"
>
> This is the error I am getting:
>
> make[1]: Entering directory
> `/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
> make[1]: *** No rule to make target `cyberpower', needed by `all-am'.  Stop.
> make[1]: Leaving directory
> `/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
> make: *** [all-recursive] Error 1
>   * ERROR: sys-power/nut-2.4.3-r2 failed:
>   *   emake failed
>   *
>   * Call stack:
>   *     ebuild.sh, line   48:  Called src_compile
>   *   environment, line 2904:  Called _eapi2_src_compile
>   *     ebuild.sh, line  640:  Called die
>   * The specific snippet of code:
>   *              emake || die "emake failed"
>   *
>   * If you need support, post the output of 'emerge --info
> =sys-power/nut-2.4.3-r2',
>   * the complete build log and the output of 'emerge -pqv
> =sys-power/nut-2.4.3-r2'.
>   * The complete build log is located at
> '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'.
>   * The ebuild environment file is located at
> '/var/tmp/portage/sys-power/nut-2.4.3-r2/temp/environment'.
>   * S: '/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3'
>
>  >>> Failed to emerge sys-power/nut-2.4.3-r2, Log file:
>
>  >>>  '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
>   *
>   * The following package has failed to build or install:
>   *
>   *  ('ebuild', '/', 'sys-power/nut-2.4.3-r2', 'merge'), Log file:
>   *   '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
>   *
> root@smoker / #
>
> Any idea why it can't make my driver when it is the right one and is set
> in make.conf?  What am I missing?  Oh, this is connected to my serial
> port, NOT the USB port.

Wrong driver combined with outdated website info or other docs?

I have no idea of their driver model but a hunch from the basis of
cups and a quick grep would lead me to suggest that cyberpower driver
possibly no longer exists. It might have been replaced by powerpanel:

drivers/powerpanel.c: * powerpanel.c - Model specific routines for
CyberPower text/binary

-- 
Arttu V. -- Running Gentoo is like running with scissors



  reply	other threads:[~2010-07-15 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  4:04 [gentoo-user] sys-power/nut-2.4.3-r2 fails to compile driver Dale
2010-07-15 12:25 ` Arttu V. [this message]
2010-07-15 17:09   ` Dale
2010-07-15 20:42     ` Dale

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=AANLkTikymKIOIADxbTjPGeceY_1JUvLWiOrJ_-LC00LQ@mail.gmail.com \
    --to=arttuv69@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox