vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
SwagatSBhuyan[m] has joined #haiku
rando25892 has quit [Quit: off for now]
DKnoto has quit [Ping timeout: 480 seconds]
DKnoto has joined #haiku
WishBoy has quit []
vdamewood has joined #haiku
bitigchi has joined #haiku
rando25892 has joined #haiku
Maturion has joined #haiku
<jt15s[m]>
Erm, PulkoMandy, not sure what's going on but the October activity report isn't showing up on the website :(
bitigchi has quit [Ping timeout: 480 seconds]
rennj has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
bitigchi has joined #haiku
mmu_man has joined #haiku
maquak has joined #haiku
<maquak>
Good morning! My build is failing with this: `Error while writing to file `/myfs/system/packages/noto_sans_cjk_jp-1.004-2-any.hpkg': No space left on device` - any clues why it happens? df shows I have 40GiB of free space in /
<Diver>
you need to increase image size
<maquak>
In UserBuildConfig? I don't have my config, so it should work for default image anyway, no?
AlaskanEmily has quit [Remote host closed the connection]
bitigchi has quit [Ping timeout: 480 seconds]
<jessicah>
maquak: if you've been doing a lot of builds, then try rm -rf attributes in the generated dir
<jessicah>
I ran out of inodes because of that
<jessicah>
I still had space, but had that error too
Maturion has quit [Ping timeout: 480 seconds]
<maquak>
I removed whole generated (and all non-repo files with git clean -xdf) and still the same :( I installed a bunch of software recently, I'll see if booting old state helps
maquak has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
maquak has joined #haiku
maquak has quit []
bitigchi has joined #haiku
maquak has joined #haiku
<maquak>
Booting old state doesn't help :/ @jessicah how did you find out that you're out of inodes? Maybe I have too many files, but somewhere outside of build directory?
<jessicah>
oh this was on Linux, not Haiku
<jessicah>
I don't know about Haiku
bitigchi has quit [Ping timeout: 480 seconds]
jesse_blue has joined #haiku
countryboy has joined #haiku
jesse_blue has quit [Remote host closed the connection]
HaikuUser has joined #haiku
HaikuUser is now known as mrentropyvcs
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<countryboy>
about gambas : not save files in hidden dirs => put them in a normal directory ... ;-)
<kallisti5[m]>
powerpc is is in maintenance mode for the moment
<kallisti5[m]>
aka... i'm doing the bare minimum to keep it compiling :-)
<kallisti5[m]>
There's not a lot of interest since the old hardware is getting less useful and wearing out, and there is no new hardware on the horizon.
<countryboy>
and changing name to gambas ... freedom ;-)
maquak has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
<mmu_man>
I had a working patch at some point but never submitted it
<mmu_man>
for gambas
B2IA has quit [Ping timeout: 480 seconds]
<ilzu[m]>
Kallisti5 I dont think it compiles right now, I tried out of curiousity few days ago when I found my old iBook. The bootloader complained of missing zstd.h. I think it needs zstd bootstrapping package, I tried to make one, but failed and haven't had time to play with it since.
<kallisti5[m]>
I fixed that a few days ago. Made zstd optional
<kallisti5[m]>
eventually we will need a zstd package for ppc, but the build no longer fails for now
<ilzu[m]>
Ah, maybe I'll try again then.
phaedros_ has joined #haiku
<countryboy>
thank you mmu_man ;-)
<Not-5726>
[haiku/website-inc] waddlesplash pushed 1 commit to master [+0/-0/±1] https://git.io/JPQkf
<pch>
and nobody wants to get in on it because everyone's cushy with intel at its perf level
<pch>
that is a motherboard that takes the HPC cpu developed by IBM and puts it in a desktop format
<nephele>
4Core ~3-4Ghz doesn't really scream supercomputer to me
<pch>
each of those cores have SMT4 as a minimum
<pch>
usually SMT8
<pch>
so 4 cores is 16 threads for the smallest you can get, and these processors are made for absolutely massive SIMD stuff
<nephele>
16 threads is still sometwhat mid to high end of desktop systems nowadays, so while you are certainly correct that the main target is supercomputers, i don't think it's acurate to say it isn't for anything less powerfull than one :)
<pch>
do you know much about how a CPU actually works? GHz means nothing across different platforms
<pch>
it's only a measurement for in-platform things
<nephele>
I know that, It still makes no sense to call a desktop computer formfactor a supercomputer to me, that it is in a desktop format prooves that it can work in that formfactor just aswell, those clearly aren't inteded for typical supercomputer workloads
<pch>
the clockrate of a core is read as the rate of the timerclock it acts to, but the cpu can perform many more actions than the clock can spit out timing pulses
<pch>
the cores are made for supercomputers, and the desktop formfactor motherboards provided by raptor are for compact massive compute (for CAD scenarios and similar)
<nephele>
I'd expect they are also to develop stuff to run on those supercomputers aswell?
<pch>
the performance (and power draw) is much, much more than modern "desktop specification"
<pch>
yeah
<nephele>
Yes, that is certainly true... though developer workstations are usually pretty ridicilous (or expected to be)
<pch>
I want back the days where POWER is a consumer architecture, since it's amazing for desktop-style compute
<nephele>
The only power computer I own is the Wii ;), sadly it doesn't quite fit the bill for running haiku on it
<pch>
x86 was really designed for dispatch to more powerful coprocessors, and the system architecture of x86-pc makes it very obvious
<pch>
we're in a day where CPUs as primary compute devices is just the norm, yet we're stuck to x86-pc which requires working around to make appropriate devices for this
<pch>
and the wii is just a gamecube, which was a 2001 midrange for PPC, and still much faster than its competitors (ps2 pushing MIPS to its max, xbox pulling out everything on x86)
<nephele>
It would certainly be fast enough to run Haiku, but the RAM requirements of Haiku, as they are currently, are too much for the Wii (It has like 64MB of onboard ram, and then some more accesible via other means; while the haiku requirement is currently somethin like 364~mb (though that could probably be decreased, just don't know if it can be decreased to compfortably run on the Wii)
<nephele>
)
<pch>
yeah, I want a modern POWER revival
tqh has joined #haiku
<pch>
either that or a similarly-good or better HPC arch to come into vogue
<nephele>
The Wii U however has 2GB of ram, it could probably run Haiku
<pch>
ARM is getting close to HPC, but mainly in massively-parallel non-SIMD applications
<pch>
would love haiku on a wii u, wii u is like the newest POWER-based consumer device
<pch>
and it's got 3 cores! how wonderful
bbjimmy has joined #haiku
<nephele>
I think I'll try that eventually, sounds like a funky project, and would teach me about arch bringup
bitigchi has joined #haiku
maquak has joined #haiku
<maquak>
Does anyone runs just "jam" in main haiku repo? What would you expect it do to?
<waddlesplash>
just "jam"? that sounds wrong
<waddlesplash>
you generally pass -q and a profile at least, if not also -j
<waddlesplash>
"@minimum-raw" or "@nightly-raw" is probably what you want
<waddlesplash>
but more often if you are working on just one thing you also pass that
<maquak>
I encountered this problem in the morning: https://discuss.haiku-os.org/t/issue-building-haiku/10284/6 and I got it when running "jam" without profile specified. I was running it like so for some time now and it worked (until today). I suppose I had some build config set up which I accidentally deleted and it stopped building.
<nephele>
maquak: only if i am in a specific subdirectory, to build only that specific component
countryboy has joined #haiku
<maquak>
I would modify build scripts to bail out early if profile is not set, wdyt?
<nephele>
if you don't configure a build profile you get nasty stuff like builds without TLS support and such (Transport layer security, not the thread stuff)
<nephele>
maquak: could be, or we could question why non-TLS builds is even a thing ;)
<waddlesplash>
maquak: well, I think profile-less builds are OK if you have a Userbuildconfig
<waddlesplash>
but otherwise it should be disallowed, yeah
<countryboy>
bewake => inTheWake ...
WishBoy has quit []
gouchi has joined #haiku
x10z has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
maquak has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
B2IA has joined #haiku
bitigchi_ has joined #haiku
bitigchi has quit [Read error: No route to host]
bitigchi_ has quit [Remote host closed the connection]
bitigchi has joined #haiku
<Not-5726>
[haikuports/haikuports.cross] pulkomandy pushed 1 commit to master [+0/-0/±1] https://git.io/JPQ9A
<Not-5726>
[haikuports/haikuports.cross] davidkaroly 35dc313 - icu: add arm to 67.1
MrSunshine_ has joined #haiku
Skipp_OSX has joined #haiku
MrSunshine has quit [Ping timeout: 480 seconds]
beaglejoe has quit [Quit: Leaving]
MrSun has joined #haiku
<Not-5726>
[haikuports/haikuports] pulkomandy pushed 1 commit to master [+0/-0/±1] https://git.io/JPQbk
<Not-5726>
[haikuports/haikuports] davidkaroly a3a6b44 - gcc: enable build for arm
MrSunshine_ has quit [Ping timeout: 480 seconds]
<nephele>
Huh... My web interface stopped working for my synology drive because it thought the connection was still open, it showed 92H as uptime for the connection, I most certainly had my haiku desktop completely off severall times during that, i guess this is just a bug in the server :g
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
MrSun has quit [Ping timeout: 480 seconds]
BrunoSpr has quit [Quit: Vision[]: Ich wurde verwaschen!]
BrunoSpr has joined #haiku
BrunoSpr has quit []
olhado22 has joined #haiku
ClaudioM has quit [Quit: leaving]
MrSun has joined #haiku
Maturion has joined #haiku
jesse_blue has quit [Remote host closed the connection]
MrSunshine_ has quit [Ping timeout: 480 seconds]
MrSunshine_ has joined #haiku
<Skipp_OSX>
better you say?
<Skipp_OSX>
well that's why I am trying to improve Haiku
BrunoSpr has joined #haiku
MrSunshine has joined #haiku
BrunoSpr has quit []
MrSun has quit [Ping timeout: 480 seconds]
MrSunshine_ has quit [Ping timeout: 480 seconds]
countryboy has quit [Quit: countryboy]
x10z has joined #haiku
<Skipp_OSX>
speaking of which I gotta figure out what's going on with icon attributes in Tracker not working correctly... it should work exactly like before unless the file is an image type
<Skipp_OSX>
Last minute change was to try and see if there is a translator before I check if file is an image type... I knew that might cause problems
dforde has joined #haiku
dforde has quit []
dforde has joined #haiku
dforde has quit []
gouchi has quit [Remote host closed the connection]
dforde has joined #haiku
<waddlesplash>
yeah, that probably is it
beaglejoe has joined #haiku
dforde has quit []
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
gouchi has joined #haiku
Dusan_Krehel has joined #haiku
Dusan_Krehel has quit []
nhtello has quit [Quit: Vision[]: i've been blurred!]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
HaikuUser has joined #haiku
HaikuUser has quit []
x10z has joined #haiku
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
tqh has quit [Quit: Leaving]
B2IA has joined #haiku
tqh has joined #haiku
<B2IA>
(Butler) Welcome to BeShare.agmsmith.ca.
gouchi has quit [Ping timeout: 480 seconds]
gouchi has joined #haiku
<B2IA>
(Butler) Welcome to BeShare.agmsmith.ca.
B2IA has quit [Quit: Vision[0.10.3]: i've been blurred!]
<waddlesplash>
though maybe not, it could be a stack issue that I fixed
<Vidrep_64>
I'm still getting errors when attempting to build HaikuWebKit
<waddlesplash>
are you on gcc11
<Vidrep_64>
Probably a known issue, since neither HaikuWebKit nor WebPositive have been updated in the repositories yet
<Vidrep_64>
I am
<waddlesplash>
error log?
<Vidrep_64>
Here's a few lines of spam:
<Vidrep_64>
/boot/home/haikuwebkit/Source/WTF/wtf/Compiler.h:103:2: error: #error "Building release without compiler optimizations: WebKit will be slow. Set -DRELEASE_WITHOUT_OPTIMIZATIONS if this is intended."
<Vidrep_64>
103 | #error "Building release without compiler optimizations: WebKit will be slow. Set -DRELEASE_WITHOUT_OPTIMIZATIONS if this is intended."
<Vidrep_64>
| ^~~~~
<Vidrep_64>
[765/4207] Building CXX object Source/...ources/UnifiedSource-bfc896e1-16.cpp.o
<Vidrep_64>
I see that same error message repeated several times throughout the build log
<Vidrep_64>
Welcome to the Haiku shell.
<Vidrep_64>
<Vidrep_64>
~> gcc --version
<Vidrep_64>
gcc (2021_04_27) 11.1.0
<Vidrep_64>
Copyright (C) 2021 Free Software Foundation, Inc.
<Vidrep_64>
This is free software; see the source for copying conditions. There is NO
<Vidrep_64>
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
<waddlesplash>
you did not pass the right things to CMake probably
<waddlesplash>
I can't remember precisely what needs to be passed, nephele likely does
<Vidrep_64>
I just run the script as I always have done before
<Vidrep_64>
"build-webkit --haiku"
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<waddlesplash>
yeah, but it needs some new arguments now, it seems.
<waddlesplash>
Vidrep_64: anyway, in a day or two I am going to have a test version of the new NTFS driver ready
<waddlesplash>
I imagine you may be interested in that
<Vidrep_64>
Lately NTFS has been behaving. However, I have not tried to write any large files, which is usually when I get really slow write speeds. Trying to delete a file usually results in a crash.
<waddlesplash>
indeed, the new driver should fix all those problems
<waddlesplash>
or at least "some" of them
<Vidrep_64>
Any improvement is welcome :)
<waddlesplash>
I finished read support already and it is indeed *much* faster; write support is about halfway
<Vidrep_64>
It looks like you're following your plan as you explained it to me at the beginning of your contract
<waddlesplash>
yep: USB issues (all KDLs now resolved, a lot of other instabilities resolved), now NTFS
<waddlesplash>
lots of other stuff in the middle there, too, but that's the big stuff so far
<Vidrep_64>
I don't think you'll run out of things to fix any time soon
x10z has joined #haiku
<Vidrep_64>
That's it for me today.
<Vidrep_64>
gn
Vidrep_64 has quit [Quit: Vision[]: i've been blurred!]