IRC channel logs
2026-03-09.log
back to list of logs
<jlicht>is there a way to "clear" cached go files easily? I've now hacked up something with (and=> (compiled-file-name file) delete-file), but it feels a bit janky :-) <jlicht>where for my situation it shouldn't matter if the go file is put right next to my scm file, or into $HOME/.cache <old>sneek: later tell graywolf, primitive-load indeed does not load any compile file. It only expand and evaluate on the fly <old>jlicht: GUILE_AUTO_COMPILE=fresh ? <jlicht>old: should do the trick, thanks <rlb>lechner: not sure i understand exactly what your'e asking, but platform triples like that are often I think "autotools" derived. i.e. what autoconf uses, and what you'll get from running config.guess, e.g. for guile, build-aux/config.guess. <rlb>and if you grep config.guess, etc. you'll see mips64el <rlb>Though debian, specifically, does differ in some arch names, like amd64, which iirc is in part an artifact of the fact that, when debian started the port, amd was the one that had created the architecture, and the initial hardware --- intel adopted it later. <rlb>You can see "all the names" on a debian system via dpkg-architecture if dpkg-dev is installed. <ieure>rlb, Correct, Intel was failing to make their Itanium ground-up 64-bit ISA redesign fly when AMD swooped in with "x86, but we made it all 64-bit and backwards compatible" and won the whole thing. <mwette>I think it is mips64el, I've seen that term before <mwette>now that I think about it; the mips32 entry in arch-info is mipsel <mwette>lechner: thanks for the followup; once I saw mipsel (for 32bit) in arch-info.scm I assumed the mips64el one was ok; it's slated for 3.04.2 and in latest tag for guile-cdata <lechner>mwette / thanks for supporting your software so well!