summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/011/review/28596630
blob: 0421c99f981ce3015f68f9c98f95cedeeb4eccba (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
semantic: 0.095
device: 0.093
other: 0.090
permissions: 0.085
PID: 0.079
network: 0.075
socket: 0.068
performance: 0.066
graphic: 0.066
files: 0.062
vnc: 0.058
debug: 0.056
boot: 0.055
KVM: 0.052
debug: 0.304
files: 0.184
other: 0.115
PID: 0.058
socket: 0.056
device: 0.049
network: 0.044
vnc: 0.041
performance: 0.037
boot: 0.033
semantic: 0.027
KVM: 0.021
permissions: 0.018
graphic: 0.014

[Qemu-devel] [BUG] [low severity] a strange appearance of message involving slirp while doing "empty" make

Folks,

If qemu tree is already fully built, and "make" is attempted, for 3.1, the 
outcome is:

$ make
        CHK version_gen.h
$

For 4.0-rc0, the outcome seems to be different:

$ make
make[1]: Entering directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
        CHK version_gen.h
$

Not sure how significant is that, but I report it just in case.

Yours,
Aleksandar

On 20/03/2019 22.08, Aleksandar Markovic wrote:
>
Folks,
>
>
If qemu tree is already fully built, and "make" is attempted, for 3.1, the
>
outcome is:
>
>
$ make
>
CHK version_gen.h
>
$
>
>
For 4.0-rc0, the outcome seems to be different:
>
>
$ make
>
make[1]: Entering directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
>
make[1]: Nothing to be done for 'all'.
>
make[1]: Leaving directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
>
CHK version_gen.h
>
$
>
>
Not sure how significant is that, but I report it just in case.
It's likely because slirp is currently being reworked to become a
separate project, so the makefiles have been changed a little bit. I
guess the message will go away again once slirp has become a stand-alone
library.

 Thomas

On Fri, 22 Mar 2019 at 04:59, Thomas Huth <address@hidden> wrote:
>
On 20/03/2019 22.08, Aleksandar Markovic wrote:
>
> $ make
>
> make[1]: Entering directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
>
> make[1]: Nothing to be done for 'all'.
>
> make[1]: Leaving directory '/home/build/malta-mips64r6/qemu-4.0/slirp'
>
>       CHK version_gen.h
>
> $
>
>
>
> Not sure how significant is that, but I report it just in case.
>
>
It's likely because slirp is currently being reworked to become a
>
separate project, so the makefiles have been changed a little bit. I
>
guess the message will go away again once slirp has become a stand-alone
>
library.
Well, we'll still need to ship slirp for the foreseeable future...

I think the cause of this is that the rule in Makefile for
calling the slirp Makefile is not passing it $(SUBDIR_MAKEFLAGS)
like all the other recursive make invocations. If we do that
then we'll suppress the entering/leaving messages for
non-verbose builds. (Some tweaking will be needed as
it looks like the slirp makefile has picked an incompatible
meaning for $BUILD_DIR, which the SUBDIR_MAKEFLAGS will
also be passing to it.)

thanks
-- PMM