<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]
melnary has joined #haiku
Viking668 has quit [Quit: shutting down]
<Begasus[m]>
g'morning peeps
deneel has joined #haiku
<OscarL>
hello Begasus[m].
<Begasus[m]>
Hola OscarL ! :)
<Begasus[m]>
catching up on forum/logs/mail :)
<Begasus[m]>
HEICTranslator ... need to check :)
<Begasus[m]>
finaly made a post on you setup I see OscarL +1
<OscarL>
And somehow mananged to not make it THAT long :-)
<Begasus[m]>
yeah :D
<OscarL>
(had made a few attempts in the past, but it kept getting longer and unfinished :-D)
<Begasus[m]>
got lost in that other post you ddi earlier :)
<Begasus[m]>
s/didi/did
<OscarL>
yeah, that one was written at the same time I was actually doing the work of updating the git patchset, so I documented *everything* I though important (or that I knew I would forget :-D).
<OscarL>
need to write a new version, but motivation is low, now that *I* know how to do it :-)
<Begasus[m]>
don't have anything to "share" in cases like this for the moment (I think) :)
<Begasus[m]>
coffee !
<Viking667>
Um, are the forums available from the top site? (https://haiku-os.org/ ?)
<nekobot>
• Peppersawce (c432c3b9): Omnispeak port (#12080)
<Begasus[m]>
what's the stat on the libfossil recipe OscarL ?
<Begasus[m]>
wait for fnc one or can this be merged?
<Viking667>
And after you answer that, what's in /Data1/haikuports ?
<Begasus[m]>
didn't check yet, both are required for fnc?
<OscarL>
Viking667: the git clone of the HaikuPorts repo.
<OscarL>
Begasus[m]: no. fnc is standalone.
<Viking667>
libfossil has some utility functions available _and_ a copy of fnc (that sometimes crashes), there is a standalone copy of fnc with other patches that doesn't seem to crash.
<Begasus[m]>
mine is /Opslag/haikuports :) (meaning is the same)
<Viking667>
Okay, that's what I needed to know. Thanks for that.
<Begasus[m]>
so both ready to merge OscarL ?
<OscarL>
Begasus[m]: I have both fnc and libfossil recipes. at the moment, the latter also provides cmd:fnc, if we merge both, we should disable fnc on the second.
<Viking667>
They pass the smoketest on my machine at least (as in, they compile to completion) and the fnc works "properly". I've been using some of the libfossil utility functions, so that appears to work in as far as I've tested it.
<OscarL>
nothing else on tree uses libfossil, so I'd say that merging fnc for now makes the more sense.
<nekobot>
• OscarL (5b1db33b): libmd: update to version 1.1.0. (#12098)
<Viking667>
If it were me, I'd disable fnc on the libfossil until upstream can get it consistently staying up without crashing.
<OscarL>
Begasus[m]: thus why I only opened a PR for fnc.
<Begasus[m]>
lol
<Viking667>
But that's not speaking as an official team member of libfossil.
<Viking667>
Anyhow, it's dinner time here - so it's hot dogs.
<Begasus[m]>
I thought there was a libfossil PR, there isn't?
<Begasus[m]>
enjoy Viking667 :)
<OscarL>
fnc from libfossil works just fine for me on both beta5 and nightlies, as built from recipes, so not convinced it is not a problem only on your side Viking667.
<OscarL>
Bon appétit, Viking667 :-)
<OscarL>
Begasus[m]: I only shared a link to my branch so certain viking could take a look at my first attempt at libfossil+fnc
<Begasus[m]>
so best wait for libfossil PR before merging fnc?
<OscarL>
no. fnc doesn not needs the libfossil recipe.
<Begasus[m]>
ok, let's merge fnc then
<Begasus[m]>
libfossil is mentioned in the recipe for fnc, but not as a requirement?
<OscarL>
it's tarball already includes a copy of libfossil source code.
<nekobot>
• OscarL (26d27947): fnc: new recipe. (#12093)
<calcmandan>
alt.os.haiku is dead. last post was 2018
<calcmandan>
bummer
ChaiTRex has quit [Ping timeout: 480 seconds]
<Begasus[m]>
haven't used newsgroup in ages here also, since most providers shut down the interesting ones :)
<calcmandan>
lol, a post titled haiku r1 beta 1
<calcmandan>
there are a few providers of free newsgroups.
<phschafft>
mau Begasus[m], also mau the rest.
<calcmandan>
i pay $5/month for a good service with posting rights.
<calcmandan>
quite vibrant still.
Traveler has quit [Quit: Vision[]: i've been blurred!]
<calcmandan>
well, i see here that emacs is written for haiku. that's a huge selling point.
<calcmandan>
and i'll have to find a terminal program that supports cp437
* Begasus[m]
pokes OscarL
<Begasus[m]>
fell asleep?
<OscarL>
bah, Traveler went away.
HaikuUser2 has joined #haiku
<OscarL>
was trying to cook something Begasus[m].
<Begasus[m]>
"trying" ... didn't go to well? ;) (enjoy)
<Begasus[m]>
breakfast here
<OscarL>
for future reference, yes, Haiku supports TRIM operations (at least for some devices/file systems). There's a /bin/fstrim command that users can invoke.
<Begasus[m]>
and trying to install KF6 update on the qemu image ...
<OscarL>
(for the details of how such commands instructs drivers to perform the trim)
ChaiTRex has joined #haiku
<OscarL>
calcmandan: Haiku's terminal supports code page 437. On its menu: Settings->Text encoding-> DOS Latin-US (IBM437).
<calcmandan>
awesome. does it support the file transfer protocols like zmodem?
<OscarL>
no. it is just a TTY emulator.
<OscarL>
There's a SerialConnect app, not sure what it supports.
<calcmandan>
is there a tty mode that a user can log into without going into teh gui?
<calcmandan>
i'll keep researching.
<OscarL>
other than that... "pkgman search xmodem" lists at least "lrzrz"
<calcmandan>
growing weary of the gnu/linux community.
<Viking667>
see if minicom is in the packages too.
<Viking667>
that's a good pair-up with lrzsz
<OscarL>
searched for that first Viking667, but it is not there.
<Viking667>
Ha. I've known about minicom since I first moved over to Linux back in 1.0.9 days.
<OscarL>
Haiku always boots into GUI mode. You can conect remotly to it via ssh (after some minimal setup).
<Viking667>
and that's going all the way back to 1996 for me. The laugh is that I ran it off two ESDI drives, the _full_ full height drives.
<OscarL>
there is no local mode "text/console" mode.
<calcmandan>
bummer
<OscarL>
(not unless you are willing to roll your own install, kill app_server, so "consoled" is the only thing available)
<Viking667>
Yah. People confuse it with a form of UNIX, it's not. And it makes no pretense of being a unix-like OS, aside from providing basic POSIX compliance.
<OscarL>
I booted Haiku in text mode in 2005, but never more since then.
<calcmandan>
yeah, i casually read about beos in the late 90s
<Viking667>
I tried the demo
<calcmandan>
found out about haiku tonight
<Viking667>
heh, well, welcome along.
<calcmandan>
thanks. i may just stick with the cozy confines of my pi500 and debian
<calcmandan>
or install haiku on a spare memory card and swap boot
<OscarL>
Haiku doesn't supports Raspberry Pi, nor any other arm/arm64 at the moment.
<Viking667>
If you want an alternative OS for your pi500, try one of the BSDs that supports it.
<Viking667>
Has Haiku ticked off all the BeOS boxes yet?
<OscarL>
only decent experiecen is on x86 32 or 64 bits. One developer has it running it his RiscV board, but he has to compile ALL the packages by himself (as there's no infrastructure setup for that port yet)
<Viking667>
At least he has a compiler...
<OscarL>
if I'm not mistaken, problem with RISCV boards is that are slow.
<OscarL>
(even the "high end" ones)
<calcmandan>
well, my wife just hopped into bed with no top on, which means, it's time for me to join her. going to bed. great meeting yall.
<Viking667>
At least they're not MIPS
calcmandan has quit [Remote host closed the connection]
CRThaze has quit [Ping timeout: 480 seconds]
<Viking667>
mind you, the one MIPS machine I was on, was actually pretty decent - 128 CPUs, and 128GB memory. It was an SGI Origin 2000.
<OscarL>
128 GB in 2000? hot damn.
<phschafft>
now calcmandan is gone.
<phschafft>
hm.
<OscarL>
I had only 4 MB of RAM well into 1997 :-(
<phschafft>
it puts me out of my misery of the ethics of sharing information. ;)
<phschafft>
OscarL: my WFW machine has 27MB of RAM. but I put every single module I found in it. down to those with 8KB. which also explains why it had such a strange amount of RAM.
<OscarL>
:-)
<phschafft>
I think my Alpha had 160MB, that was like 2001 or something.
<OscarL>
the late 90s / early 00s were crazy in how RAM, HDD, and CPUs got masive gains.
* phschafft
nods.
<OscarL>
Went from 486 SX, 4 MB in late 1997 (640 MB HDD), to K5-PR133, 16 MB (2 GB HDD), to Celeron 300, 32 MB (20 GB HDD), to Athlon 900, 256 MB of RAM and a 60 GB disk in Feb 2001.
<phschafft>
I was always a bit behind because I only had second hand hardware. but on the pro side I got the better hardware.
<OscarL>
(forgot to mention the 386SX 1 MB, floppy only, I had from 94-96 :-))
<phschafft>
my first machine was a 80286, 640KB RAM, one floppy.
<phschafft>
a laptop.
<OscarL>
fancy!
<phschafft>
on that machine I wrote my first multitasking kernel.
<OscarL>
meanwhile I still can't multitask myself.
<phschafft>
and I think it is the only machine I had that is still no longer working.
<phschafft>
(I also lost my Alpha, but it was in working condition at that time.)
<phschafft>
I think that first machine was my only one without SCSI. and only because the driver didn't want to load into so little RAM.
<OscarL>
I remember reading about Alpha back in the day, in the context of it being the "inspiration" for the progess AMD made into their Athlon line.
<phschafft>
yes, a lot of Alpha is today in AMD and AMD64.
<phschafft>
on of the things I used SCSI for was networking. ethernet over SCSI was just much faster than 10BaseT-HD.
<Viking667>
I think I started with a SYSTEM-80 (A New Zealand version of the TRS-80)
<Viking667>
bought my first "PC" in 1990, which was an XT clone. Never went down the road of the C64
<phschafft>
(yes, there are/were SCSI switches at that time (up to 640 Mbit/s per port))
<Viking667>
Probably time I departed, I'm still waiting for someone to reply to my other questions - and that might take a day or ten.
<phschafft>
Viking667: also never had a C64. I enjoy some of it's design aspects (strangely those other people seem to hate about it). But would like one in my collection.
<Viking667>
I have had an Amiga 500+ though.
<Viking667>
This one came with a GVP sidecart that also included its own '8088 or '286 card I could run MSDOS on.
<Viking667>
... very very slowly.
<phschafft>
;)
* Viking667
waves good morftervening to all
<phschafft>
erysdren provided me with some code. which I included in SIRTX that allows you to run some dos programs on a 8 bit machine with 2KB RAM.
<Viking667>
2kb?
<phschafft>
it can't handle more than a nice hello world, but hey, still fun.
<Viking667>
smallest machine I've seen supported for PC was 64k, and that was with a tape drie.
<phschafft>
after all you got about 512 Bytes of RAM for the program to use.
<Viking667>
drive.
<phschafft>
Viking667: SIRTX is one of my projects, a little (but already produtive) OS for small machines. 2KB physical RAM is the minimum requirement.
<phschafft>
if you have more you have more, sure thing. but that is the requirement.
<Viking667>
How large is the ROM?
<phschafft>
depending on what you include in the image. 32KB is the minium requirement.
<Viking667>
mmm hmm. Not too far different from the ROM in the Archimedes A3000 I had the use of. I think that had a 64KB ROM, though I don't know how large the RAM was.
<phschafft>
but it naturally depends on what options you enable, and how much data you have in the database.
<Viking667>
Anyhow, I'm outta here.
Viking667 has quit [Quit: *croak*]
* phschafft
nods.
Aedil has quit [Ping timeout: 480 seconds]
<gordonjcp>
aw, another Archimedes enthusiast but they left
<Begasus[m]>
text showing again in NeoChat and Quaternion on nightly :D
<Begasus[m]>
using KF6 6.12.0 and Qt6 6.8.3 though :P
<Begasus[m]>
so, 1, it isn't nightly issue, 2 needs software rendering for nighly (which doesn't seem to be needed for beta5)
<Begasus[m]>
well 1 maybe partial
freddietilley1 has joined #haiku
<OscarL>
by "needs software rendering" I assume you mean you have to "force" it to via some config/flag?
<gordonjcp>
Begasus[m]: wait is that Haiku running in Qemu on Haiku?
<OscarL>
yes, but without hardware acceleration
<OscarL>
(no kvm/nvvm)
freddietilley has quit [Ping timeout: 480 seconds]
<Begasus[m]>
right gordonjcp
<Begasus[m]>
handy to do some quick checks :)
<Begasus[m]>
hmm ... come to think of it, could maybe be an issue with rendering earlier in qemu OscarL ?
<OscarL>
my uneducated guess: maybe some change in nightlies makes it think we have working 3D support and thus it wants to use it, while on beta5 it just defaults to soft-rendering?
<Begasus[m]>
I don't think anything 3D has been inserted yet?
<OscarL>
if you were just testing in QEMU... dunno, you'll have to compare with bare-metal, I'm affraid.
<OscarL>
Begasus[m]: I was thinking maybe something in mesa/lavapipe.
<OscarL>
but just a thought.
<Begasus[m]>
was afraid about it yes
<Begasus[m]>
maybe I could switch between beta and nightly
<Begasus[m]>
looking at the commits at haikuports there hasn't been an update on mesa for a while
<OscarL>
if bare-metal testing is not easy.. if you still have Win... maybe test on VMware, that would at least be a different VM than qemu (trying to discard possible sources of errors)
<Begasus[m]>
if I don't run any other updates I could switch beta/nightly/beta without problems
<Begasus[m]>
booting other laptop
<OscarL>
I keep drooling every time I see the specs for that Ryzen 5 5825U :-)
<Begasus[m]>
heh
<OscarL>
amazing CPU at @15W
<Begasus[m]>
already thinking on something newer/faster :)
<Begasus[m]>
but it's just "thinking" right now :)
<OscarL>
I was considering buying an used 4700S + RX550 combo (CPU and 16 GB of ram both soldered to the little board), but had to spend my savings in some house reparations. So...
<nekobot>
• jernoble (5d237fff): [Cocoa] Adopt playback state properties of PIPViewController…
<nekobot>
• alanbaradlay (584b2ebb): [Cleanup] Move functions from RenderObject to RenderElement…
<OscarL>
I tend to leave 2 GB partitions just for nightlies (still haven't setup a 32 bits one), eaving a couple larger for beta5 32/64, and the rest in "/Data".
<Begasus[m]>
can't boot 32bit on this one, so only 64bit
<OscarL>
so even in a 120 GB SSD, can have 32/64 in both beta/nightly + space for repos.
<Begasus[m]>
almost 43GB in use from 100GB on this "system" partition :)
<Begasus[m]>
but probably need to clean some states to clear up some space
<OscarL>
maybe you could setup 32 bits VMs that access the phisycal partitions (all my VMs do).
<Begasus[m]>
s/clear/clean
<Begasus[m]>
would mean I need to boot into Windows :P
<OscarL>
then you could move that drive to other machines if needed to test 32 bits on bare-metal.
<Begasus[m]>
and tried with VMWare without luck (back when I couldn't boot into Haiku on bare metal)
<OscarL>
(just thinking out loud about possible alternatives :-))
<Begasus[m]>
well, this one doesn't have an "actual" disk to swap :)
<OscarL>
if you only have one drive... say... the internal one on the laptop... only VirtualBox has allowed me to access partitions from the same drive where the host is running.
<OscarL>
with VMware, I can access physical drives, but not the one the host is running.
<PulkoMandy>
Webkit reuses already built files like any other project, but when merging new changes, some header wil be changed and that requires rebuilding everything
CRThaze has joined #haiku
<PulkoMandy>
On my 64bit machine it takes about an hour, on my old 32bit machine from 2014, it needs a day or two :(
<Begasus[m]>
ok, thought so
<OscarL>
read you later, folks. have a pleasant day.
OscarL has quit []
yann64 has joined #haiku
Aedil has joined #haiku
janking has quit [Quit: Vision[]: i've been blurred!]
janking has joined #haiku
janking has quit [Quit: Vision[]: i've been blurred!]
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
BrunoSpr has joined #haiku
janking has joined #haiku
<nekobot>
• threedeyes (dd0bc9c1): tg_owt: bump for rebuild
dpirate has quit [Remote host closed the connection]
BrunoSpr has quit [Quit: Vision[]: Ich wurde eingeweicht!]
neoncortex has quit [Ping timeout: 480 seconds]
neoncortex has joined #haiku
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
nebulabc has quit [Remote host closed the connection]
henesy has joined #haiku
MsInput has quit [Quit: WeeChat 4.6.0]
wolfdog has joined #haiku
leahc has joined #haiku
toasterking has joined #haiku
dominicm has joined #haiku
bmp has joined #haiku
rodolphoeck has joined #haiku
nebulabc has joined #haiku
nephele has joined #haiku
<phschafft>
that feeling when you look at dependency graphs and think: that is a big one, that should have a ton of ... oh wait. only two.
<phschafft>
but that is just that tiny module. it should have like none! *forest of dependencies*
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
<phschafft>
nephele: what is your schedule for the next days?
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
<nephele>
Unavailable friday afternoon till sunday, but available before that
<neoncortex>
say I have a script that filter filenames: how do I open the result in a tracker window?
<neoncortex>
the result will be like /home/whatever/directory
<nephele>
"open /home/whatever/dir/"
<neoncortex>
open, got it. Thanks.
<neoncortex>
this open command can be used as an equivalent of xdg-open?
<neoncortex>
yeah, looks like it.
<nephele>
No. xdg-open only supports a single argument
<nephele>
this open works similar to open on macos, you can provide as many files to it as you want and it will open all of them according to the app set in filetypes
<neoncortex>
I see. Very nice.
<waddlesplash>
neoncortex: why filter filenames in a script, instead of using queries?
MsInput has joined #haiku
AD_Haiku_onPC_ has joined #haiku
<phschafft>
nephele: and next week?
tigerbrother has quit [Quit: Ping timeout (120 seconds)]
AD_Haiku_onPC has quit [Read error: Connection reset by peer]
yann64 has quit [Remote host closed the connection]
Nasina has joined #haiku
Viking667 has joined #haiku
<Viking667>
Good morftervening all.
<gordonjcp>
Viking667: Feasgar mhath
<Viking667>
Tha madainn an seo.
<Viking667>
(I'm assuming that's correct, my Gaelic is practically non-existent)
<Viking667>
Stephan of the libfossil project has managed to get libfossil working with the patches provided by OscarL, so I guess I'll need to stick around here until he gets here. <grin>
neoncortex has quit [Quit: Vision[]: i've been blurred!]
* phschafft
wave sto Viking667.
mmu_man has quit [Ping timeout: 480 seconds]
FreeFull has quit []
<Viking667>
lol. Typos are a rot that have infected this channel.
Habbie has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
<phschafft>
hm...
Nasina has quit [Remote host closed the connection]
Nasina has joined #haiku
Nasina has quit [Ping timeout: 480 seconds]
stephan48 has left #haiku [WeeChat 4.6.0]
Nasina has joined #haiku
Nasina has quit [Remote host closed the connection]
Nasina has joined #haiku
Nasina has quit [Read error: Connection reset by peer]
Nasina has joined #haiku
Nasina has quit [Read error: Connection reset by peer]