00:37:29 -!- amalloy_ is now known as amalloy
01:21:26 <Lantell> Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-3570-gb561bb485a
02:14:04 <Cbrotell> Unstable branch on cbro.berotato.org updated to: 0.26-a0-661-g406de6ba63 (34)
03:30:56 <Kelbell> Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-3570-gb561bb485a
05:00:36 -!- amalloy is now known as amalloy_
06:15:52 <ZureaL> %cache
06:15:52 <Cbrotell> CCACHE status: Hit Rate =50.00 % | Files Cached=2 | Cache Size=8.2 kB | Max Cache Size=5.0 GB
06:15:57 <ZureaL> meh
06:17:51 <Pinkbeast> ZureaL: What's "ccache -s" as crawl-dev say?
06:47:00 <ZureaL> pretty much what %cache reports.  I'm just pulling from that command to fill the bot's reply.  There's only 2 files in cache
06:48:13 <Pinkbeast> cache hit rate                     64.91 %
06:50:28 <Pinkbeast> Hm. ~crawl-dev/dgamelaunch-config/crawl-build/update*sh here
06:50:38 <Pinkbeast> invokes make with an explicit "FORCE_CXX=g++" (and ~crawl-dev/bin is in the PATH (and at the front), and there's a symlink to ccache there)
06:50:46 <Pinkbeast> I guess some of that isn't true for you
06:50:52 <Pinkbeast> Sorry if that's all Capt Obvious
06:52:11 <ZureaL> well, we'd gone through and made sure that /usr/lib/ccache was first and that the symlinks for all the compiler tools exists there
06:52:43 <ZureaL> cause If I do 'which gcc' as crawl-dev, it points to the ccache one
06:53:16 <Pinkbeast> What about "which g++"; also there might be an actively bogus FORCE_CXX in those files
06:53:33 <ZureaL> same on which g++
06:53:39 <ZureaL> I'll look for the foce
06:53:40 <ZureaL> forc
06:53:50 <ZureaL> fuck it, I can't type, too early :)
06:53:55 <Pinkbeast> (and if there isn't one, I'd add one, although that's getting a bit cargo-culty)
06:56:38 <ZureaL> so the only FORCE_CXX exists in the makefile, down in the source dir
06:58:24 <Pinkbeast> Aha!
06:59:11 <Pinkbeast> And the Makefile does gcc -dumpmachine to set LMACH and then invokes (eg) "arm-linux-gnueabihf-g++"
06:59:34 <ZureaL> but the 'export PATH=' statement is in the update-trunk shell script at least
07:00:00 <Pinkbeast> So you definitely want to set FORCE_CXX in those update*sh scripts, or make whatever your equivalent of arm-linux-gneuabihf-g++ is also a symlink in ~/bin
07:00:29 <ZureaL> I don't need it in ~/bin, I'm calling the ones in /usr/lib/ccache
07:00:52 <ZureaL> ls -l /usr/lib/ccache
07:00:55 <ZureaL> oops
07:00:59 <ZureaL> wrong window
07:01:39 <Pinkbeast> Uh - but there isn't, and won't be, a file in /usr/lib/ccache with that name
07:01:39 <Pinkbeast> So either you'd have to do it via a symlink in ~/bin, or edit those shell scripts.
07:01:41 <Pinkbeast> I could make our copies of them available for reference if you like
07:01:45 <ZureaL> gcc, g++, etc...all those exist as symlinks in /usr/lib/ccache
07:01:54 <Pinkbeast> ZureaL: Yes, but see above re LMACH
07:02:37 <ZureaL> x86_64-linux-gnu-gcc -- also exists in /usr/lib/ccache
07:02:45 <ZureaL> and the g++ variant
07:02:55 <Pinkbeast> And with g++-6?
07:03:06 <ZureaL> it's -9, but yet
07:03:09 <ZureaL> er...but yes
07:03:22 <Pinkbeast> OK, this is a bit mysterious, but why not humour me and edit the scripts anyway?
07:04:55 <ZureaL> I'm not opposed to it, I'm just trying to make sure the issue is understood :)  So you're saying I should "export FORCE_CXX=x86_64-linux-gnu-gcc-9"? in the script?
07:05:39 <Pinkbeast> Not quite. As mentioned, I could easily make our version available (& I forget if it makes a difference if you invoke it as gcc these days, but I'd use g++)
07:05:56 <ZureaL> okay g++-9 :)
07:06:17 <Pinkbeast> In the make invocation midway down the script, add "FORCE_CXX=/usr/lib/ccache/g++" to the giant list of arguments
07:07:15 <ZureaL> ok
07:07:18 <Pinkbeast> (I'm trying to make your setup exactly like CMOU just to be sure we're not missing something)
07:08:25 <ZureaL> FORCE_CXX=/usr/lib/ccache/g++  lives in the trunk script in the 'say-do crawl-do nice make' section
07:09:13 <Pinkbeast> Quite so
07:09:36 <ZureaL> we'll see what happens next update :)
07:09:39 <Pinkbeast> (And stable, but you probably care a lot less about ccache for stable builds)
07:09:49 <Pinkbeast> Best of luck
07:09:56 <ZureaL> yea, I did it in stable too
07:10:14 <ZureaL> thanks!
07:10:34 <Pinkbeast> Don't thank me unless it works :-)
10:12:25 <Cheibriados> 03advil02 07[targeted-commands] * 0.26-a0-687-g6fa7f52: Tweak autofight_throw behavior and clarify comments 10(4 minutes ago, 1 file, 23+ 4-) 13https://github.com/crawl/crawl/commit/6fa7f52329bf
10:12:35 <Cheibriados> Branch pull/1581 updated to be equal with targeted-commands: 13https://github.com/crawl/crawl/pull/1581
12:39:42 <Kelbell> xyva (L8 DsNe) Crash caused by signal #6: Aborted (D:7)
13:06:28 <Henzell> Unstable branch on crawl.akrasiac.org updated to: 0.26-a0-661-g406de6b (34)
18:23:50 <Lantell> Unstable branch on underhound.eu updated to: 0.26-a0-661-g406de6ba63 (34)
19:03:00 -!- jfcaron_ is now known as jfcaron
20:14:35 <advil> well, the odd redraw-related lag I was seeing the other day was indeed fixed by restarting terminal (and actually before that even by using a fresh window)
20:14:58 <advil> which is good, because it would have been seriously painful to debug if it were on the crawl end
20:40:17 <advil> hm, if you gain a level during world_reacts, need to select an attribute to increase, and disconnect on that prompt, what happens?
22:27:27 <Cheibriados> 03PleasingFungus02 07* 0.26-a0-662-g8b9c6da: Make demons truly spineless 10(26 hours ago, 2 files, 4+ 4-) 13https://github.com/crawl/crawl/commit/8b9c6dab8160
22:32:37 <Kelbell> Unstable branch on crawl.kelbi.org updated to: 0.26-a0-662-g8b9c6dab81 (34)
22:53:43 -!- amalloy_ is now known as amalloy
23:42:27 <twelwe> is it intended design that good gods dislike condenser vane?
23:51:11 <Discord|> <12e​bering> yea
23:51:15 <Discord|> <12e​bering> negative energy clouds