erysdren has quit [Quit: Konversation terminated!]
tuaris has quit [Quit: Leaving.]
dqk has joined #haiku
dqk_ has quit [Ping timeout: 480 seconds]
* OscarL
removes 10.213 files (52.92 MiB) in... almost 120 seconds (had several stalls of around 1 second each, still better than on beta4)
Oscar-L has joined #haiku
<Skipp_OSX>
there are an unfortunate number of FindPanel related crashes...
OscarL has quit [Ping timeout: 480 seconds]
<Skipp_OSX>
They do seem legitimate and not effected by any of my changes just bugs
Oscar-L is now known as OscarL
<OscarL>
thanks for tackling that "cut/pasted file remains 'ghosted'" bug! (among other) :-)
<OscarL>
"Warning: Found old repository format - repopulating the repository ..." Do not lie to me, HaikuPorter! You did NOT found any repository, old or new (that was the 10K files folder I just nuked)
dcatt has joined #haiku
<Skipp_OSX>
well good because I've requested a style change, ha
<Skipp_OSX>
(to nipos from earlier)
<oanderso[m]>
waddlesplash: Can you link the instructions or the hacks I need to try it?
<oanderso[m]>
Or did I miss those somewhere upthread?
<waddlesplash>
oanderso[m]: mkdir generated.arm64.clang (or whatever you want to call it); cd generated..; ../configure --use-clang arm64
<waddlesplash>
if "clang" isn't in your PATH it will ask you about what to use, you will likely need to specify it with HAIKU_clang_arm64=clang... environ
<waddlesplash>
same for HAIKU_ld_arm64=lld and probably also elfedit. if you have llvm-ar etc. in PATH it'll find it
<oanderso[m]>
Cool, maybe I'll give it a try when I get frustrated with page tables :-)
<waddlesplash>
then just build as normal. The hack for CreateAsmStructOffsetsHeader1 shouldn't be needed, but I'm not sure what's different between Clang and GCC asm output formats here
<waddlesplash>
I just needed to change the sed from 's/@define/#define/g' to 's/\/\/define/#define/g'
<waddlesplash>
you'll probably also hit the kernel link error but I trust you'll be able to investigate that one yourself
<waddlesplash>
oanderso[m]: sounds good. thanks again for working on ARM64 support! :)
<oanderso[m]>
No problem. I'll be offline for a week or so starting on Wednesday, but I'll try to get back to it when I'm back
<oanderso[m]>
Hoping to get a lot of the MMU fixes parted out and landed by then
<oanderso[m]>
Is 8102 ready to land?
<oanderso[m]>
(Trying to reduce my git stack)
<waddlesplash>
looks like it to me, but these less-trivial changes I'd prefer get +2'd by one of the more knowledgeable ARM folks than myself before merging
<waddlesplash>
if nobody comes along and comments, I'll merge in a few days
<oanderso[m]>
Sounds good
<waddlesplash>
ah, I didn't add them to reviewers, they might've missed these
<waddlesplash>
will add them
smalltalkman__ has quit []
Coldfirex has quit [Remote host closed the connection]
dcatt has quit [Quit: Vision[]: i've been blurred!]
<botifico>
[haikuports/haikuports] pulkomandy 1288536 - mutt: update to openssl 3
<botifico>
[haikuports/haikuports] pulkomandy 5c9ad4c - trojita: update to openssl 3
<botifico>
[haikuports/haikuports] pulkomandy 552daf4 - tg_owt: update to openssl 3
<botifico>
[haikuports/haikuports] ... and 3 more commits.
<x512[m]>
oanderso: llvm-ar for creating static libraries, no?
<oanderso[m]>
There's no particular reason to use it unless you're doing old-fashioned "fat" LTO builds
<nipos>
Begasus: Dark mode for the buildmaster website should be ready, I think. The buildmaster page was easy to understand. The logviewer has some color definitions that seem never used (checked many logs, also from years ago) so I ignored them and only changed the default colors that are always in use.
<x512[m]>
Also not sure, but binutils ar may not support cross compilation.
<oanderso[m]>
It does within ELF systems
<oanderso[m]>
ar isn't very smart
<oanderso[m]>
It's basically an old version of tar. The only smart feature is that it can create a symbol table file within the archive by reading the symbol tables of the contained objects and concatenating them
<oanderso[m]>
Hence the special feature of llvm-ar: it knows how to read the symbol tables of bitcode files
<oanderso[m]>
Anyways, it's a little weird to require a pure LLVM stack
<oanderso[m]>
LLVM/clang are purposefully built to be able to interoperate with the GNU stack as much as possible
<x512[m]>
Haiku may move to LLVM stack in future to get rid of GPL components etc..
<oanderso[m]>
No objections from me :-)
<x512[m]>
Process of building GCC/Binutils is a pain. There is still unresolved problem of broken exceptions when cross-compiling stdc++ in haikuports.cross repo.
<oanderso[m]>
x512: I'd prefer if you could do it if you're setup to test it. Here's the sample code to find the assembly sequence to get the address PC-relative: https://godbolt.org/z/sazvj846z
<oanderso[m]>
Interestingly, clang outputs something different
<x512[m]>
oanderso: Do you have an idea what "-static" flag should do on Haiku where fully static executables are not supported? What it do on Windows/MinGW? Is it good idea to just ignore it?
DKnoto_W has joined #haiku
<phschafft>
Good morning. :)
DKnoto_W2 has quit [Ping timeout: 480 seconds]
yann64 has joined #haiku
yann64 has quit [Quit: yann64]
yann64 has joined #haiku
<phschafft>
Hm, there really is no /dev/stdout.
<phschafft>
would have thought that would have broken one of the ports way earlier.
<phschafft>
it's also not part of POSIX.
<phschafft>
oanderso[m]: not into python, but generally speaking the handle is already open, so you can maybe just use that.
<oanderso[m]>
x512: On Darwin (which has the same issue) it just fails with because there is no crt0.o present
<botifico>
[haikuports/haikuports] Begasus a6b70b7 - qt6_charts, revbump for openssl3 (#10883)
<waddlesplash>
oanderso[m]: I also got that herror error on x86, I just commented out the weak_alias and that fixed it. but it's weird because we use lots of weak_alias around libroot & libnetwork and they work fine, not sure what the difference is with that one
<waddlesplash>
oanderso[m]: I think I did experiment with LTO at some point, but it just seems to make sense to use llvm tools instead of host tools in general?
<jmairboeck>
because it just repackages a python wheel, there are no sources
<jmairboeck>
this is needed as dependency for other packages, otherwise we wouldn't even need a recipe for it
<jmairboeck>
and also, technically the sources are available in the package itself as the .py files
<nipos>
Begasus: The colors for active, finished, failed,... are all slightly different. I used the same sort of color as in the light mode for each type, but a darker one. You can't see it in the screenshot because there is only active, but I tested it by editing the HTML classes in Inspect Element
<nipos>
If you want the new design to go into production, that's your turn now. I linked to the new CSS files on my server. I won't touch M$ Github.
<Begasus>
I'll take your word for it nipos :)
<Begasus>
I have no clue on how those repos for the website(s) are setup
<Begasus>
or where to find them
<nipos>
You can try it by opening Inspect Element on the Buildmaster page and edit the HTML link tag to point to my server's CSS file instead of the relative path on Haikus server
<botifico>
[haikuports/haikuports] jmairboeck ddbda0c - pytest_datafiles: new python recipe
zardshard has left #haiku [Error from remote client]
zardshard has joined #haiku
HaikuUser has joined #haiku
HaikuUser has quit []
<dovsienko>
maybe it is because yesterday's weather is much easier to forecast
<phschafft>
haha.
<PetePete>
dovsienko *palmface*
zardshard has left #haiku [Error from remote client]
zardshard has joined #haiku
HaikuUser has joined #haiku
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
_-Caleb-_ has left #haiku [#haiku]
HaikuUser has quit [Read error: Connection reset by peer]
_-Caleb-_ has joined #haiku
<nipos>
Skipp_OSX: Thanks for looking at my code. Please don't merge the Keymap one yet, however. I'm currently reworking it to use tint or mix_color instead of hardcoded dark color constants.
<botifico>
[haikuports/haikuports] Begasus 28a5df5 - qt6_positioning, revbump for openssl3 (#10890)
<PetePete>
Any way to get additional themes?
<nipos>
There's a flat theme and a original BeOS theme in the source tree, but I can't enable them in appearance. Probably they're not built by default?
<Skipp_OSX>
you have to install the Haiku-Extras package to get the extra decorators/control looks
<waddlesplash>
the physical map already exists of course, but it isn't tracked before that
<waddlesplash>
you can actually allocate arbitrary memory before post_area() though, you have to use vm_allocate_early_page(), and then you have to create an area for the pages you allocated once post_area() is called
<oanderso[m]>
I only need 256 bits 😂
<waddlesplash>
yes, but I'm just mentioning in case it's useful otherwise :)
<waddlesplash>
there are more things that can be done in early boot besides just placement new of static arrays