00:00:00 --- log: started forth/05.04.15 01:10:39 --- quit: Herkamire ("off to bed") 03:04:05 --- quit: tathi ("leaving") 03:25:41 --- join: skylan_ (~sjh@dialup-216-211-5-113.tbaytel.net) joined #forth 03:28:27 --- quit: aum () 03:38:44 --- quit: skylan (Read error: 110 (Connection timed out)) 05:30:33 --- nick: sk1p_ -> sk1p 05:39:06 --- quit: ASau (Read error: 60 (Operation timed out)) 05:45:33 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 06:16:22 --- join: aum (~aum@60-234-138-239.bitstream.orcon.net.nz) joined #forth 07:07:48 --- quit: madwork (Read error: 131 (Connection reset by peer)) 07:07:51 --- quit: aum () 07:19:08 --- join: ASau (~user@83.102.133.66) joined #forth 08:36:38 --- quit: qFox ("this quit is sponsored by somebody!") 08:53:38 Dobry vecer! 08:53:46 Random stuff updated. 08:54:29 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth 08:55:38 Also I've got fixed point multidimensional optimization. 08:56:35 Hooke---Jeeves algorythm. Polished enough. 08:57:32 It can be easily converted to utilize floating point numbers, if needed. 09:23:38 --- join: Herkamire (~jason@c-24-218-95-147.hsd1.ma.comcast.net) joined #forth 09:23:38 --- mode: ChanServ set +o Herkamire 14:28:58 HI ALL 14:29:09 err, caps lock on by accident :( 14:58:18 --- join: Topaz (~top@spc1-horn1-6-0-cust219.cosh.broadband.ntl.com) joined #forth 14:59:07 --- quit: qFox (Read error: 54 (Connection reset by peer)) 15:46:34 --- quit: Topaz ("Leaving") 17:20:00 goodnight 17:44:39 --- quit: Quartus (Remote closed the connection) 17:52:43 --- join: Rockford (~trailer@ansuz.pair.com) joined #forth 17:52:47 --- nick: Rockford -> Quartus 18:02:09 --- join: TheBlueWizard (TheBlueWiz@ts001d0872.wdc-dc.xod.concentric.net) joined #forth 18:43:55 somebody say somethinh im bored 18:44:30 --- join: aum (~aum@60-234-138-239.bitstream.orcon.net.nz) joined #forth 18:44:46 * TheBlueWizard burps...hopes that count :) 18:45:04 :) 18:56:26 --- join: cr3 (~marc@Quebec-HSE-ppp240708.qc.sympatico.ca) joined #forth 18:57:12 how is a string defined in Forth? I'm looking at the Gforth manual and not able to find the information there, though I'm sure it's in there. 18:59:19 depends on the forth 18:59:27 typically, its a counted string 18:59:40 that means, the first byte is the length of the string, then that many bytes after 19:01:54 arke: I don't mean how the string is represented internally, I just meant in a Forth script. For example, how would I define "a b c" as a string of 5 characters? 19:02:08 " a b c" 19:02:10 errr 19:02:14 s" a b c" 19:02:22 I dnt use ANSI Forth too often, so I might be wrong 19:02:24 that returns addres and count 19:02:29 s" is correct 19:03:15 arke: cool! thanks, that's exactly what I was looking for. 19:03:45 cr3: no problem :) 19:04:01 cr3: and thannks to hyrax for pointing out that it also returns the count.. 19:10:19 is there a particular implementation of forth which is more recommended than others, or does it really depend a lot on the context? 19:10:28 context and preference 19:10:34 i prefer retroforth 19:10:40 but itsnot at all like gforth 19:15:28 gforth is dying with: Cannot allocate memory. sad :( 19:16:20 yes 19:16:22 sad 19:16:22 :) 19:21:39 --- join: Sonarman (~cleetus@adsl-64-171-254-118.dsl.snfc21.pacbell.net) joined #forth 19:23:41 arke: is it worth looking into why gforth cannot be installed on a common linux distro, or is that just a sign of worse things to come? 19:24:24 cr3: actually, that is very odd 19:24:59 shall I get the sacrificial goat? 19:25:40 it's not as if this thing depends on any external libraries other than libc and libdl, does it? 19:26:57 linux goes in fine on a common linux distro. 19:27:01 er, gforth, I mean. 19:27:24 Hell, it runs on a Sharp Zaurus. 19:28:30 cr3: what distro? 19:28:39 arke: Fedora Core 2 19:29:24 mind if I paste 6 lines? 19:30:02 Go for it. 19:30:11 # GFORTHD="./gforth-ditc -p .:." GFORTH="./gforth-ditc --die-on-signal -p .:. -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs arch/386/disasm.fs" ./gforthmi gforth.fi --die-on-signal -p ".:~+:." -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs arch/386/disasm.fs 19:30:11 data offset=E0 19:30:11 code 19:30:11 in file included from *the terminal*:0 19:30:12 *evaluated string*:-1: images produced by different engines 19:30:14 comp-image ./temp-image.fi1 ./temp-image.fi2 gforth.fi bye 19:30:41 where the first line, preceded with the hash character (#), is the command generated during the make process which seems to fail. 19:32:33 What version of gforth is it? 19:32:38 latest, 0.6.2 19:33:15 running configure ; make ; make install doesn't work on 0.6.1 either. 19:33:24 Same error? 19:33:26 don't quite remember what was the error message though. 19:33:47 Roll back to 0.5.0, see if that builds. 19:33:56 Maybe there's something chronically unwell with your distro. 19:34:48 --- join: sk1p_ (alex@pD958C049.dip.t-dialin.net) joined #forth 19:35:00 Quartus: I work with several other programming languages on this box and build several programs every day, I must've been chronically lucky ;) 19:35:50 Could be :) I've never seen gforth not build, but there's a first time for everything. 19:36:12 ./gforth --die-on-signal -m 4M -p ".:~+:." -i kernl32l.fi -e 3 exboot.fs -e 'fpath= .|~+|.' -e 's" mach16b.fs"' ./kernel/main.fs -e "save-cross kernl16b.fi- /usr/local/bin/gforth-0.6.1 bye" 19:36:13 make: *** [kernl16b.fi-] Segmentation fault 19:36:26 that's what happens with gforth-0.6.1, trying 0.5.0 right now 19:36:29 Ok. 19:36:43 You're in as root? 19:36:55 nope, only for the install. 19:37:09 GFORTHD="./gforth-ditc -p .:/tmp/gforth-0.5.0" GFORTH="./gforth-ditc --die-on-signal -p .:/tmp/gforth-0.5.0 -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs arch/386/disasm.fs" ./gforthmi gforth.fi --die-on-signal -p ".:~+:/tmp/gforth-0.5.0" -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs arch/386/disasm.fs 19:37:10 data offset=7AD0E0 19:37:10 in file included from *the terminal*:34 19:37:10 *evaluated string*:-1: images produced by different engines 19:37:10 comp-image ./temp-image.fi1 ./temp-image.fi2 gforth.fi bye 19:37:16 Maybe it's a permissioning issue in your build tree. 19:37:19 And that was for 0.5.0, sorry for all the pastes 19:37:51 Quartus: cd /tmp; tar -xzf gforth-0.5.0.tar.gz; cd gforth-0.5.0; ./configure ; make 19:37:55 Ok, well it's officially you in some way, but I'm not sure how exactly. I'd guess the images aren't getting built, but exactly why would depend on your situation. 19:38:41 Compare the two images yourself, see which if they differ, see if they were both created by the make. 19:38:42 What the heck does this mean: data offset=7AD0E0 19:38:54 Probably the offset where the images differ. 19:40:05 temp-image.fi[1-2] don't seem to exist under the build tree, they must be generated with mktemp or something. 19:40:19 Or they're not getting created at all. 19:40:55 Quartus: I now tried compiling 0.6.2 on RedHat Enterprise 4, still get the same error 19:41:28 On a different box? 19:41:34 yes 19:41:46 Mystifies me. 19:42:30 I'm about to try on a Linux distro which happens to have a much older kernel, lets see how that goes. 19:44:51 my toocan sam nose suspects gforth might be making assumptions about the kernel when mapping memory. but what the heck do I know, I don't even know how to define strings ;) 19:45:07 Maybe. 19:45:42 works! do you happen to be running gforth on a 2.6.x kernel? 19:46:08 I'm not running it under Linux presently -- FreeBSD and Embeddix. 19:46:16 well, Emeddix is Linux. 19:49:11 I don't believe I have tried it under 2.6.x. 19:51:49 --- quit: sk1p (Read error: 110 (Connection timed out)) 19:51:56 I'm seeing people reporting they're using 0.6.2 under 2.6.x. 19:52:20 fedora 2, in fact. 19:52:34 gcc 3.3.3. Could that be it? 19:52:54 Quartus: maybe there's some mumbo jumbo (excuse the scientific lingo) with which I'm not terribly familiar when using gforth. 19:53:11 The build process doesn't involve either mumbo, or jumbo -- it should build. 19:53:25 Quartus: I compiled successfully with 3.2.2 on linux 2.4.x 19:53:33 What was the gcc under fedora 2? 19:53:47 Quartus: 3.3.3 19:54:44 Curious. 19:58:51 gotta jet, thanks for the help in getting gforth working. I've tried part of the tutorial already and it's pretty exciting, I'll be dropping by in the near future. g'night. 19:58:58 --- quit: cr3 ("Leaving") 20:19:51 bye all 20:20:09 --- part: TheBlueWizard left #forth 20:28:13 --- nick: skylan_ -> skylan 21:03:26 --- quit: swalters (Connection reset by peer) 21:51:08 --- join: x2Sx (~x2Sx@212.180.15.37) joined #forth 22:12:36 --- quit: x2Sx () 22:18:45 --- join: OrngeTide (~orange@c-67-180-163-152.hsd1.ca.comcast.net) joined #forth 22:18:48 hio 22:25:54 --- nick: sk1p_ -> sk1p 22:28:49 --- join: swalters (~swalters@2416457hfc118.tampabay.res.rr.com) joined #forth 22:44:13 --- quit: aum () 23:17:50 --- quit: Herkamire ("off to bed") 23:49:28 --- join: Serg[GPRS] (~z@193.201.231.126) joined #forth 23:52:08 hi ! who's online from USA ? 23:54:04 --- quit: Serg[GPRS] () 23:59:20 I am. but you left 23:59:59 --- log: ended forth/05.04.15