Oddbean new post about | logout
โ–ฒ โ–ผ
 seriously? i never got this issue. 
 Have you had success compiling Lume ? 
 Wait nvm it wasnโ€™t Lume it was Gossip 
โ–ฒ โ–ผ
 trying now.
 
โ–ฒ โ–ผ
 followed instructions, compiled ok. seems to be working.

https://image.nostr.build/f27f93349cbfbd9386a91285ebc080f497ee2db4aae459dc3e6cc97869caaa4c.png 
 ๐Ÿ‘€ itโ€™s either that Iโ€™m retarded or ARM64 based pc issues 

@M. Dilger ๐Ÿ‘€ 
โ–ฒ โ–ผ
 oh.. probably arm64... i have plenty of issues with dependencies in my raspberry pi's... 
โ–ฒ โ–ผ
 gossip seems to use LMDB. LMDB has issues with arm, that need some fine tunning to work. this might be the issue here. 
 Ahhhh well I guess Iโ€™m fucked Iโ€™m not good at fine tuning ๐Ÿ’€ 
โ–ฒ โ–ผ
 I didn't know LMDB has issues on ARM. If you have compile failures, or runtime issues with LMDB data corruption, please file an issue on github so I can try to find the problem    https://github.com/mikedilger/gossip

Also, gossip compiles on windows without needing WSL. You just need a git-bash shell to run the commands from. 
โ–ฒ โ–ผ
 alignment matters on arm if doing zero copy flatbuffer stuff, on intel its just a performance hit. this has nothing to do with lmdb tho, we use lmdb on ios and it works fine. 
โ–ฒ โ–ผ
 Yes ok alignment matters.  LMDB data is just a sequence of bytes so it is not doing any alignment, and I presume each LMDB value starts aligned.  I'm using speedy for most of the data, and I see zero issues on the speedy repository about anybody getting alignment errors.  That is why I'd love to see an error message, so I can know this issue is real and then chase it down, rather than trying to fix something that might not be broken. 
 Iโ€™m gonna hop on @HiveTalk in like 20 mins to try doing it again Iโ€™ll share my screen n see if anyone can help walk me thru it 
โ–ฒ โ–ผ
 Not specific to gossip. I had problems with both stfry and khatru. It's usually at runtime, when initializing the DB it complains of "out of memory" (i suspect it is actually complaining of low disk space). I'ts usually solvable by lowering the size limit for the DB. (strfry has a param for that, but in kathru i had to fork and change the source).

I haven't tried gossip in arm yet, i'll try it tomorrow and if i run into troubles, i 'll post an issue. 
โ–ฒ โ–ผ
 Ah yes. You have to tell it how big the database might eventually become ... a max size... when you create it.   If you don't have that much space it would fail. 
โ–ฒ โ–ผ
 it doesn't fail on linux-amd64 though. But it fails in other platforms. 
โ–ฒ โ–ผ
 Has something to do with sparse file support I'm guessing. 
โ–ฒ โ–ผ
 Anyway, the problem  @๐“ข๐“ฎ๐“ป ๐“ข๐“ต๐“ฎ๐“ฎ๐“น๐”‚ is getting is quite different, from his other posts. It seems he has problems with the C compiler:

nostr:note1yekq0lmw8fjkdtee6s3appxzwqn7vaqrr2xyk007twneeyt6rp7syj7vv9 
โ–ฒ โ–ผ
 We use 24GB.  I could make a launch option to set it smaller I suppose.