Gentoo Archives: gentoo-user

From: "Iván Pérez Domínguez" <ivanperezdominguez@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] USE flags and configure-time problems
Date: Sun, 14 Jan 2007 19:11:10
Message-Id: 45AA803E.5050105@gmail.com
1 Hi there.
2
3 I just happend to emerge evince and, after half an hour got the
4 following error:
5
6
7 18:07:32 (44.99 KB/s) - `/usr/portage/distfiles/evince-0.6.1.tar.bz2'
8 saved [1212271/1212271]
9
10 * checking ebuild checksums ;-) ...
11 [ ok ]
12 * checking auxfile checksums ;-) ...
13 [ ok ]
14 * checking miscfile checksums ;-) ...
15 [ ok ]
16 * checking evince-0.6.1.tar.bz2 ;-) ...
17 [ ok ]
18 * Please re-emerge app-text/poppler-bindings with the gtk USE flag set
19
20 !!! ERROR: app-text/evince-0.6.1 failed.
21 Call stack:
22 ebuild.sh, line 1626: Called dyn_setup
23 ebuild.sh, line 701: Called qa_call 'pkg_setup'
24 ebuild.sh, line 38: Called pkg_setup
25 evince-0.6.1.ebuild, line 67: Called die
26
27 !!! poppler-bindings needs gtk flag set
28 !!! If you need support, post the topmost build error, and the call
29 stack if relevant.
30
31
32 I understand why this happend, and I know how to solve it.
33
34 My point is: should the RDEPEND and DEPEND syntax in ebuilds be changed
35 so that this kind of problems can be detected before emerging?
36
37 Here's an example. Imagine program A depends on B, and if A is built
38 with use flag "dvi", then it depends on C to be built with use flag
39 dvi2. The following could be A's DEPEND:
40
41 DEPEND="dvi? ([dvi2 C])
42 B"
43
44 This is just an example, and I'm sure there's a different syntax that
45 could be more appropriate.
46
47 What do you this of it?
48
49 Is there any ongoing implementation to solve it in a different way?
50
51 Cheers,
52
53 Ivan.

Attachments

File name MIME type
smime.p7s application/x-pkcs7-signature

Replies

Subject Author
Re: [gentoo-user] USE flags and configure-time problems "Bo Ørsted Andresen" <bo.andresen@××××.dk>
Re: [gentoo-user] USE flags and configure-time problems Avaricen <avaricen@×××××.com>