+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: PVR Development (/forumdisplay.php?fid=136)
+--- Thread: New MythTV add-on using libcmyth (/showthread.php?tid=110694)
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
- fiveisalive - 2012-02-23 21:11
Any chance of a sync with https://github.com/opdenkamp/xbmc ? Last sync was Feb 6 and there are some good bug fixes in the main PVR code that would be nice to test with the cmyth add-on.
- tsp42 - 2012-02-24 01:09
Sure. It should be synced know. Sorry for the lack of updates but to much work to do.
- flitter2009 - 2012-02-24 03:37
Thanks tsp! Did this go both ways? Is the libcmyth addon now in the opdenkamp branch? (I'm in xvba land)
- sysadm1n - 2012-02-24 15:45
flitter2009 Wrote:...(I'm in xvba land)
Using the latest fglrx driver from ATI/AMD you don't need to do anything special for xvba. Here's a snippet from my xorg log:
Code:
[ 97.818] (II) Module amdxmm: vendor="X.Org Foundation"
[ 97.818] compiled for 1.4.99.906, module version = 2.0.0
[ 97.818] (II) Loading extension AMDXVOPL
[ 97.818] (II) Loading extension AMDXVBA
[ 97.818] [- XMM_GLX] [I ]glesxXvInit Configureable RGBOutputColorRange
[ 97.854] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):- Jimmer - 2012-02-24 19:52
Hey tsp,
Just a quick note to say that the last merge compiles fine on my Maverick box, but compile always stumbles and falls over on my ATV running Hardy at the point where it's tackling the vdr-vnsi addon. Compile output here:
http://pastebin.com/2AG3BTqQ
any thoughts about what might have changed to affect Hardy but not Maverick?
Jim
- just a ps: I use ccache and wondered if my cache may have become corrupt somehow. Anyway, I completely cleared the cache and still have the same compile errors. Nothing has changed on the box: I use it purely for this branch and never update anything (unless a dependency changes, which I don't think it has?)
Crash on start - neuroGeek - 2012-02-25 22:58
I have been running this version of XBMC for a while, periodically doing a git pull and recompiling. Yesterday I did this and XBMC no longer starts. I updated again today, and recompiled and get the same thing. I have moved my .xbmc folder so that it's trying to start fresh, with no extra plugins or settings, but I get the same error. When I run xbmc, I get this:
Code:
xbmc.bin: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
Aborted (core dumped)
Crash report available at /home/jay/xbmc_crashlog-20120225_153414.logSometimes, I get this instead: http://paste.ubuntu.com/857004/
My crashlog is here: http://paste.ubuntu.com/857008/
- tsp42 - 2012-02-26 00:10
flitter2009: no not yet. I still want to finish the addonGUI code first and get it proper tested.
Jimmer: Maybe an older version of GCC causes it? The latest update may fix the compile error though.
neuroGeek: I saw the same error, but it disappeared after recompiling the latest version (and running apt-get upgrade). Not sure what caused it, other than it seems to be caused by the python interface.
- flitter2009 - 2012-02-26 00:19
Thanks tsp42! Your hard work is well appreciated!
- Jimmer - 2012-02-26 00:31
tsp42 Wrote:Jimmer: Maybe an older version of GCC causes it? The latest update may fix the compile error though.
Could be caused by GCC? I think you're right....
I should have just read the compiler warnings properly! At the bottom of the following files:
lib/platform/threads/mutex.h
lib/platform/threads/threads.h
lib/platform/sockets/sockets.h
xbmc/pvrclients/tvheadend/HTSPData.h
any references to "bool&" after PLATFORM::CCondition need to be changed to simply "bool"
Not sure why an older GCC would hate that, but there you go......
PS found an issue addressing this with LLVM and some other header files on opdenkamp's github. I posted these one's as well, so hopefully a fix will naturally trickle down....
Building trouble - tricky720101 - 2012-02-26 03:14
Hi all,
Having trouble building the latest version of xbmc my system is:
ubuntu 3.0.0.16-generic 32-bit.
I used the script by sysadm1n
The error is:
make[2]: Entering directory `/home/rick/src/xbmc/lib/cpluff/libcpluff'
make[2]: *** No rule to make target `../kazlib/list.c', needed by `list.lo'. Stop.
make[2]: Leaving directory `/home/rick/src/xbmc/lib/cpluff/libcpluff'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rick/src/xbmc/lib/cpluff/libcpluff'
make: *** [lib/cpluff/libcpluff/.libs/libcpluff.a] Error 2
Does anyone know why and how to fix this??
cheers
rick