From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: cups-filters failing to build
Date: Mon, 24 Nov 2014 17:26:15 -0800 [thread overview]
Message-ID: <m50lro$rcr$1@ger.gmane.org> (raw)
In-Reply-To: <5473B007.1020905@alectenharmsel.com>
On 11/24/2014 02:24 PM, Alec Ten Harmsel wrote:
> Hey guys,
>
> I've been having a really strange issue with net-print/cups-filters for
> the last few weeks, wondering whether or not it's a bug or I just have
> something configured wrong. Somehow ${S} is defined as:
>
> /var/tmp/portage/net-print/cups-filters-1.0.53/work/cups-filters-3.2.10
You're right. That is a *really* strange error :) Where did that 3.2.10 come
from? I can't reproduce the same error here so I can only guess. Have you
tried grepping for 3.2.10 in /var/tmp/portage/net-print/ ?
Running emerge with the -d flag can sometimes shed some light. More light than
you probably want :)
> and the build predictably fails. Normally this wouldn't bother me (I
> don't use cups at all), except that cups is a build-time dependency for
> dev-java/icedtea.
I see there is a cups USEFLAG for icedtea. Could you unset that flag for
icedtea as a workaround?
A question of my own: the ebuilds for icedtea list the cups flag as +cups.
So far I haven't discovered a man page that explains the + prefix. Is there
such a man page?
next prev parent reply other threads:[~2014-11-25 1:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:24 [gentoo-user] cups-filters failing to build Alec Ten Harmsel
2014-11-25 1:26 ` walt [this message]
2014-11-25 1:35 ` [gentoo-user] " wraeth
2014-11-25 2:04 ` Alec Ten Harmsel
2014-11-25 8:36 ` Neil Bothwick
2014-11-25 9:49 ` [gentoo-user] " Andreas K. Huettel
2014-11-25 14:23 ` Alec Ten Harmsel
2014-11-25 15:41 ` Andreas K. Huettel
2014-11-25 17:56 ` Alec Ten Harmsel
2014-11-25 19:38 ` Andreas K. Huettel
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='m50lro$rcr$1@ger.gmane.org' \
--to=w41ter@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