<The_Ringmaster>
does anyone use chat-o-matic? it doesn't seem to work right. there's no window title bar
Diver has joined #haiku
<Begasus>
the one working on it back then doesn't seem to be in the channel
<PulkoMandy>
you can try reporting bugs on her github
<PulkoMandy>
but it seems she's back using Linux these days
<Begasus>
or use Renga? ;)
<PulkoMandy>
Renga does only XMPP and no other protocol (unless there is a bridge on the server side)
<Begasus>
ah, can't you import lbipurple for the others? ;)
<The_Ringmaster>
I was looking for discord support and just found this app
<PulkoMandy>
I don't want to. libpurple results in implementing only the minimal common subset of all chat protocols, and I have enough work to do on properly doing XMPP already
<Begasus>
np, could only ask :)
<Begasus>
k, 2 left for libsdl it seems according to the reports (me wonders if anyone ever checks up on those) :)
<Begasus>
note to self (others), do not revert the change for coreutils, Haiku depends on it (providing non suffixed package)
<Begasus>
PR closed
xet7 has quit [Ping timeout: 480 seconds]
bjorkintosh has quit [Remote host closed the connection]
<mrjones>
looks like the right kind of era for me ;)
<Begasus>
why do we need secondary build for autoconf213 (it's the only one in the list containing secondary arch
<Begasus>
PulkoMandy, automake 1.16.5 has "?arm" in there, does that mean you tested an older version for arm?
<Begasus>
the others don't have that
<Begasus>
and only 1.16.5 and 1.13.1 are active
mrjones has quit [Quit: Vision[]: i've been blurred!]
mrjones has joined #haiku
mrjones has quit []
<PulkoMandy>
Begasus, I don't know, probably an older version is used in haikuports-cross or is used in haiku and it seemed easier to keep that one enabled for ARM?
<Begasus>
k, I'm not familiar with haikuports-cross, are they relying on haikuports recipe in some way?
<PulkoMandy>
no, it's a separate set of recipes
<PulkoMandy>
for new platforms it may be easier to reuse the same versions on both sides, but it's not too important, someone who wants to work on the ARM port can fix these things if needed
<PulkoMandy>
(ideally by updating haikuports.cross rather than downgrading haikuports :))
<x512[m]>
PulkoMandy: Still think it is better to have unified haikuports without separate cross.
<x512[m]>
Also GCC in haikuports.cross is semi-broken.
bjorkintosh has quit [Remote host closed the connection]
<PulkoMandy>
fine, are you going to contribute and maintain the recipes that can be used to build both from Linux and Haiku? you canthink it is better, but if no one does that work; it doesn't exist, while haikuports.cross exists
<PulkoMandy>
also recipes in haikuports.cross have reduced dependencies so we can build starting from some linux host tools only. recipes in haikuports have circular dependencies and rely on an already existing set of packages. Do you have plans to solve this?
bjorkintosh has joined #haiku
<x512[m]>
It should be possible to setup automatic HaikuPorts building on Linux with GitHub Actions etc..
<PulkoMandy>
yes, "it should be". Who wants to do the work?
<trungnt2910[m]>
x512[m]: This repo uses a brute force method that builds everything every time.
<trungnt2910[m]>
Imagine building a few thousand recipes.
<trungnt2910[m]>
Then there's the task of setting up a VM.
<x512[m]>
There are not so many packages that need to be crosscompiled.
<Begasus>
I doubt that would pass trungnt2910[m], probably still some broken recipes around ...
<x512[m]>
Haiku packages crosscompiling is done from Linux, no Haiku VM is needed.
<x512[m]>
Even more: packages crosscompiling currently work from Linux only and don't work from Haiku.
bjorkint0sh has joined #haiku
<PulkoMandy>
x512[m], so, the github action is already in place in haikuports.cross. Now all we need is 'someone' submitting fixes for all the problems it detects
<Maston[m]>
<Forza> "Maston: how do you mean.? If you..." <- i mean, install haiku in a 10 GB image, then boot that image with grub as loopback
<PulkoMandy>
just create a partition. nothing else is supported, you need a partition and it has to be in BFS format
<Maston[m]>
🛌
<x512[m]>
PulkoMandy: At least some time ago it was possible to boot from ISO FS.
FreeFull has joined #haiku
<PulkoMandy>
yes that may work too, with attribute overlay and write overlay
<PulkoMandy>
but I wouldn't say it's still supported
HaikuUser has joined #haiku
HaikuUser has quit []
bjorkintosh has quit [Ping timeout: 480 seconds]
novaphoenix has quit [Quit: gone fishing]
phoenix has joined #haiku
zard has joined #haiku
<kallisti5[m]>
<PulkoMandy> "who is going to fix it? this..." <- Yup. I played with those actions briefly, but they never really worked. Patches welcome 😁
<Begasus>
k, think I'm done so far for diffutils/automake and autoconf, waiting for replies :)
<zdykstra>
mornin' all
orealis has quit [Read error: Connection reset by peer]
<ahwayakchih>
i saw your conversation abotu cross tools action on github and fixed it, i'm waiting for it to finish to see if there's any other problem there
<ahwayakchih>
is full git history needed for them? i'm asking because i noticed that full clones are done in workflow script, but maybe `--depth 1` would be enough?
orealis has quit [Read error: Connection reset by peer]
orealis has joined #haiku
<ahwayakchih>
it would make running the workflow slightly faster, although compared to build times it would not make much difference
<Begasus>
I'm not familiar there ahwayakchih, don't even have a linux setup here :)
<Begasus>
anymore*
<zard>
So you use just Haiku?
<ahwayakchih>
hehe, ok :). but when you're building Haiku regular way, do you need full clone, or just a "shallow" one?
<zard>
Shallow suffices in my experience
<ahwayakchih>
ok, thanks
<Begasus>
running Haiku native on both the laptops now zard
Guest5173 has quit [Read error: Connection reset by peer]
zard has quit [Quit: leaving]
Halian has quit [Ping timeout: 480 seconds]
BrunoSpr has joined #haiku
BrunoSpr has quit []
jmairboeck has joined #haiku
BrunoSpr has joined #haiku
BrunoSpr has quit []
vdamewood has quit [Remote host closed the connection]
vdamewood has joined #haiku
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
jmairboeck has quit [Quit: Konversation terminated!]
DKnoto has quit [Quit: Leaving]
BrunoSpr has joined #haiku
<BrunoSpr>
hello
BrunoSpr has quit []
sarmonsiill has joined #haiku
<sarmonsiill>
Hello everyone. Is it possible to use Let's Encrypt (certbot) on haiku?
<Habbie>
hi sarmonsiill
<Habbie>
a lot of software just works on haiku
<Habbie>
certbot is not in haikuports currently
<Habbie>
maybe you can just try to use it?
<moparisthebest>
sarmonsiill: acme.sh is what I use on Linux, probably works
vdamewood has quit [Remote host closed the connection]
vdamewood has joined #haiku
Halian has joined #haiku
trn has joined #haiku
<trn>
Hi, quick question ...
<trn>
I see there is a pthread_getname_np defintion in gnu/pthread.h - what's the proper way to go about getting that?
erysdren has quit [Quit: Konversation terminated!]
<PulkoMandy>
#define _GNU_SOURCE before you #include <pthread.h>, or set your compiler to use -std=gnu99 instead of -std=c99 (adjust for the specific language version you want)
<trn>
PulkoMandy: Hrrm. I'm pretty sure that I was defining _GNU_SOURCE first, explicitly.
<trn>
I guess I can try -std=gnu11 as a quick test.
<PulkoMandy>
maybe something is brokeen then
<trn>
Let me check before I waste anyones time.
<PulkoMandy>
do you get a compile time or link time error?
<PulkoMandy>
(missing prototype or undefined reference?)
<PulkoMandy>
ah, yes, clang default include path may be missing some things
<trn>
That's probably not your fault.
<trn>
I'm not sure how to work around it though, because something like #include <gnu/posix.h> upsets things.
<trn>
I was hoping to get one less ifdef :)
<PulkoMandy>
I think you can add /system/develop/headers/gnu to the system include paths, but I don't remember if you have to add it before or after the existing ones
<PulkoMandy>
and I also don't remember how to print gcc default include paths
<PulkoMandy>
looking at the header it seems it should be added before headers/posix/. Not sure if that's doable from clang command line
<trn>
Since it returns an int, it's only going to give me a warning on Clang, which is kind of acceptable, because Haiku doesn't error on -Wimplicit-function-declaration
<trn>
But it's kind of annoying.
<trn>
Is there somewhere I should report this as a bug in Clang?
<trn>
PulkoMandy: FWIW, `clang -isystem /boot/system/develop/headers/gnu` instead of Clang seems to work.
<trn>
I think, for now, I'm going to include the definition myself, wrapped in `#if defined(__HAIKU__) && defined(__clang__) && !defined(_GNU_PTHREAD_H_)`
<trn>
If a newer Clang package comes out that fixes it, I'll check the version. I doubt the defintion of that or the header will change soon, and if it does, it's still only a warning.
<trn>
Thanks for the pointers.
<PulkoMandy>
Yes, I don't expect much changes in that area :)