/srv/irclogs.ubuntu.com/2013/02/07/#ubuntu-x.txt

tjaaltonbryce: what mlankhorst said :) guess it's xserver and at least some drivers today05:55
tjaaltonllvm built, finally07:18
tjaaltonstill no sign of doko or sylvestre07:18
tjaaltonI'll just email them07:18
tjaaltonupdating libdrm for newer mesa snapshot08:52
=== yofel_ is now known as yofel
mlankhorstI guess I better test mesa 9.0.2 now then :P10:07
mlankhorsttime to run the piglit tests I suppose10:16
tjaaltonmeh, how hard can it be to get reprepro signing work.. i've done this before, years ago10:17
RAOFWhat are you trying to do?10:18
tjaaltonto test the builds locally with sbuild10:18
tjaaltonpulling from a local repo10:18
tjaaltoninclude/export works, now sbuild-update claims the pubkey isn't known10:18
RAOFhttp://paste2.org/p/283401710:18
tjaaltonoh :)10:19
* mlankhorst just builds on launchpad with high priority, evil, I know10:19
mlankhorstI do feel guilty about it though, so it's ok!10:19
RAOFtjaalton: Dump in /etc/schroot/setup.d as 60add-local-repository, combine with http://paste.ubuntu.com/1619254/ and you've got a raring-local chroot that builds against ~/Builds10:20
tjaaltonthat's neat10:21
tjaaltonI'll probably use reprepro still for some stuff, but this is good enough for builds :)10:21
mlankhorstbut if I had to test before pushing, I'd probably mess up my own raring chroot/netboot image instead. It can do both :-)10:22
RAOFArsing llvm10:22
RAOFWhat's a man got to do to build mesa in a ppa these days :)10:22
mlankhorstpush dh-exec 0.6 to precise? :P10:23
tjaaltonnext I'd like it to build under /run/shm, guess my ssd will wear more quickly because of sbuilding all the time :)10:23
mlankhorstIt needs 0.3 or newer for building llvm-3.210:23
RAOFtjaalton: Heh. My sbuild config used to also have raring-tmpfs, too, before btrfs-snapshot.10:24
mlankhorsttjaalton: it will kill itself even faster here because I'm using encryption, I tested, it's not cpu limited any more after a fix!10:24
mlankhorstand it's going like 400 mb/s 10:24
RAOFtjaalton: I could probably find the config I was using to do tmpfs stuff.10:25
tjaaltonthat would be nice10:25
tjaaltonmy ssd died after one year, so will try to minimize it's use now10:26
mlankhorstI'm a terrible person, and keep backups for that. :-)10:27
tjaaltonme too, but only of my own $HOME, screw the others :)10:28
tjaaltonor the system files10:28
mlankhorstoh everything important is in a git repository10:28
tjaaltonstill don't have a working smtp config..10:28
RAOFActually, from memory I think it's pretty easy - you mount /var/lib/schroot/tmpfs-overlay in /etc/fstab, then use that as the overlay dir in the schroot config.10:28
mlankhorstsince ssd's have been so fast I've been pretty lazy though. I'm just building from ssd since doing otherwise takes more effort and longer10:29
tjaaltoni have 16 gigs of ram, better use it for something!10:29
mlankhorstI do too10:29
mlankhorstCached:         12110996 kB10:30
mlankhorstit's practically building from memory already10:30
tjaaltonhmm, I should probably clean up my build dir :)10:32
tjaaltona ton of cruft there slowing sbuild down10:33
mlankhorstthat's why I don't use tmpfs ;-)10:33
tjaaltonthe destination is on ssd10:34
tjaaltonE: 60add-local-repository: gpg: keyring `/var/lib/sbuild/apt-keys/secring.gpg' created10:39
tjaaltonE: 60add-local-repository: gpg: keyring `/var/lib/sbuild/apt-keys/pubring.gpg' created10:39
tjaaltonE: 60add-local-repository: gpg: no default secret key: secret key not available10:39
tjaaltonE: 60add-local-repository: gpg: signing failed: secret key not available10:39
tjaaltondid I miss something?10:40
tjaaltonprobably should create the key first :)10:41
tjaaltonmeh, refuses to install llvm-3.2-dev10:47
tjaaltonRAOF: I guess your sbuild runs update too :)10:52
mlankhorstdid I mess up? :s10:58
mlankhorstoh wait in sbuild I suppose10:58
tjaaltonnah, it's the repo10:58
tjaaltonwell, now it's claiming libdrm* is unsigned10:58
tjaaltonthe llvm maintainer promised to add the backend \o/10:59
mlankhorst\o/10:59
tjaaltongrr11:19
tjaalton sbuild-build-depends-mesa-dummy : Depends: libdrm-dev (>= 2.4.39) but it is not going to be installed11:19
mlankhorstyou forgot to bump libdrm-dev? :P11:26
mlankhorstprobably needs to be 2.4.42 there11:27
tjaaltondidn't update the branch yet11:28
tjaaltonthis is the apt resolver failing11:28
tjaaltonrefuses to install stuff from the local repo11:28
tjaaltonok, it was 2.4.42-1 test build that was broken11:31
tjaaltonrebuilt -0u1 and it's fine now11:32
tjaaltonmlankhorst: did you test that it built using shared llvm libs?11:39
tjaaltonI got the same issue with gensymbols11:39
tjaaltonor did i11:40
mlankhorstI'm testing on quantal atm11:41
mlankhorstI want to get the 9.0.2 sru done first :)11:42
tjaaltonI'll pastebin this.. guess it's normal after all11:43
tjaaltonhttp://pastebin.com/8bMUBdDU11:53
tjaaltonhm no :)11:54
mlankhorstdo you have the full debdiff to llvm-3.2 btw? I'm missing radeonsi11:55
mlankhorsthm indeed, tons of symbols11:56
mlankhorstsounds like it statically linked against libgallium or something11:58
mlankhorstsurprise surprise, it probably did11:59
mlankhorstoh well build libgallium dynamically and you're fine12:01
tjaaltonis there a separate option for it?12:03
mlankhorstone line hack would be noinst_LTLIBRARIES -> lib_LTLIBRARIES12:04
mlankhorstin src/gallium/auxiliary/Makefile.am, but no idea if it works yet12:05
tjaaltonok12:05
tjaaltonwth, the diff with the upstream branch shows changes all over the place12:08
mlankhorstaw still broken12:12
mlankhorstgrabbing rbug, svga and some vmw symbols12:13
mlankhorstcould be fixed in the same way I suppose12:14
mlankhorsteither that or I just hack in the visibility things for now12:14
mlankhorstprobably better for now12:17
tjaaltonso my merge of git master on jan 9th created issues12:19
tjaaltondunno what's the best way to get out of it, other than maybe cleaning them up in a separate commit, or losing history of debian/12:22
mlankhorstdo you want to rewind?12:23
mlankhorstor move forward12:23
tjaaltonwell, rewind wouldn't be that bad12:24
tjaaltonI guess..12:24
mlankhorstwell trying to build it atm, hopefully working this time by adding some visibility cflags back12:27
tjaaltonI'll rebuild the branch, first merge whatever was there before the bad merge, then cherry pick the commits to debian/ after that12:30
mlankhorstdown a lot of symbols..12:31
mlankhorststill missed a few12:31
mlankhorstdriver_descriptor@Base remaining12:37
mlankhorstas good as it gets I suppose12:38
mlankhorsttjaalton: http://paste.ubuntu.com/1620151/12:39
mlankhorstthere's probably a better fix, but meh..12:40
tjaaltonmlankhorst: ok, thanks13:03
mlankhorstyou need to add driver_descriptor@Base to the symbols list btw13:04
tjaaltonsigh13:34
tjaaltonconclusion; git merge does funky stuff13:35
tjaaltondespite merge -s ours13:35
tjaaltoni got exactly the same diff13:35
tjaaltonfor some reason it decides the remote is more important13:37
mlankhorstyou can override it. :P13:37
mlankhorstgit checkout whatevercommit . git commit --amend13:37
tjaaltonhmh?13:38
mlankhorstto amennd the merge commit13:38
tjaaltonwhat's whatevercommit13:39
mlankhorsterm what you want the HEAD to look like after merge13:40
tjaaltonsure I can touch whatever but it's work13:40
tjaaltonhttp://pastebin.com/kGwnuACC13:41
mlankhorstgit rm debian src; git checkout COMMIT src ?13:42
tjaaltondon't want to lose history for debian13:43
mlankhorsterm skip the rm debian then13:43
tjaaltonhmm13:43
tjaaltonhah13:46
tjaaltondid the trick13:46
tjaaltonamended with the merge13:46
tjaaltoncheckout $path sounds interesting..13:48
mlankhorst:-)13:50
tjaaltonwell, it does lose history, so it's not useful for pulling the packaging13:50
mlankhorstnot really? or at least git log debian/ kept working for me13:51
tjaaltononly if your branch had debian/ at some point13:51
mlankhorstyeah you need to start from debian branch13:52
tjaaltonbut if you checkout the upstream branch and then the packaging on top of it13:52
tjaaltonright13:52
tjaaltonworks for src/ etc13:52
tjaaltonnow where was I ..13:52
tjaaltonhave a dozen branches to weed through :P13:52
=== jono is now known as Guest81910
=== Quintasan_ is now known as Quintasan
tjaaltonattached a power meter between the outlet and ups, combined consumption is around max 200W including the monitor and DAC when building mesa with ivb :)15:01
tjaaltonidle is 90-10015:01
tjaaltonlibgles2 needed one symbol added, seems fine now15:03
tjaaltonmlankhorst: libxatracker1 is still big, but at least it didn't complain about the symbols15:11
mlankhorsttjaalton: yeah that was the goal :-)15:12
mlankhorstI didn't feel like making all those libraries shared just yet15:12
tjaaltonok now onto the ubuntu branch..15:31
mlankhorstwell radeon piglit results done, now i915 I suppose.15:42
mlankhorstwell afaict no regressions on radeon \o/15:49
tjaaltonugh, the gallium dricore patches make my head hurt.. I'll just push what I have so far16:05
mlankhorstwant me to rebase the gallium and dricore patches again? :P16:05
tjaaltonwell, yeah, all the files 117 touches have vanished :)16:06
tjaaltonfor starters16:06
mlankhorstwell I'm waiting on piglit to finish anyway16:06
mlankhorstwhy not16:06
tjaaltonmlankhorst: force-pushed16:14
mlankhorsttjaalton: nitpick, it's not from llvm. it's from libgallium and those other static libs where I added the flags to16:15
tjaaltonwell, do it properly and we can drop the patch :)16:16
tjaaltonwith a properly-named one16:16
tjaaltoner, replace it with..16:16
mlankhorstI'm probably just going to push it upstream..16:16
tjaaltonof course, even better16:17
mlankhorsttjaalton: 117 patch should no longer apply, but the fix is even easier to make :-)16:20
tjaaltongood16:21
mlankhorstbut I think it's better to just check with upstream first16:23
mlankhorstactually I guess I could just do an ugly hack for now16:25
mlankhorstseems we don't add version to libgallium in previous patches anyway16:26
mlankhorstdone with libgallium, now dricore gallium..16:28
mlankhorstoh right, that one was annoying16:32
mlankhorstit was a bit of abuse since I needed libmesagallium to be done after libdricore, so I had to move it to the mesa/libdricore directory16:34
mlankhorstwow, only d3d1x is still using makefiles16:39
mlankhorstok I'm still thinking about the best way to approach the dricore fix, but gallium was easy16:46
tjaaltonso it wasn't a great idea to push libxi to raring, need to revert the new stuff for now :P16:57
mlankhorstbroke unity?17:02
tjaaltonkde builds17:02
mlankhorstah, worse17:02
tjaaltonbut probably others too17:02
tjaaltonif includes both XInput2.h and Xfixes.h it'll go boom, duh17:03
mlankhorstwell lets see if it builds now17:04
mlankhorstoh right17:04
mlankhorstneed new llvm and new libdrm17:04
mlankhorsttjaalton: I pushed what I have17:05
mlankhorstit's guaranteed to break on building17:05
mlankhorstbut hopefully that only happens when it finds a new libmesagallium*.so17:06
mlankhorstif not, let me know17:06
tjaaltonyup, fails17:10
tjaaltonhttp://pastebin.com/xQM8QVb517:11
ricotztjaalton, hi :)17:24
ricotzmlankhorst, hey17:24
ricotztjaalton, did you notice some conflicts between libxi-dev and libxfixes-dev?17:25
ricotz/usr/include/X11/extensions/Xfixes.h:274:17: error: conflicting types for 'BarrierEventID'17:25
ricotz/usr/include/X11/extensions/XInput2.h:173:22: note: previous declaration of 'BarrierEventID' was here17:25
Sarvatt#ubuntu-devel :P17:25
ricotzah good17:25
mlankhorstricotz: hello17:26
tjaaltonricotz: yeah, fixed already17:26
tjaaltonI'll upload another one to the ppa, reverting the revert.. and then libxfixes dropping the old stuff17:27
ricotztjaalton, thanks!17:27
mlankhorsttjaalton: yeah looks like I'm including too much somehow17:27
mlankhorstI guess you need to exclude state_tracker/st_glsl_to_tgsi.cpp from the 118 patch17:27
mlankhorstin src/mesa/libdricore/Makefile.am17:27
ricotztjaalton, will be barrier stuff move away from xfixes?17:28
ricotzbe/the17:28
mlankhorstlooks funny there anyway, it was probably to work around some issue17:28
tjaaltonricotz: yes17:28
ricotztjaalton, ah i see17:28
tjaaltonslightly different anyway17:28
mlankhorsttjaalton: anyhow I have to leave for a bit, I think that specific issue should be easy to fix with that hint :-)17:28
tjaaltonmlankhorst: ok, I'll give it a got..17:29
tjaalton-t17:29
mlankhorstafk!17:29
tjaaltonfixesproto and lib pushed to c-x/x-s18:04
* mlankhorst back-ish18:09
tjaaltonhmm, could I upload xserver to the ppa then18:19
mlankhorstdid you get mesa running?18:19
tjaaltonah, no18:20
tjaaltonhttp://pastebin.com/xQM8QVb518:20
mlankhorstthat's  the same you posted earlier?18:20
tjaaltonoh right :)18:20
tjaaltonhttp://pastebin.com/p65CeikP18:22
mlankhorstoh so that's why I needed that file18:23
mlankhorsttjaalton: I pushed the fix, I hope..18:36
tjaaltonbuilding..18:36
tjaaltonmlankhorst: http://pastebin.com/axgf3Wst18:40
mlankhorststill the case? evil!18:41
tjaalton:)18:41
mlankhorstI guess it needs to be moved around18:41
mlankhorsttjaalton: what if you move that egl_gallium_la_LIBADD += $(MESAGALLIUM_LIBS) line in egl-static/Makefile.am all the way down to bottom of the file?18:43
mlankhorstI'm just guessing, I need to get my hands on a working llvm-3.2 build18:44
tjaaltonmlankhorst: grab it from the ppa :)18:52
tjaaltonmlankhorst: still the same19:01
mlankhorstoh :/19:01
mlankhorstI'll look tomorrow19:01
tjaaltonyeah19:01
Sarvatttjaalton: going to upload xserver?19:02
Sarvattor want me to do it? I can do the drivers too19:03
Sarvattoh, long queues :(19:03
Sarvattand sorry for not pushing it to expeirmental, didn't realize it was there also19:04
tjaaltonha, no worries, sorry for being tired/grumpy last night :)19:13
tjaaltonfeel free to upload them!19:13
DandelSarvatt: I spotted a major problem with piglit packages :/19:34
Dandelwhen running from installed packages, I found out that resume is broken.19:35
Sarvattdoh, did it just start happening one day or always been like that?19:36
Sarvattit's building daily git snapshots and i haven't looked at git in like 8 months19:36
Dandelit's not a one day issue19:37
Dandelit's a combination of bugs19:37
Dandel1 sec while i get the log from git to find out which commit is the likely culprit. 19:39
Dandelmost likely, it's this file ( in combination): http://cgit.freedesktop.org/piglit/log/framework/shader_test.py19:40
DandelSarvatt: also, on a similar note, piglit really needs to capture the core dumps ( and heap stacks )19:45
bryceDandel, agreed19:49
bryceDandel, well possibly we need a wrapper19:49
Dandelbryce: that's actually somewhat easy to "mimic"19:49
Dandelit already can identify when the test crashes19:49
Dandelit just needs a little bit of expansion ( based on what xbmc does for their launcher ) to be able to fully capture the stack.19:50
DandelSarvatt: I have a few fixes that should work... want to give em a try?20:43
Dandeljust double checked, and there's some patches on the piglit mailer that seem to address the issue about resuming tests.23:21

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!