v18 LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: v18 LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) (/showthread.php?tid=298461) Pages:
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
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
|
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 07:25)techie67 Wrote: Hi milhouse, Check that you haven't run out of disk space - it looks like Kodi may be having trouble reading from, or writing to, /storage. It looks like Safe Mode is starting, and writing out a fresh guisettings.xml, then crashing because it can't read the guisettings.xml file it has just created (possibly because the /storage file system is out of space). RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - smp1 - 2018-07-31 @Milhouse Did you have any trouble building with flatbuffers package? My build fails unless I remove flatbuffers. Code: [i][i][i][i][i]../include/flatbuffers/flatbuffers.h:1200:24: error: 'i' was not declared in this scope RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - ktfzone - 2018-07-31 (2018-07-27, 19:22)asavah Wrote: @ktfzone is you pi3 a pi3b or pi3b+?I tried that, it appeared to make things worse. Plus the buffering happened on a RPI2 that worked flawlessly with the exact same movie a couple of months ago, I don't remember on what version I was back then. I will try to install 17.3 on a different card and see how it goes. I never saw the buffering stuff in the past , nor should I, all my stuff is on local LAN. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 15:14)smp1 Wrote: @Milhouse No build issues right now - I just did 6 clean builds (RPi/RPi2/Generic, current kernel and 4.18-rc7) that included the flatbuffers package and no build issues. Note that I haven't been including https://github.com/xbmc/xbmc/pull/14209 since #0727 due to rebase issues (which might be resolved now, will try building it again later). I'll try building in a plain VM too. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - popcornmix - 2018-07-31 (2018-07-31, 16:28)ktfzone Wrote: I tried that, it appeared to make things worse. Plus the buffering happened on a RPI2 that worked flawlessly with the exact same movie a couple of months ago, I don't remember on what version I was back then. I will try to install 17.3 on a different card and see how it goes. I never saw the buffering stuff in the past , nor should I, all my stuff is on local LAN. See if you can identify an older build that works correctly. If you can't it will be something on your network. I once had terrible network performance. I found I'd configured a device with a static IP address that collided with the DHCP one of the device with the problem. A dodgy ethernet lead could also be causing this. Try disconnecting other devices from network and swap ethernet cables. Another possibility is it's a problem on the server hosting the files. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 16:41)Milhouse Wrote:(2018-07-31, 15:14)smp1 Wrote: @Milhouse @smp1 I get this build failure when building the flatbuffers package in a minimalist Ubuntu 16.04 VM: http://ix.io/1iQt, but no problems with my normal Ubuntu 17.10 build machine. Hmmm. Edit: this is the initial error http://ix.io/1iQy - after that it just logs thousands upon thousands of errors from the flatbuffer package. Not sure what would cause this difference between the two build systems I have available to me, and I'm not currently able to look into this right now. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - asavah - 2018-07-31 CXXFLAGS += -std=c++11 should help if memory serves g++ 5.3 in ubuntu 16.04 defaults to std=gnu++98, which lacks lots of stuff, however this should be checked and set properly by cmake, if it's not than it's a bug in the package itself and should be reported to package maintainers. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 19:55)asavah Wrote: CXXFLAGS += -std=c++11 should help I'll try it a bit later (or if you have a patch!) I added the start of the log which includes the initial (and relevant) error. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - asavah - 2018-07-31 > I'll try it a bit later (or if you have a patch!) Nope, sorry, I build using gcc 7.3 (host) and 8.2 (cross), builds fine here. I'll take a look at cmake stuff on a 16.04 VM I have handy. https://github.com/google/flatbuffers/blob/master/CMakeLists.txt#L123 <- that's what they do, it should be enough ... Heh found it - https://github.com/google/flatbuffers/blob/master/CMakeLists.txt#L111 if CMAKE_TOOLCHAIN_FILE exists it won't add std= flag thus the build will fail on older gcc, just force add -std=c++0x -faligned-new to CXXFLAGS when cross compiling. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 19:55)asavah Wrote: CXXFLAGS += -std=c++11 should help Yeah... from 16.04 VM (which fails):
and from 17.10 (which works):
Both are wrong, of course, as in both cases it's building with gcc-8.1.0 - what the package is doing is detecting the build host gcc version not the $TOOLCHAIN version (even though that is what it claims to be using). So it's possibly a little more involved than setting CXXFLAGS. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - asavah - 2018-07-31 I edited my post, check the remark about the CMAKE_TOOLCHAIN_FILE Edit: Hmm in my buildsystem it detects both compilers right host:
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 I'm not a cmake expert (or even a compilation expert, I mostly just push buttons and hope it works!), but it looks like when building flatbuffers for the host it uses the build host gcc (ie. in my case gcc-5.4.0 on 16.04 and gcc-7.2.0 on 17.10), but when cross compiling for the target it correctly uses gcc-8.1.0 from $TOOLCHAIN - the following is from 17.10 (as 16.04 failed during the host build):
Somehow we need the host build to use the correct $TOOLCHAIN path(s). RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - asavah - 2018-07-31 >I'm not a cmake expert (or even a compilation expert, I mostly just push buttons and hope it works!) +1 Push button, read logs, try to make sense of cryptic error messages, google it, try to fix, rinse and repeat >Somehow we need the host build to use the correct $TOOLCHAIN path(s). Ahh, yes, I stumbled into this long ago. My solution was to use CMAKE_TOOLCHAIN_FILE for host too, with the right values and pathes of course. As further improvement to this I dynamically generate CMAKE_TOOLCHAIN_FILE and toolchain.meson hints with a python script, as my build-crap-system is heavily python-based it was trivial to do. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - Milhouse - 2018-07-31 (2018-07-31, 21:18)asavah Wrote: >I'm not a cmake expert (or even a compilation expert, I mostly just push buttons and hope it works!) Yes, exactly! (2018-07-31, 21:18)asavah Wrote: >Somehow we need the host build to use the correct $TOOLCHAIN path(s). Yes, this seems to be a fundamental issue with the LE "cmake" buildsystem - it's not specific to the flatbuffers package, it's every host package we build with cmake is identifying the "wrong" (ie. host) gcc version rather than the toolchain host-gcc version. It's just that flatbuffers craps out after identifying the wrong gcc whereas other packages build successfully, so I think this needs to be fixed across the board and then flatbuffers should build successfully for LibreELEC. But PR14209 doesn't currently build anyway, so not building flatbuffers is probably the best option for now! Hopefully one of my colleagues will be able to dig into this - I'll point them at your posts, we already generate the various config scripts but maybe we're missing something vital for host... RE: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0) - asavah - 2018-07-31 That's what my cmake toolchain file for host looks like https://gist.github.com/asavah/7eb88c16533b4d94bb58b7bca69d70c3 I don't bother building a toolchain for host, but I do prefer telling cmake how to deal with eg. RPATH or ccache. If necesary *FLAGS get added later by the buildsystem itself depending on what a particular package may want. Hope this helps. |