<Viking668>
wow. All quiet on the Western, Eastern, and Northern fronts...
<Viking667>
And down here on the Southern front...
zardshard has left #haiku [Error from remote client]
<erysdren>
im (somewhat) here
<erysdren>
hi
zardshard has joined #haiku
<Viking667>
hrm. I'll have to go back to the earlier patchset OscarL did - this one I've cobbled together not working for me.
<Viking667>
Wow. Looks like I was here back in September/October - again talking to OscarL.
erysdren has quit [Quit: Konversation terminated!]
<scanty>
Viking667: Oscar is a good guy. i know him for many years
<Viking668>
mmm.
<Viking668>
I've lost a link, I'll have to dig through the logs
<Viking668>
Found the link in my browser history. Phew. Still doesn't help me compile though.
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
<Viking667>
tip tap, tap tap tip,...
<Viking668>
Sorry about that, I was resetting timestamp in Emacs ERC channel window.
zardshard has left #haiku [Error from remote client]
deneel has joined #haiku
zardshard has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
vdamewood has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Viking668 has quit [Quit: *croak*]
melnary has joined #haiku
OscarL has joined #haiku
<OscarL>
Viking667: good night. I have a pretty clean/small patchset for latest libfossil+fnc.
<OscarL>
was getting a unexpected linker error, but I think I have resolved it by disabling use of -fPIE when compiling fnc on Haiku (upstream fnc doesn't use that either, so...).
<Viking667>
?
<OscarL>
Will run a clean build of my libfossil-2025.04.02.recipe, just to confirm things, and will share the new .patchset.
<Viking667>
I noticed that linker too, I was wondering if it was an internal compile error.
<Viking667>
s/linker/link error/
<Viking667>
And yes, that would be absolutely fantastic - I've been banging my head against that one and not getting anywhere
<OscarL>
Viking667: seems that the with the GNUmakifile changes libfossil introduced in newer versions, it added -fPIE inconditionally. I don't remember the details, but Haiku mostly uses/defaults to -fPIC, IIRC, and seems that mixing -fPIC and -fPIE was tripping the linker.
<Viking667>
I tried the compiler without -fPIE, it kept whining. I tried it WITH -fPIE it whined.
<Viking667>
Just so you've got a heads-up, Stephan's looking at recreating the Makefile toolset from scratch in parallel.
<OscarL>
Viking667: in any case... as libfossil copies fnc from upstream... and the biggest part of the patch is for fnc... I think it makes more sense to send that to fnc first.
<OscarL>
changes to libfossil's GNUMakefile are pretty small, and well contained now.
<Viking667>
Yah - it means I'll have to send a message to the fnc mailing list. At least that works.
<OscarL>
Not sure if exactly what upstrem will like, but I think is better to show Stephan that diff, and let him decide.
<OscarL>
seems my build went fine :-)
<Viking667>
Yup. I'll put it into a branch for him to look at. I'm assuming you're talking about the libfossil patch here/
<Viking667>
?
<OscarL>
let me install the packages, smoke test them, and will let you know.
<Viking667>
Heh. I like that term. I've heard that on and off since my electronics days in the '80s.
<OscarL>
yes! "fnc --version" -> "fnc 0.19 [7a8431de2a] 2024-10-01 14:06:26 UTC" (that comes from libfossil's fnc)
<Viking667>
uh? Nice. What GNUmakefile.in patches are there?
<Viking667>
I'll go bring up the Haiku VM
<Viking667>
mind you, I've got an OpenBSD VM running just now - that's on this local machine, I gotta love network-accessible VMs.
<OscarL>
uff, bpa.st not working right now, let me try 0x0.st
<OscarL>
for fnc, I attempted to make it work for both beta5 and nightlies. So far I have only tested it on beta5. Will try a nightly in a moment.
<OscarL>
(the libfossil's copy of fnc I mean)
Viking668 has joined #haiku
<Viking668>
whoops, sorry about that - I may have missed a link or three
<Viking667>
Ah, here we are. The beauty of running two ERCs
<OscarL>
meanwhile my nightly VM is having netwokring issues, and not letting me install the required tcl package I need to build libfossil :-)
* OscarL
cheats by severing all connections, and installing tcl*.hpkg from his beta5 installation.
<OscarL>
mmm, it is compiling reallocarray.c in my nightly too, lol.
<OscarL>
ideally it would use the reallocarray from the system but, at least the build goes fine, and fnc runs OK on nightlies too.
melnary has quit [Ping timeout: 480 seconds]
<OscarL>
nah, we're good. even if reallocarray.c is "compiled", it won't include anything on nightlies because it uses a "#ifdef HAVE_REALLOCARRAY" block.
zardshard has left #haiku [Error from remote client]
<OscarL>
So, Viking667, that patchset I've sent is the best I can do for libfossil+fnc. I will update the patch I have for upstream newest fnc so both match.
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
freakazoid332 has joined #haiku
<OscarL>
from upstream fnc on nightlies: fnc 0.19 [a89c68b7d2] 2024-11-10 11:33:20 UTC
<Viking668>
as each of those is a checkout hash, I can figure out what the current hash is, then step back if needed.
<OscarL>
those hashes are the newest I could find.
<Viking668>
right.
<OscarL>
the way those patches are applied on Haiku (when using Haikuporter) is: the tarball gets unpacked, then "git init" gets called on that dir, an initial commit adds all the original files, and then "git am xxx.patchset" applies the patchsets.
<Viking668>
Ah well. I'll have to poke this again. libfossil's copy of fnc crashes fairly consistently
<Viking668>
heh. I do it far simpler. I do "fossil clone ...", then "mkdir libfossil; cd libfossil; fossil open ../libfossil.fossil"
<OscarL>
well, I have all for versions
<Viking668>
then I head off and grab the patch file, and use patch. "patch -p1<82Ya.patchset"
<OscarL>
*working... older and current "masters" from upstream.
<OscarL>
Viking668: in Haiku I just do "hp libfossil" and the tool handles all the mentioned steps for me, I was just commenting how it works under the hood, in case it might help them apply them on your side :-)
<Viking667>
Okay. I'll smoketest that over on Linux and OpenBSD
<Viking667>
I haven't even started with hp yet
<Viking667>
given that my normal run of "configure" involves --prefix=/boot/home to put it in the "right"ish place.
<OscarL>
as I run it from an hp recipe, I use --prefix=$prefix (where $prefix == /boot/system)
<OscarL>
Viking667: you should be using --prefix=/boot/home/config/non-packaged
<Viking667>
I think the install location is about the only thing that differs
<Viking667>
heh. Then where do the binaries go?
<OscarL>
the "non-packaged" sub dirs (there's one under system, and one under home)...
<OscarL>
contain a read-write hierarchy that matches the one under /system/
<Viking667>
I suppose those are in$PATH?
<OscarL>
yes /boot/home/config/non-packaged/bin is in $PATH
<Viking667>
hm.
<OscarL>
"stuff" in Haiku can be either packaged or non-packaged, and be at system or user (home) level. so in the end you have 4 "bin" locations for example. and search path for those are from more specific. user's before system, and non-packaged over packaged.
<Viking668>
so, to call the recipe, do I need to be in the place the recipe is, or in some hierarchy?
<OscarL>
no, HaikuPorter has a config file that tells it where the haikuports repo is located, so you can call it from wherever.
<OscarL>
(as long as you remember the correct name for the port you want to build)
<Viking668>
I guess that libfossil and fnc haven't made it to the "official" location yet?
<OscarL>
not so far. I've placed them under: haikuports/dev-vcs/fnc and haikuports/dev-vcs/libfossil
<Viking667>
okay, where's that in the filesystem?
<OscarL>
libfossil might better belong under dev-libs perhaps, but only if we actually merge both recipes (and disable fnc from libfossil)
<OscarL>
I use /Data1/haikuports/, but that's up to you.
<Viking667>
/Data1? hm.
<OscarL>
that's the name of one of my BFS partitions. I have many.
<Viking668>
... and you point the config at that location?
<OscarL>
I have many Haiku installs... beta5 vs nightlies, 64 vs 32 bits, etc, etc.
<OscarL>
so I try to centralize things I can use from all of them in those /DataX partitions.
<OscarL>
on the /boot/home/config/settings/haikuports.conf file, yes
<zdykstra>
OscarL: !
<OscarL>
hello there zdykstra! :-)
<OscarL>
all well on your side of the world? (at least close to you I mean)
<OscarL>
Viking668: in that file I have: TREE_PATH="/Data1/haikuports"
<OscarL>
(among other things so I can use a "ram drive" for builds instead of killing my crappy SSD :-D)
<Viking667>
Okay, I'll go look for the config file location
<Viking667>
heh. I can't really "do" RAM drives. This VM only has 2GB and 2 CPU cores allocated.
janking has quit [Quit: Vision[]: i've been blurred!]
<Viking667>
mind you, the host has 32GB, I could happily allocate more memory.
<OscarL>
I was using a ram drive even with 2 GB, but then had to give the VM 3 GB, and later 4 GB to handle some larger builds :-)
<OscarL>
I should probably just do a post on the forums about my setup.
wicknix has quit [Ping timeout: 480 seconds]
<OscarL>
Originally, I kept a haikuports repo for 64 bits, and a different one for 32 bits... all on slow HDD. was a major PITA.
<OscarL>
now I have only one repo for all, 32b/64b, beta5/nightlies. Recipes, patchsets, tarballs and built .hpkg files remain on SSD, but the "work-dirs" (where tarballs get unpacked/patched/compilled) are in RAM.
* OscarL
copies those lines as intro for the possible forum post
janking has joined #haiku
<janking>
Good morning to you all :)
<OscarL>
Hello there janking. Same to you :-)
<janking>
:)
wicknix has joined #haiku
<Viking667>
Thank you for getting those patches together for me - I very much doubt I could have done the same.
<Viking667>
If you'd like your email address added as a contact, pass it to me via PM and I'll put it into the post/commit message for each.
<Viking667>
If you want to remain without email address, let me know and I will at least mention your name.
<OscarL>
happy to be of any help.
<Viking667>
...ahhhh. That perc coffee is intriguing. (A Moka pot, for future reference)
<OscarL>
the .patchsets I shared/linked already have my name and email. Albeit I may not even check it, though :-)
<OscarL>
in any case, the patches kept getting smaller and smaller, which is great, feel free to use them as you see them fit, without even mentioning me.
<Viking667>
Yup. The bit I don't know is: do you want your email elided, or left in?
<OscarL>
the name only would be more than ok. thanks.
<Viking667>
Good, then that's what I'll do.
Aedil has joined #haiku
deneel has quit [Read error: Connection reset by peer]
deneel has joined #haiku
Aedil has quit []
Aedil has joined #haiku
deneel has quit [Read error: Connection reset by peer]