Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2016-12-12

00:00:56[Saint]PLATFORM_HOSTED only gets viewers, right?
00:01:01[Saint]wrt: plugins
00:01:54[Saint]or is that only the case if you don't build against a resolution that happens to be shared by a supported target?
00:03:40[Saint]trying to follow the chain here and it isn't too obvious to me immediately.
00:03:53[Saint]__builtin: plugins are your jam, ^?
00:04:11__builtingive me a sec
00:05:18[Saint]I seem to recall that the case is basically that we just supply viewers and assume that the host will do a much better job with native functions.
00:08:21__builtinit seems that there's a separate SOURCES for app builds
00:09:53__builtinand if there's a keypad it just degenerates to including SOURCES, but if not, only a select subset are built
00:11:21__builtin... which seem to be mostly viewers but also a few games
00:13:15__builtinso there are a couple games built for hosted targets
00:14:08 Quit paulk-collins (Remote host closed the connection)
00:16:45[Saint]ones that have no hard requirement on fixed size bitmaps I presume.
00:17:07[Saint]I presume boomshine is one of them.
00:19:05__builtinchopper, clix, and boomshine
00:19:16__builtinand reversi
00:20:00[Saint]does clix have a different common/display name?
00:20:02[Saint]can't recall it offhand.
00:20:25[Saint]Not that I spend a hell of a lot of time in plugin-land. my own builds just disable plugins globally.
00:21:17__builtinjust clix
00:21:29__builtinthe one with a bunch of colored squares
00:22:32__builtinit's pretty similar to "Same Game" in sgt-puzzles
00:30:00***Saving seen data "./dancer.seen"
00:30:41 Quit alexweissman (Remote host closed the connection)
00:32:08[Saint]Is it reasonably new?
00:32:25 Join alexweissman [0] (
00:32:31[Saint]where "reasonably new" == +/- ~36 months or so
00:32:57__builtinprobably not
00:33:43__builtin2009 or so
00:35:48[Saint]Hmmm. I see. Selective memory I guess. I don't recall that name at all.
00:38:47 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.
00:44:19 Quit pamaury_ (Ping timeout: 256 seconds)
00:54:46 Join aaron [0] (a2ed858f@gateway/web/freenode/ip.
00:55:10 Nick aaron is now known as Guest54433 (a2ed858f@gateway/web/freenode/ip.
00:58:51 Quit Guest54433 (Client Quit)
01:06:53__builtinwould I be correct in stating that rockbox does not control the entire boot process on most devices?
01:20:00[Saint]You could probably go so far as to say on a good chunk of devices it doesn't control any of it. But I suppose that gets artificially inflated somewhat by the sansas and hosted platforms.
01:20:51 Quit girafe (Read error: Connection reset by peer)
01:22:18 Join girafe [0] (
01:29:56 Quit alexweissman (Remote host closed the connection)
01:51:35 Quit Senji (Ping timeout: 240 seconds)
02:08:46 Join alexweissman [0] (
02:23:58 Quit ZincAlloy (Quit: Leaving.)
02:25:07 Quit krnlyng (Ping timeout: 246 seconds)
02:30:01***Saving seen data "./dancer.seen"
02:35:36 Quit alexweissman (Remote host closed the connection)
02:38:31 Join krnlyng [0] (
02:42:44 Join Senji [0] (~Senji@
02:48:46 Join nlogex [0] (
02:50:03 Quit girafe (Quit: Leaving)
02:51:10 Quit Senji (Ping timeout: 270 seconds)
03:02:38 Quit Moarc (Ping timeout: 265 seconds)
03:02:41 Quit Slasheri (Ping timeout: 254 seconds)
03:02:59 Join Moarc [0] (
03:03:31 Join Slasheri [0] (
03:03:31 Quit Slasheri (Changing host)
03:03:31 Join Slasheri [0] (~miipekk@rockbox/developer/Slasheri)
03:06:57 Join Senji [0] (~Senji@
03:13:57 Quit Senji (Ping timeout: 250 seconds)
03:14:05 Join alexweissman [0] (
03:16:30 Join Senji [0] (~Senji@
03:16:45 Quit Senji (Read error: Connection reset by peer)
03:17:13 Join Senji [0] (~Senji@
03:23:54 Quit Senji (Ping timeout: 265 seconds)
03:30:02 Join Senji [0] (~Senji@
03:30:17 Quit Senji (Read error: Connection reset by peer)
03:30:47 Join Senji [0] (~Senji@
03:50:37 Quit robertd1 (Ping timeout: 258 seconds)
04:06:02 Join webguest54 [0] (
04:10:57 Quit webguest54 (Quit: CGI:IRC (Ping timeout))
04:30:04***Saving seen data "./dancer.seen"
05:39:27 Quit einhirn (Ping timeout: 252 seconds)
05:47:29 Quit nlogex (Ping timeout: 256 seconds)
05:48:25 Join JanC_ [0] (~janc@lugwv/member/JanC)
05:49:37 Quit JanC (Ping timeout: 245 seconds)
05:49:40 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
06:11:04 Join einhirn [0] (
06:12:47 Join einhirn_ [0] (
06:16:07 Quit einhirn (Ping timeout: 250 seconds)
06:17:07 Quit TheSeven (Ping timeout: 245 seconds)
06:17:57 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
06:28:15 Join chrisb [0] (
06:30:08***Saving seen data "./dancer.seen"
06:42:37 Nick [Saint] is now known as [Sinner] (~sinner@rockbox/staff/saint)
08:23:52 Quit einhirn_ (Quit: Miranda IM! Smaller, Faster, Easier.
08:30:11***Saving seen data "./dancer.seen"
08:35:12 Nick [Sinner] is now known as [Saint] (~sinner@rockbox/staff/saint)
08:36:48 Join ender` [0] (
08:50:16 Join einhirn [0] (
08:51:02 Join edhelas [0] (~edhelas@
08:57:25 Join petur [0] (~petur@rockbox/developer/petur)
08:57:37 Join The_Prospector|2 [0] (
09:00:25 Quit petur (Client Quit)
09:00:43 Quit The_Prospector (Ping timeout: 258 seconds)
09:00:47 Join petur [0] (~petur@
09:00:47 Quit petur (Changing host)
09:00:47 Join petur [0] (~petur@rockbox/developer/petur)
09:01:08 Quit edhelas (Ping timeout: 248 seconds)
09:20:24 Join wodz [0] (
09:20:30 Quit wodz (Client Quit)
09:20:51 Join wodz [0] (
09:40:12 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
09:52:08 Join advcomp2019 [0] (
09:52:08 Quit advcomp2019 (Changing host)
09:52:08 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019)
09:54:55 Quit advcomp2019_ (Ping timeout: 265 seconds)
10:04:32 Quit The_Prospector|2 (Ping timeout: 252 seconds)
10:12:42 Quit pamaury (Ping timeout: 268 seconds)
10:16:16 Join MrZeus [0] (~MrZeus@
10:30:12***Saving seen data "./dancer.seen"
10:31:19 Join bzed [0] (
11:21:01 Join elensil [0] (~edhelas@2001:1c02:1903:d800:a5ef:9915:d112:99e8)
11:25:30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
11:30:52 Quit prg318 (Ping timeout: 245 seconds)
11:32:52 Join prg318 [0] (~prg318@deadcodersociety/prg318)
11:35:18fs-bluebotBuild Server message: New build round started. Revision 8e82839, 255 builds, 13 clients.
11:36:29 Quit MrZeus (Read error: Connection reset by peer)
11:37:15 Join MrZeus [0] (~MrZeus@
11:44:14fs-bluebotBuild Server message: Build round completed after 535 seconds.
11:44:15fs-bluebotBuild Server message: Revision 8e82839 result: All green
11:53:43fs-bluebotBuild Server message: New build round started. Revision 5c50efc, 255 builds, 13 clients.
12:03:09fs-bluebotBuild Server message: Build round completed after 567 seconds.
12:03:11fs-bluebotBuild Server message: Revision 5c50efc result: All green
12:03:12fs-bluebotBuild Server message: New build round started. Revision a983859, 255 builds, 13 clients.
12:05:34 Join The_Prospector [0] (~The_Prosp@unaffiliated/cornman)
12:13:29fs-bluebotBuild Server message: Build round completed after 618 seconds.
12:13:30fs-bluebotBuild Server message: Revision a983859 result: All green
12:13:31fs-bluebotBuild Server message: New build round started. Revision 1c97083, 255 builds, 12 clients.
12:22:27fs-bluebotBuild Server message: Build round completed after 536 seconds.
12:22:28fs-bluebotBuild Server message: Revision 1c97083 result: All green
12:22:29fs-bluebotBuild Server message: New build round started. Revision af81cc4, 255 builds, 12 clients.
12:30:15***Saving seen data "./dancer.seen"
12:35:39fs-bluebotBuild Server message: Build round completed after 792 seconds.
12:35:40fs-bluebotBuild Server message: Revision af81cc4 result: All green
12:45:34 Join rela_ [0] (
12:45:46 Quit rela (Read error: Connection reset by peer)
12:58:12 Join pamaury_ [0] (
13:05:29 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:24f5:a979:5299:889e)
13:10:42fs-bluebotBuild Server message: New build round started. Revision 9ca8bd6, 255 builds, 13 clients.
13:11:24 Join rlnd [0] (
13:20:42fs-bluebotBuild Server message: Build round completed after 601 seconds.
13:20:43fs-bluebotBuild Server message: Revision 9ca8bd6 result: All green
13:20:44fs-bluebotBuild Server message: New build round started. Revision 17277fa, 255 builds, 13 clients.
13:31:37fs-bluebotBuild Server message: Build round completed after 653 seconds.
13:31:37fs-bluebotBuild Server message: Revision 17277fa result: All green
13:31:39fs-bluebotBuild Server message: New build round started. Revision ac0fc74, 255 builds, 13 clients.
13:37:07 Quit Senji (Ping timeout: 245 seconds)
13:42:28fs-bluebotBuild Server message: Build round completed after 650 seconds.
13:42:29fs-bluebotBuild Server message: Revision ac0fc74 result: All green
13:50:05 Join skapazzo [0] (~skapazzo@
14:05:36 Quit alucryd (Remote host closed the connection)
14:06:55 Join alucryd [0] (~quassel@archlinux/developer/alucryd)
14:12:37 Join robertd1 [0] (~root@
14:30:17***Saving seen data "./dancer.seen"
14:38:48 Join girafe [0] (
15:02:31 Join paulk-blaze [0] (
15:10:02 Quit marex-cloud ()
15:10:24 Join marex-cloud [0] (sid137234@gateway/web/
15:18:08 Quit Moarc (Ping timeout: 260 seconds)
15:18:08 Quit froggyman (Ping timeout: 260 seconds)
15:18:27 Join Moarc [0] (
15:18:36 Quit krnlyng (Ping timeout: 260 seconds)
15:19:40 Quit Tristitia (Ping timeout: 246 seconds)
15:20:07 Quit wodz (Quit: Ex-Chat)
15:23:19 Join krnlyng [0] (
15:25:37 Join froggyman [0] (~frogs@unaffiliated/froggyman)
15:38:37 Join Tristitia [0] (
15:39:46 Quit paulk-blaze (Quit: Leaving)
15:59:53 Join amayer [0] (
16:06:25 Join fujisan_ [0] (~fujisan@unaffiliated/fujisan)
16:13:34 Join paulk-collins [0] (
16:26:13 Part robertd1
16:30:18***Saving seen data "./dancer.seen"
16:46:24 Join dfkt [0] (~dfkt@unaffiliated/dfkt)
16:46:52 Quit dfkt (Client Quit)
16:47:52 Join dfkt [0] (~dfkt@unaffiliated/dfkt)
17:06:01 Quit utrack (Ping timeout: 258 seconds)
17:06:08 Join nlogex [0] (
17:06:36 Join utrack [0] (
17:17:36 Join PurlingNayuki [0] (~Thunderbi@
17:26:12 Quit petur (Quit: Connection reset by beer)
17:30:39 Quit PurlingNayuki (Ping timeout: 250 seconds)
17:39:28 Quit Rower (Quit: Hmmm...)
17:43:28 Join Rower [0] (
17:46:06 Quit pamaury_ (Remote host closed the connection)
17:49:23 Join scorche|sh [0] (
17:49:23 Quit scorche|sh (Changing host)
17:49:23 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche)
17:50:43 Quit pamaury (Ping timeout: 248 seconds)
18:05:51 Quit elensil (Quit: Leaving.)
18:07:05 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier.
18:25:00 Quit nlogex (Ping timeout: 258 seconds)
18:25:25 Join nlogex [0] (
18:30:21***Saving seen data "./dancer.seen"
18:35:24 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
18:55:41 Quit rela_ (Quit: Leaving)
19:25:50 Join Link8 [0] (~me@
19:32:56 Join rela [0] (~x@pdpc/supporter/active/rela)
19:44:32[Saint]Why are we getting build round notifications, but no commit notifications?
19:44:47 Quit Galois (Ping timeout: 260 seconds)
19:45:18pamaury[Saint]: no idea, I never quite understood the bluebot magic
19:46:44[Saint]I am writing another bot presently. Well, rather, I am pulling apart a much, much, much more complex bot and stripping it down to the bare essentials we would need.
19:47:16[Saint]I would really love to get a look at bluebot though.
19:47:59 Join Galois [0] (
19:48:46[Saint]One cute thing I noticed is that fs-bluebot doesn't seem to have any magic to determine /where/ it should look for Gerrit tags
19:49:26 Nick [Saint] is now known as g123 (~sinner@rockbox/staff/saint)
19:49:34g123like so
19:49:55g123Hmmm. Interesting.
19:50:21g123g123: testes
19:50:21 Nick g123 is now known as [Saint] (~sinner@rockbox/staff/saint)
19:50:23fs-bluebotGerrit review #123 at : Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini
19:50:34[Saint]There we go.
19:51:08pamauryinteresting... yeah a new bot with the code would be nice
19:51:15[Saint]I noticed that a couple of days ago when someone's nick set it off.
19:51:20bluebrother[Saint]: that "magic" is simply a regexp :)
19:51:38bluebrotherbut it's not the nick, it's the nick being mentioned
19:51:49bluebrotherr'([rR]eview\s+|[Gg](errit)?) *#?([0-9]+)([^0-9a-zA-Z]|$)'
19:52:29[Saint]right, I should've been more clear. anyway, you've inspired me to ignore "g***:"
19:52:39pamauryI thought the syntax was g#number
19:52:51[Saint]AFAIK, it should be.
19:53:02bluebrotherwell, in the beginning we had g#<number>, but then we also had g<number>, and gerrit<number>
19:53:15pamauryoh, I was never aware of that
19:53:17bluebrotherbut we could simply always require the #
19:53:33pamauryI think most people use the #
19:53:36bluebrotherI've seen g123 being used quite some times.
19:53:37fs-bluebotGerrit review #123 at : Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini
19:53:54bluebrotherbut I don't see a problem in restricting that. Those false alerts are a bit annoying ...
19:53:56[Saint]IIRC, somethingsomethingfoog123 triggers it too.
19:53:57fs-bluebotGerrit review #123 at : Add an alternative analogic touchpad sensitivity setting by Jean-Louis Biasini
19:54:12bluebrothersure, because it's g<number> ;-)
19:54:27bluebrotherand requiring a space before it breaks (g#<number>)
19:54:30[Saint]no, it's "*g<number>" ;)
19:54:39[Saint]they're distinct.
19:54:40bluebrotheror that :D
19:55:17fIorz\<g[0-9]+ ?
19:55:26bluebrotherand then we had g#<number> as well as g #<number> so ...
19:55:34[Saint]any idea why the commit notifications died?
19:55:56bluebrotherno, they should work.
19:56:12bluebrotherah, commit notification. We only had build notifications from the bot
19:56:13[Saint]they ded. RIP.
19:56:30fIorz(or whatever the regex engine expects for a (left) word boundary)
19:56:45[Saint]Ah, what handles the commit nook notifications? I thought it was bluebot that did that?
19:56:53bluebrotherhmm, last build was ac0fc74 and that was announced in the channel
19:57:08[Saint]Oh, I misunderstood.
19:57:26bluebrotherno. I have a build client running on the same box as bluebot, and that build client pushes the notifications to bluebot
19:57:48[Saint]I wondered how you were doing that.
19:57:50bluebrothersome weird socket interface thingy. I don't like it too much but it works ;-)
19:58:10bluebrotherso when the build client dies the channel notifications stop
19:58:18[Saint]right. makes sense.
19:59:37bluebrotherI should review that code ...
19:59:51[Saint]If a client ends up being so shit that it can't compete in the build system, and never gets passed builds...does it still get notified of the builds?
20:00:08[Saint]As far as I'm concerned the only really interesting metric is that builds have started.
20:00:15bluebrotherand then there's still that ssl thing about Rockbox Utility open :(
20:00:28bluebrotheryes, I'm forwarding the messages the build client gets from the build server.
20:00:30[Saint]I figure I could abuse the rating system for build clients to artificially kill my clients reputation.
20:00:45bluebrotherand if the build server finds a client to be too slow it simply stops its build and uses another client
20:00:58[Saint]so I never actually get builds, but still get notitfied.
20:01:05bluebrotherbut that's a build server thingy
20:01:05[Saint]cheating, but...should work for what I need.
20:01:39[Saint]well, it is and it isn't. iirc, the reputation is stored client side?
20:01:41 Join lebellium [0] (
20:01:59bluebrotherthat's kinda what I'm doing here. Though my client does get builds.
20:02:01[Saint]I'd need to look again but I recall this just being stored in a plain text file client side.
20:02:11bluebrotherit's one of the clients that provide the latex toolchain :)
20:02:14[Saint]I figure I'll just artifically shit the bed.
20:03:26[Saint]it makes some sense for reputations to be stored client side so if a person running a build client fixes their shit up they aren't still ignored by the build system I guess. I may be talking out my ass though.
20:03:40bluebrotherproviding no useable toolchain might work as well :)
20:04:07[Saint]I think if it reports no usable build chain it /does/ get ignored.
20:04:12[Saint]but I might be wrong on that.
20:04:27[Saint]If it does it for too long.
20:05:07gevaertsWhat's this "reputation" you mention?
20:05:49bluebrotherhmm, dev.cgi still shows only 0's when hovering over the state of a build
20:06:10*gevaerts doesn't really understand what [Saint] is proposing
20:06:57[Saint]gevaerts: aren't there client side metrics stored on builds completed and times taken to do so which is used to favor who gets handed what in the next rounds?
20:07:10gevaertsWell, to decide
20:07:12bluebrotherI think he wants to mess with the score of his client to avoid geting builds
20:07:17gevaertsI wouldn't call it "favor"
20:07:38gevaertsBut if you want a notify-only client, why would you give it the same id as a build client?
20:08:39[Saint]I wouldn't. I'd set an entirely new instance up and then just artificially puke on the score/reputation.
20:09:26[Saint]Is there some other way of doing this you're withholding that I'm obviously not aware of with the existing build system?
20:09:47gevaertsDoing what? I still don't get what you're trying to achieve
20:09:57[Saint]I want to know when a build round has been handed out.
20:10:27bluebrotherwhat happens if you try to start a build client that hasn't any useable toolchains?
20:11:02[Saint]guess I'll find out after coffee starts to kick in.
20:11:37[Saint]Well, do share.
20:11:48bluebrotherjust tried it. Set −−archlist=,
20:11:53gevaertsInstall an obsolete toolchain, and then perl -s -username=something -password=something -clientname=something -archlist='arm' -port=19999
20:12:03gevaertsOh, , works? Great!
20:12:23gevaertsBetter than reusing those old compilers I forgot to uninstall :)
20:12:24bluebrotherwell, the client did connect. No idea if it will get any info from the server though
20:12:35[Saint]But won't I need to tell someone what I'm doing so no one culls it from the build system?
20:12:38gevaertsI don't see wht it shouldn't
20:12:51bluebrotherme neither.
20:12:56gevaerts[Saint]: you do get general information about the build round
20:13:14[Saint]semi-regularly non-contributing clients get disabled, I thought?
20:13:16bluebrotherleaving archlist empty didn't work (it tells me I need to provide all arguments). But since it uses toolchain1,toolchain2 ...
20:13:23[Saint]I guess I'd need to say "hey, leave me alone" or so.
20:13:52bluebrotherwhy not just do some cheap builds?
20:14:22bluebrotherI have my client running mostly to have a client that provides latex, but I also announce sdl. Doesn't hurt, even if the machine is slow
20:14:26gevaertsBroken clients get disabled
20:14:32gevaertsUsually by me, when I notice
20:15:25[Saint]does 'never actually contributes a build, or even tries, ever' not count as broken? If not, sweet.
20:15:28[Saint]But I guess bluebrother is right, I just like to segregate things.
20:16:01bluebrotherjust announce sdl, it will build some checkwps things or so. No biggie
20:16:03gevaertsBroken clients get disabled manually
20:16:09gevaertsThere's no automated system
20:18:06[Saint]it's mildly annoying that I should even need to want to monkey the system like this, but I understand wholeheartedly why it never occurred to anyone to add a hook solely for notification to the build system.
20:19:24gevaertsAll you do is connect and tell the server you have no toolchains
20:19:29gevaertsThat's not *that* terrible
20:20:58bluebrotherI think there was discussion about this (*quite* some time back), and it kinda ended that it would be as simple as running a client that has no usable toolchains
20:21:12 Quit fujisan_ (Quit: Textual IRC Client:
20:21:43lebelliumpamaury: do you have some things to try out on E580 or A850?
20:21:57[Saint]If you're wondering, bluebrother, I'm not muscling in on your territory - so to speak. Or creating redundancy.
20:22:06[Saint]This bot will only speak when spoken to.
20:22:13[Saint]And even then only in privmsg.
20:22:58bluebrother[Saint]: I have no problem with you running another bot
20:23:19[Saint]I'm sure people would if we were both yelling about build metrics in channel. :)
20:23:36bluebrotherbluebot came to life simply because some people thought it would be useful and I was kinda interested in a programming excercise back then :)
20:23:49bluebrother[Saint]: I'm not people :D
20:24:08[Saint]yeah, it is useful. just making it clear that there's two distinct goals.
20:24:30bluebrotheroh, it's already 5 years ... though I've rewritten it 2 years ago
20:24:44[Saint]primary goal of this is spooky analytics.
20:25:53[Saint]logbot's pervy stalker cousin.
20:26:01*bluebrother hides
20:30:25***Saving seen data "./dancer.seen"
20:33:52pamaurylebellium: yeah, but first you need to build the toolchain
20:34:05pamauryget g#1424
20:34:08fs-bluebotGerrit review #1424 at : Initial commit for the Sony NWZ linux port and NWZ-E460 (WIP) by Amaury Pouly
20:41:14 Join TheLemonMan [0] (~root@unaffiliated/thelemonman)
20:41:59lebelliumpamaury: got
20:44:11pamaurylebellium: ok, now make sure you have installed on your system at least libmpfr-dev and libmpc-dev
20:44:35pamauryand libgmp-dev
20:44:54pamauryonce done, to go to tools, run and select the arm-app
20:47:06lebelliumsudo apt-get libmpfr-dev?
20:48:25pamaurysomething like that
20:48:41lebelliumE: Invalid operation libmpfr-dev
20:48:47lebelliumbut not exactly as it should :D
20:49:19pamauryapt-get install
20:56:16lebelliumRBDEV_PREFIX=~/arm-sony-linux-gnueabi ./ is OK?
20:58:33pamaurylebellium: actually the toolchain is now call arm-rockbox-linux-gnueabi
20:58:47pamauryotherwise yes it is ok
20:58:56lebelliumI already run it
20:58:57pamauryI mean it's a small detail
20:59:01pamaurythat's fine
21:07:45lebelliumhum I don't know if it finally complete or if I mistakenly cancelled it
21:07:55lebelliumROCKBOXDEV: gcc-4.9.4/make
21:14:58 Quit chrisb (Ping timeout: 265 seconds)
21:17:37pamaurylebellium: you cancelled (^C) is Control-C
21:18:03pamauryyou can restart from the last step with a special command
21:18:20pamaurycan you pastebin the output of the tool ?
21:20:15pamauryRESTART=gcc-stage1 RBDEV_PREFIX=~/arm-sony-linux-gnueabi ./
21:20:34pamauryselect arm-app against and it should restart at the same step
21:21:30lebelliummkdir: cannot create directory `build-gcc-4.9.4': File exists
21:22:34pamauryah you need to rm -rf the build dir
21:22:48pamaurysomething like:
21:22:48pamauryrm -rf /tmp/rbdev-build/build-gcc-4.9.4
21:23:25 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627)
21:23:33 Quit cc___ (Client Quit)
21:24:20 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627)
21:33:48 Join edhelas [0] (~edhelas@
21:36:43lebelliumpamaury: gcc-4.9.4/make lasts forever!
21:37:54pamaurylebellium: you are compiling a compiler! (twice)
21:38:14pamaurythe whole things takes about 45min on my i5 machine
21:38:37lebelliumI also have a tired i5-540m but in Virtualbox...
21:58:07pamaurybluebrother: what is the "policy" to pull libraries in rbutil ? I'm starting to write a mknwzboot for Sony players and I need some crypto that we don't already have (DES). Currently I'm use libcrypto++, will that be a problem when we add it to rbutil?
22:03:00 Quit michaelni (Ping timeout: 264 seconds)
22:07:02 Join petur [0] (~petur@rockbox/developer/petur)
22:11:45 Quit pookie_ (Quit: All for nothing)
22:15:23 Join michaelni [0] (
22:15:38edhelashi pamaury :)
22:18:21 Quit ZincAlloy (Quit: Leaving.)
22:20:03 Quit nlogex (Ping timeout: 248 seconds)
22:30:27***Saving seen data "./dancer.seen"
22:39:36lebelliumpamaury: I guess I need your i5. Mine is boring^^
22:48:47lebelliumpamaury: pff I aborted it again, just at the ened
22:49:09lebelliumROCKBOXDEV: Done!
22:49:10lebelliumROCKBOXDEV: Make sure your PATH includes /home/ubuntu/arm-sony-linux-gnueabi/bin
22:49:12lebelliumubuntu@ubuntu-VirtualBox:~/rockbox/tools$ ^C
22:49:25 Quit paulk-collins (Remote host closed the connection)
22:49:42lebelliumI just wanted to copy and paste
22:50:15 Quit bluebrother (Ping timeout: 240 seconds)
22:51:00 Quit fs-bluebot (Ping timeout: 258 seconds)
22:52:05 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
22:54:57 Join nlogex [0] (
22:56:56pamaurylebellium: I think it was done, since it said Done!
22:57:12lebelliumI don't know if I can trust it :D
22:57:31lebelliumcan I check easilyN
22:59:37pamaury/home/ubuntu/arm-sony-linux-gnueabi/bin/arm-rockbox-linux-gnueabi-gcc -v
22:59:41pamauryand pastebin the result
23:00:00lebelliumubuntu@ubuntu-VirtualBox:~/rockbox$ /home/ubuntu/arm-sony-linux-gnueabi/bin/arm-rockbox-linux-gnueabi-gcc
23:00:02lebelliumarm-rockbox-linux-gnueabi-gcc: fatal error: no input files
23:00:03lebelliumcompilation terminated.
23:00:52lebelliumhere you are
23:01:38 Quit nlogex (Read error: Connection reset by peer)
23:02:18 Join nlogex [0] (
23:02:45pamauryit looks all right
23:03:43pamauryOk, I am still creating the configure entries for the E580 and A850, wait for 5min
23:03:44lebelliumI didn't expect it to last the whole night but at least we can now on serious things from tomorrow :D
23:04:01pamauryBut yeah maybe better wait until tomorrow ;)
23:04:20lebelliumyeah, it's already quite late. You're available tomorrow night?
23:04:34pamauryyes, around the same time
23:05:05lebelliumok, thanks for your help and see you
23:05:29 Join fs-bluebot [0] (
23:05:32lebelliumI'll read the logs if needed
23:07:12 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 50.0.2/20161129173726])
23:13:44[Saint]sudo mount -o remount,rw /dev/mmcblk0p1 ; touch /boot/ssh
23:13:50[Saint]sudo mount -o remount,ro /dev/mmcblk0p1
23:14:02[Saint]ah, shit.
23:17:20pamaurysudo mount -o loop [Saint] [Saint]
23:19:08[Saint]ps ax | grep pamaury
23:19:08[Saint]sudo kill ~pamaury@rockbox/developer/pamaury
23:20:56 Quit Link8 (Ping timeout: 250 seconds)
23:21:23*pamaury is shocked but not killed
23:22:17[Saint]sudo pkill -f pamaury
23:22:25pamauryah damn
23:23:03*pamaury has a patched kernel to intercept the KILL signal
23:26:38__builtinkill -SIGHUP `pidof pamaury`
23:26:58pamauryah that's clever
23:31:22 Quit ender` (Quit: How many SEO experts does it take to change a light bulb, lightbulb, light, bulb, lamp, lighting, switch, sex, xxx, hardcore)
23:32:45 Join JanC_ [0] (~janc@lugwv/member/JanC)
23:34:00 Quit JanC (Killed ( (Nickname regained by services)))
23:34:00 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)
23:45:32 Quit [Saint] (Quit: Going down for routine maintenance - estimates downtime 5 minutes (+/- 2 minutes))
23:48:14 Quit skapazzo (Quit: Lost terminal)
23:54:24 Join [Saint] [0] (~sinner@rockbox/staff/saint)

Previous day | Next day