log☇︎
24 entries in 1.075s
mircea_popescu: i think you have a point, re compiles.
scriba: Logged on 2019-04-27: [14:04:48] <asciilifeform> you turn on the mains, thing compiles the coupla MB of sores kept in nonvolatile. this -- runs. you go an' change a line, it recompiles that section, at same time as the cache refreshes.
asciilifeform: you turn on the mains, thing compiles the coupla MB of sores kept in nonvolatile. this -- runs. you go an' change a line, it recompiles that section, at same time as the cache refreshes.
phf: asciilifeform: i thought that you were arguing that the subset of ada runtime that's included in zfp "ought to be enough for everyone", since at the moment i believe it compiles ffa, my apologies.
mircea_popescu: dude. situation 1, as currently : you release code, mp like an idiot compiles it on ubuntu, jnow your code exists as a drepper mockery of itself. as far as the machine can tell, you asciilifeform are an idiot.
a111: Logged on 2018-07-15 15:38 mircea_popescu: asciilifeform check this out : i got a bundle which compiles to 64 bits except one lib, which compiles to 32 bit and then i get " wrong ELF class: ELFCLASS32 Program exited with code 0177". the configure for it manages to ignore both enable-lib64 --disable-lib32 and CFLAGS=-m64 CXXFLAGS=-m64 LDFLAGS=-m64 sets of flags. you ever heard of such ?!
mircea_popescu: asciilifeform check this out : i got a bundle which compiles to 64 bits except one lib, which compiles to 32 bit and then i get " wrong ELF class: ELFCLASS32 Program exited with code 0177". the configure for it manages to ignore both enable-lib64 --disable-lib32 and CFLAGS=-m64 CXXFLAGS=-m64 LDFLAGS=-m64 sets of flags. you ever heard of such ?! ☟︎
phf: mod6: think plaintext tar archive that you stick inside a vpatch. there's only ever ~one file~ in your tree. for simplicity it's one large trb.cpp that compiles to the result. no other dependencies.
asciilifeform: and if you merely long for the days of 8 hour compiles -- will luvv large fpga wurk.
mike_c: python compiles it when you run it and makes a .pyc
mircea_popescu: asciilifeform to be precise : i can't turn the greek string into an english string for you for the same reason you can't turn trb into lisp code for me. "but alf, it compiles! a lisp version must exist!" hurr. i don't propose "because you can't take object code and make me lisp source it follows no c sources existed" do i ?
mircea_popescu: you just said, lisp compiles to native bytecode.
phf: sbcl/cmucl already compiles whatever code you ask it to to native, architecture specific assembly, that's not the C layer's role
asciilifeform: and again, e.g., sbcl, compiles. question is what do you compile ~it~ with
punkman: mircea_popescu: http://log.bitcoin-assets.com/?date=30-01-2016#1389596 << so like a rotor reimplementation ? << more like some rotor automation to try various builds and lets you know what compiles or not ☝︎
mircea_popescu: you can actually use this to obtain code that compiles to different results can't you ?
artifexd: He said "write it in whatever you want as long as it compiles on linux"
assbot: Logged on 07-10-2014 06:20:35; mircea_popescu: the power of jesus compiles you!
assbot: 55 results for 'compiles you' : http://search.bitcoin-assets.com/?q=compiles+you
mircea_popescu: !s compiles you
decimation: I found that if you s/MSG_NOSIGNAL/SO_NOSIGPIPE/ the thing compiles (using macports g++-mp-4.7)
mircea_popescu: the power of jesus compiles you! ☟︎
fluffypony: you can create the port...since it compiles out the box it shouldn't need anything except fancy except pkg-descr, which I have already done
decimation: the interviewer is not the best... but the guest is interesting. Apparently LTspice compiles its own custom assembly code when you run a simulation.