<joshsmt>
hello guys, idont if you saw my last message, but in 3.7 iso the curl doesnt work, is missing a lib
<SiFuh>
So much info, shame we don't know any of it.
<SiFuh>
Got a log?
<SiFuh>
What lib is missing? Also did you fresh install or update?
<SiFuh>
The lib in question was libhttp?
<joshsmt>
yeah
<SiFuh>
Fresh install or update?
<joshsmt>
no
<joshsmt>
it's on the iso live cd
<jaeger>
looks like nghttp2-libs was left out of the ISO packages... I'm trying to recall if I've ever wanted to use curl before the chroot step
<jaeger>
What's your use case for needing it before chroot?
<jaeger>
For what it's worth you should be able to use it just fine inside the chroot but I'm curious
<farkuhar>
hello joshsmt, i don't know if you saw the cruxbot notifications, but wasi-compiler-rt and wasi-libc++ (in the 3.7 ports tree) got the version bump that you were waiting for.
<joshsmt>
jaeger i use crux iso to bootstrap other distros as well
<joshsmt>
farkuhar ok i gonna see this when i get home
<jaeger>
Fair enough. Think you're the first person I've heard of doing that specifically with crux, but makes sense
<SiFuh>
Good thing Arch and Alpine were not people
<jaeger>
What do arch and alpine have to do with it?
<SiFuh>
Out of curiosity. jaeger do you rememeber which linux distro Per had boot strapped the first core for CRUX off of?
<jaeger>
I don't, sorry
<SiFuh>
Also that answers your previous question about Arch and Alpine
<SiFuh>
From what I had learned they both bootstrapped off of CRUX
<jaeger>
No idea about alpine... but arch was inspired by crux if I remember right, not built directly from it
<jaeger>
Neither of them use crux to bootstrap installs, which is what I was getting at here
<SiFuh>
Well not now, but got it ;-)
<SiFuh>
jaeger: You are in the US right? Do you mind if I know the state?
<jaeger>
Yes, in the midwest. Oklahoma
<SiFuh>
Ohhhh so sad
joshsmt has quit [Quit: Client closed]
<jaeger>
joshsmt: as a workaround you could uncompress the libnghttp2 package from the ISO into the boot environment's tmpfs and use it
<SiFuh>
I had watched 'The Greatest Beer Run Ever (2022)', excellent movie. There was a Vietnamese Traffic Cop that loved the movie Oklahoma from 1955 so in the end it kind of became his nickname.
<SiFuh>
Mr Norris was from Oklahoma
<SiFuh>
If I ever came back to US I'd choose Texas
<SiFuh>
jaeger: 'Sad' was referring to the movie I had just watched.
ocb has quit [Ping timeout: 258 seconds]
ocb has joined #crux
ocb has quit [Remote host closed the connection]
ocb has joined #crux
<jaeger>
in yet another "I hate computers" kind of situation, I have one box that cannot compile rust. It's a Ryzen 3700X on a Gigabyte Aorus X570 Elite motherboard with 16GB RAM. Every rust build fails with sig 11 segmentation faults, which almost always indicates bad RAM... but I can't get any other package to fail and the RAM all tests fine :P
<jaeger>
Going to put some other RAM in it to see if that's the problem even though the RAM tests are fine
<SiFuh>
Similar to when ROmster introduce QT6. My PC needed a crap load of build space
<jaeger>
Figures... even though the RAM tests come back fine, the rust build succeeded with different RAM
_0bitcount has joined #crux
<SiFuh>
Hmm
<SiFuh>
I don't even want to look into that. Not a rust fan from the start
<jaeger>
I have no interest in it other than as a dependency
<SiFuh>
I don't like rust
<SiFuh>
But it is here and it is coming so, I will ahve to agree
<braewoods>
jaeger: SIGSEGV doesn't necessarily mean bad RAM.
<braewoods>
It can simply be resource exhaustion. If they don't check allocations for failure, this can happen.
<braewoods>
Due to dereferencing an invalid pointer.
<braewoods>
But you'd think Rust would handle this gracefully given its whole design mantra.
<braewoods>
Pretty much every SEGV I've gotten was due to memory handling bugs.
_0bitcount has quit [Quit: Leaving]
<jaeger>
Agreed, not necessarily 100% of the time... but it looks that way in this case
DanDan has quit [Ping timeout: 246 seconds]
chrcav has joined #crux
DanDan has joined #crux
DanDan has quit [Ping timeout: 252 seconds]
tilman has quit [Ping timeout: 265 seconds]
tilman has joined #crux
<ocb>
jaeger: managed to get your laptop replaced?
<jaeger>
Still waiting
<ocb>
damn, they're slow
<jaeger>
yeah, seems slow, but I don't know what else they have on their plates