1 |
On 13/07/2015 19:22, hw wrote: |
2 |
> |
3 |
> So what happened to the 'hvm' USE flag of the "xen-tools" package? |
4 |
> |
5 |
> http://gentoobrowse.randomdan.homeip.net/package/app-emulation/xen-tools |
6 |
> says there is such a flag. However: |
7 |
> |
8 |
> |
9 |
> moonflo ~ # equery uses xen-tools |
10 |
> [ Legend : U - final flag setting for installation] |
11 |
> [ : I - package is installed with flag ] |
12 |
> [ Colors : set, unset ] |
13 |
> * Found these USE flags for app-emulation/xen-tools-4.5.1-r1: |
14 |
> U I |
15 |
> - - api : Build the C libxenapi bindings |
16 |
> - - custom-cflags : Build with user-specified CFLAGS |
17 |
> (unsupported) |
18 |
> - - debug : Enable extra debug codepaths, like |
19 |
> asserts and extra output. If you want to get meaningful backtraces see |
20 |
> |
21 |
> https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces |
22 |
> - - doc : Add extra documentation (API, Javadoc, |
23 |
> etc). It is recommended to enable per package instead of globally |
24 |
> - - flask : Enable the Flask XSM module from NSA |
25 |
> - - ovmf : Enable support to boot UEFI guest vm, |
26 |
> needed by hvm |
27 |
> + + pam : Enable pam support |
28 |
> - - pygrub : Install the pygrub boot loader |
29 |
> - - python : Add optional support/bindings for the |
30 |
> Python language |
31 |
> + + python_targets_python2_7 : Build with Python 2.7 |
32 |
> - - qemu : Enable IOEMU support via the use of qemu-dm |
33 |
> - - screen : Enable support for running domain U |
34 |
> console in an app-misc/screen session |
35 |
> - - static-libs : Build static versions of dynamic |
36 |
> libraries as well |
37 |
> - - system-qemu : Using app-emulation/qemu instead of the |
38 |
> bundled one |
39 |
> - - system-seabios : Using sys-firmware/seabios instead of |
40 |
> the bundled one |
41 |
> moonflo ~ # |
42 |
> |
43 |
> |
44 |
> So there is no such flag. Apparently my installation is missing |
45 |
> 'hvmloader', and I'm guessing that I would have that if I could enable |
46 |
> the 'hmv' USE flag. |
47 |
> |
48 |
> How do I enable a USE flag that doesn't seem to exist? |
49 |
> |
50 |
|
51 |
|
52 |
You don't enable a USE flag that does not exist. How could you? It's not |
53 |
there. |
54 |
|
55 |
|
56 |
A primer on USE flags: |
57 |
|
58 |
These set *optional* features for build time, usually by setting options |
59 |
to ./configure at build time (or some equivalent means). If a USE flag |
60 |
goes away, it usually means the feature is no longer optional but now |
61 |
permanently enabled (or sometimes not enabled at all). Or perhaps the |
62 |
upstream build system changed, and USE must correspondingly change. |
63 |
|
64 |
If something that used to work and now doesn't after USE is modified by |
65 |
the dev, then that is a bug, so report it. Sometimes an optional feature |
66 |
that never really worked at all is removed by upstream, which means the |
67 |
USE flag goes away, and that is a discussion you must have with upstream |
68 |
if it breaks stuff for you. |
69 |
|
70 |
Either way, your start point is to touch base with the Gentoo maintainer |
71 |
of the package. |
72 |
|
73 |
|
74 |
|
75 |
-- |
76 |
Alan McKinnon |
77 |
alan.mckinnon@×××××.com |