chungstoin has quit [Quit: Konversation terminated!]
worf1337 has quit [Ping timeout: 252 seconds]
angerisagift has quit [Ping timeout: 260 seconds]
angerisagift has joined #kisslinux
worf1337 has joined #kisslinux
worf1337 has quit [Ping timeout: 268 seconds]
worf1337 has joined #kisslinux
worf1337 has quit [Read error: Connection reset by peer]
worf1337 has joined #kisslinux
angerisagift has quit [Ping timeout: 246 seconds]
angerisagift has joined #kisslinux
ulterno has quit [Quit: Konversation terminated!]
fultilt has quit [Quit: Leaving]
angerisagift has quit [Ping timeout: 268 seconds]
angerisagift has joined #kisslinux
<
sewn>
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaAAAAAAaaaaaaAAAAAaaaAAAAaaaAAAAaaaaaaAAAAAAAAAAAAaaaaaAAAAAaaaAAAaaaAAAAAAAAAAAAAAAAAAAaaaaaaaaaaa
<
il>
why are you yodeling?
<
sewn>
no im just screaming
<
sewn>
yodeling is more like..
<
sewn>
OuuuuAAAHhhhAAHuuuououuoAUhhhhOUUooooHHHYyuuhhoooUUOohhhOOHHHhhh
<
il>
I didn't ask what you're doing, though
solaare has quit [Ping timeout: 252 seconds]
solaare has joined #kisslinux
kmf has joined #kisslinux
kmf has quit [Remote host closed the connection]
kmf has joined #kisslinux
kmf has quit [Read error: Connection reset by peer]
vouivre has joined #kisslinux
<
vouivre>
sewn: not bad for yodeling
<
vouivre>
does somebody else has the problem as me with the last update of libxml2 ?
vouivre has quit [Remote host closed the connection]
vouivre has joined #kisslinux
<
vouivre>
phoebos: I saw you pinged git-bruh about the issue. Isn't git-bruh automatically notified about issues ?
<
vouivre>
it was my assumption
vouivre has quit [Client Quit]
<
phoebos>
just for completeness
vouivre has joined #kisslinux
<
vouivre>
phoebos: you did the last release of kiss (24.12.18)
vouivre has quit [Remote host closed the connection]
vouivre has joined #kisslinux
<
vouivre>
on the releases notes it's recommended to set the CFLAGS to
<
vouivre>
CFLAGS="-march=x86-64 -mtune=generic -pipe -Os"
<
vouivre>
on a fresh kiss install I wasn't able to build openssl with an amd computer
<
vouivre>
only after setting
<
vouivre>
CFLAGS="-march=native -pipe -Os"
<
vouivre>
I was able to build openssl
<
vouivre>
on a computer with an intel processor no problem.
<
vouivre>
I assumed "-march=x86 -mtune=generic" was generic and for all X86_64 processors. Am I wrong ?
vouivre has quit [Quit: nyaa~]
<
phoebos>
they're not a recommendation
<
phoebos>
they're what was used to build the tarball
<
phoebos>
i don't think -march=x86 is a valid option?
<
phoebos>
-march=x86-64 is "a generic cpu with 64-bit extensions"
macquat has joined #kisslinux
macquat has quit [Client Quit]
vouivre has joined #kisslinux
<
vouivre>
sorry, you are right, it was a typo
<
vouivre>
-march=x86_64 is the right parameter
<
vouivre>
but for an unknows reason it didn't work for my processor
<
vouivre>
amd 9950x
<
vouivre>
Instructions set: x86-64
<
vouivre>
in the install there is -march=native. As I have seen, it seems optimized for the processor.
<
vouivre>
why did you choose x86-64 ?
fultilt has joined #kisslinux
vouivre has quit [Quit: nyaa~]
<
phoebos>
what do you mean
<
phoebos>
the binaries on the tarball are meant to run on any x86-64 so aren't built with extensions specific to my processor