00:00:00 --- log: started forth/18.02.02 00:02:38 --- join: proteus-guy (~proteusgu@183.89.88.74) joined #forth 00:03:47 yunfan: how would you structure a forth executable then? 00:04:56 jn: self-load? not every excutable need ld-linux ,isnt it? 00:05:49 --- quit: proteusguy (Ping timeout: 240 seconds) 00:07:00 what i'm asking is: you say "[...] isnt that much easier to create executable ?". how would you "create executable"? 00:07:51 you forth implementation that acts like ld-linux.so may not require an ld-linux.so, that's clear 00:08:01 --- join: Labu (~mik@mvice.pck.nerim.net) joined #forth 00:10:56 if your goal is to put forth source code in a file, and have the forth interpreter be loaded automatically when you try to execute that forth source file, i suggest using #! instead. this way you don't have to deal with any of the details of ELF 00:13:50 jn: no my goal is to put all these interpreter, images tother as a executable file 00:14:18 and it could even append souce to itself, since its arch is just a forth interpreter read from itself with some offset 00:14:43 what you say #! is not a good idea for portable goals 00:15:19 --- quit: dys (Ping timeout: 248 seconds) 00:16:39 messing with ELF's INTERP field (the thing that specifies which ld.so to load) is probably a worse idea for portability, but maybe i misunderstood you and that wasn't your idea when you said "if a forth could acts like ld-linux, [...]" 00:18:40 maybe, english is not my first lang, so i might has some wrong usage 00:19:26 if you mean by "if a forth could acts like ld-linux," that it's statically linked, then it sounds quite reasonable 00:19:48 but i think now you could know what i need, its just a single exetuable file, insist of a forth interpreter inside, and images , then it could dynamic modify itself to save the image change 00:20:23 yunfan: no problem. but there are different ways in which ld-linux acts, and i think i just misunderstood you there 00:21:27 ok, now i understand what you're saying, and it sounds ok 00:28:50 --- quit: Labu (Ping timeout: 252 seconds) 00:29:45 --- join: Labu (~mik@78-115-242-194.normaction.nerim.net) joined #forth 00:55:06 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 01:22:01 --- join: ncv__ (~neceve@90.192.23.42) joined #forth 01:22:02 --- quit: ncv__ (Changing host) 01:22:02 --- join: ncv__ (~neceve@unaffiliated/neceve) joined #forth 01:43:40 --- quit: nighty- (Quit: Disappears in a puff of smoke) 02:03:02 --- join: gravicappa (~gravicapp@ppp83-237-171-229.pppoe.mtu-net.ru) joined #forth 02:27:34 --- quit: Labu (Ping timeout: 248 seconds) 02:32:01 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 02:44:18 --- join: Labu (~mik@mvice.pck.nerim.net) joined #forth 03:57:50 --- quit: Labu (Quit: Leaving.) 05:47:29 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:49:05 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 05:54:19 --- quit: nighty- (Remote host closed the connection) 05:58:00 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 06:12:29 --- quit: gravicappa (Ping timeout: 256 seconds) 06:33:32 --- join: Zarutian_PI2 (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 06:33:42 --- quit: Zarutian_PI (Read error: Connection reset by peer) 07:00:08 --- nick: Zarutian_PI2 -> Zarutian_PI 08:43:03 --- join: mark4 (~mark4@cpe-75-177-17-25.triad.res.rr.com) joined #forth 08:44:52 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 09:28:13 is it possible to get hardware rendering in a virtualbox vm? 09:28:26 for some reason i cant seem to get it to work any more and im sure i did in the past 09:28:41 blargh wrong channel lol 09:44:10 --- quit: dys (Ping timeout: 240 seconds) 09:50:02 --- quit: backer (Ping timeout: 240 seconds) 09:52:07 I don't know about virtualbox, but it is with qemu/kvm 09:56:35 there is a menuconfig item in staging for virtualbox video drm :) 09:56:54 oh! 09:57:15 just learned about it a few moments ago. already building new kernel inside vm 10:18:51 --- join: backer (~backer@accordion.employees.org) joined #forth 10:24:12 --- join: dys (~dys@tmo-101-189.customers.d1-online.com) joined #forth 10:38:41 --- join: gravicappa (~gravicapp@ppp83-237-163-24.pppoe.mtu-net.ru) joined #forth 12:05:57 --- quit: dys (Ping timeout: 260 seconds) 12:12:49 --- join: dys (~dys@tmo-123-87.customers.d1-online.com) joined #forth 12:36:20 --- quit: ncv__ (Ping timeout: 240 seconds) 14:09:27 --- quit: gravicappa (Ping timeout: 240 seconds) 14:39:17 --- quit: mark4 (Read error: Connection reset by peer) 14:40:49 --- join: tomlukeywood__ (~quassel@host-92-19-232-58.static.as13285.net) joined #forth 14:40:51 --- join: mark4 (~mark4@cpe-75-177-17-25.triad.res.rr.com) joined #forth 14:48:07 --- quit: tomlukeywood__ (Remote host closed the connection) 15:38:44 --- quit: mark4 (Quit: Reality Strikes Again!) 16:28:47 --- join: karswell (~user@cust125-dsl91-135-5.idnet.net) joined #forth 18:20:15 --- quit: dddddd (Ping timeout: 252 seconds) 18:46:35 --- quit: karswell (Read error: No route to host) 19:09:13 --- quit: lijero (Remote host closed the connection) 19:54:02 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 20:26:22 --- quit: rpcope (Ping timeout: 252 seconds) 20:31:13 --- join: rpcope (~GOTZNC@162.245.217.4) joined #forth 21:14:14 --- quit: Gromboli (Quit: Leaving) 22:12:20 --- quit: groovy2shoes (Ping timeout: 252 seconds) 22:25:02 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 23:41:44 --- quit: dddddd (Remote host closed the connection) 23:59:59 --- log: ended forth/18.02.02