<Not-34b6>
[haikuports/haikuports] Begasus 9acf16a - build, new python recipe (#7020)
<Begasus>
thus concludes python week ;)
<andreasdr[m]>
Good morning
<Begasus>
g'morning andreasdr[m]
<andreasdr[m]>
Morning Begasus
<nephele>
Good morning!
<Begasus>
g'afternoon nephele :)
<nephele>
Das BSU hat seine Jahresbericht veröfentlicht Begasus :D
<Begasus>
Was ist BSU? ;)
<nephele>
Bundesamt für Seeunfalluntersuchungen
<nephele>
Ein kleines hobby von mir diese berichte zu lesen
<Begasus>
hehe, hast ja zeit uber jetzt :P
<nephele>
sehr witzig, danke :P
<Begasus>
:P
freddietilley has quit [Quit: WeeChat 3.5]
<Begasus_32>
grabbing libusb_x86-1.0.26-1-x86_gcc2.hpkg and moving it to /Opslag/haikuports/packages/libusb_x86-1.0.26-1-x86_gcc2.hpkg
<Begasus_32>
grabbing libusb_x86_debuginfo-1.0.26-1-x86_gcc2.hpkg and moving it to /Opslag/haikuports/packages/libusb_x86_debuginfo-1.0.26-1-x86_gcc2.hpkg
<Begasus_32>
grabbing libusb_x86_devel-1.0.26-1-x86_gcc2.hpkg and moving it to /Opslag/haikuports/packages/libusb_x86_devel-1.0.26-1-x86_gcc2.hpkg
<Begasus>
k, reverting that upstream stuff works
HaikuUser has joined #haiku
<nephele>
Is there a list for haiku compiler macros somewhere?
HaikuUser has quit [Quit: Vision[]: i've been blurred!]
<nephele>
Begasus: Honestly, I'm just going to not finish the love2d patch for haikuports
<nephele>
instead, i'm going to contribute "proper" Haiku integration to love 12 development
<Begasus>
nephele, how come?
<Begasus>
moving on?
<Begasus_32>
Ran 4 tests
<Begasus_32>
Passed 4 tests
<nephele>
working with haikuporter is too annoying, i'd much rather do this properly upstream and therefore do it once properly
<Begasus>
k, so there is a test case for libusb
<nephele>
haikuporter managed to destroy my patches severall times and i just don't want to deal with it
<Begasus>
upstreaming is always nice if they get merged
<Begasus>
and saves the headache for creating patchsets
<Begasus>
One thing I've noticed using Koder, it's cleaning the whitespaces alo in the patchset, but you can't manualy edit something in there because it will remove the whitespaces and gives you a patchset that can't be used
<nephele>
sure you can
<nephele>
just disable that option
<nephele>
preferences-> trailing whitespace -> trim trailing whitespace on save
<Begasus>
yeah figured it out now, will be for the next time ;)
freddietilley has joined #haiku
<nephele>
hmm, what was the function to get the image my application was started with? to get the executable path
<nephele>
(to not do the wierd "self/proc/exec" thing linux does)
<Begasus>
no idea
HaikuUser has joined #haiku
AD_MOS has joined #haiku
HaikuUser has quit [Ping timeout: 480 seconds]
<nephele>
I think this needs get_image_info, but the first paramater is the image_id, which i guess would be of the calling process for my case, but i don't know how to get the correct value
<Begasus>
looking at the libusb sourcedir I see there is a libusb_haiku.a being build, not sure if it needs to be part of the package?
<Begasus>
it's not installed by default (but some other things aren't also) :P
<Begasus>
biab
HaikuUser has joined #haiku
<HaikuUser>
Hi I am trying to get a webcam working on Haiku so I can record a video. I have 2 webcams the Microsoft Lifecam and a Logitech C920
<HaikuUser>
But I can't either to work
<nephele>
Hi HaikuUser, we do have a webcam usb driver but it is currently unfinished
<HaikuUser>
Ah ok so I guess if I use my standard camcorder for recording my video and then BeScreencapture to capture the desktop that should work once I put it all together in Medo or Openshot
<nephele>
If BeScreenCapture still works that might be viable, I don't know what you are trying to do anyhow :)
<HaikuUser>
I'm reviewing Haiku for my tech channel
HaikuUser has quit [Quit: Vision[0.10.3]: i've been blurred!]
HaikuUser has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<HaikuUser>
Hi unfortunately BeScreenCapture didn't work
<HaikuUser>
Are there any other tools you can reccomend to record the screen?
<Begasus>
BeScreenCapture seems to be OK here on 32bit
<nephele>
x512: by the way, do you know what is still missing for wow64 wine or opengl in wine? maybe I can take a look at it
<x512[m]>
OpenGL support can be added by my recent EGL and glvnd work.
<x512[m]>
I have seen an article describing how to build pure 64 bit WoW64, but I don't remember where I found it.
<x512[m]>
In theory it should be already possible to build Wine WoW64 without host OS 32 bit libraries.
<nephele>
codeweavers macos version does this
<x512[m]>
nephele: Isn't it use special LLVM compiler extensions to generate 32 bit thunks?
<x512[m]>
That approach was rejected by Wine developers.
<nephele>
It still uses 32bit mode of the cpu if you mean that
<nephele>
just not 32bit os libs
<x512[m]>
No, I mean it may use non-regular C code and special C compiler.
<nephele>
anyway, i think FreeBSD ports may be interested in this too, we could ask them aswell? currently FreeBSD ports only has a 64bit only or 32bit only because of packaging difficulties
<nephele>
I don't know about that x512, maybe you mean the same thing, don't know about the specifics codeavers has in their tree
<x512[m]>
I need to find that article how to run WoW without host OS 32 bit libs and custom C compiler.
<nephele>
Would be interested if you find it
<nephele>
I only know about the codweavers article where they outline how they did that for macos
thomaslewis has left #haiku [#haiku]
HaikuUser has joined #haiku
HaikuUser has quit []
Gaspare has joined #haiku
thomaslewis has joined #haiku
thomaslewis has left #haiku [#haiku]
thomaslewis has joined #haiku
thomaslewis has left #haiku [#haiku]
mmu_man has joined #haiku
<trungnt2910[m]>
waddlesplash:
<trungnt2910[m]>
How?
<trungnt2910[m]>
> changing our compiler specs to always include PT_EH_FRAME, then
<waddlesplash>
requires changes in the buildtools repository, and then to update the gcc recipes
<waddlesplash>
how specifically I don't know, you'd have to poke around in GCC specs settings to find out
<waddlesplash>
or I could if you don't know where to start
<x512[m]>
trungnt2910: Did you managed to run and recompile Blackbox?
<trungnt2910[m]>
x512[m]: Didn't have time...
<trungnt2910[m]>
I suddenly found out the problem to the `.eh_frame` section of llvm-libunwind and then spent the last two days building that recipe.
freddietilley has quit [Quit: WeeChat 3.5]
<trungnt2910[m]>
Also, I'm currently on x86_64
mmu_man has quit [Ping timeout: 480 seconds]
<waddlesplash>
now that you've noted EH_FRAME is how this can work without the system using libunwind, this problem makes much more sense
<x512[m]>
GCC recipe build time can be significantly reduced by adding `--disable-bootstrap` configure flag.
<waddlesplash>
this must be how Linux does it I'd guess
<waddlesplash>
x512[m]: what does that do?
x10z has joined #haiku
austin_ has joined #haiku
<x512[m]>
By default GCC builds three times (!). `--disable-bootstrap` makes it build only once, reducing build time 3 times.
x10z has quit []
<waddlesplash>
yeah, but why does it build 3 times?
<waddlesplash>
is it safe to put this in build_cross_tools_gcc4?
<x512[m]>
They want to build GCC with built GCC, not with system GCC.
<waddlesplash>
well ... the whole point of cross builds is that we're building with system gcc
<waddlesplash>
so, this makes sense for haikuports, but not for build_cross_tools
<trungnt2910[m]>
x512[m]: I can't understand the 3. Why not 2?
<x512[m]>
And then third time to ensure that GCC built with GCC works properly.
<trungnt2910[m]>
Ohhhhh...
<waddlesplash>
so, I'd hope build_cross_tools does 1 build only already?
<waddlesplash>
but we should then stick with 3 for haikuports
<trungnt2910[m]>
build_cross_tools is the one that allows compiling Haiku on Linux, right?
<waddlesplash>
more than that, we use it on Haiku itself too
<trungnt2910[m]>
IIRC it still does some sussy things with `xgcc` (the temporary bootstrap compiler?)
<trungnt2910[m]>
<waddlesplash> "now that you've noted EH_FRAME..." <- But even with compiler support for that, how are you going to deal with the old binaries? Bury them in the void?
<waddlesplash>
basically
<waddlesplash>
we should rebuild most of haikuports for the next beta release anyway
mmu_man has joined #haiku
<x512[m]>
Breaking gcc4 binary compatibility is bad idea.
<nekobot>
[haiku/haiku] 06b68f46f961 - kernel/fifo: Add missing check for B_SELECT_READ in Deselect().
<waddlesplash>
x512[m]: it won't break ABI compatibility, it's a feature addition
<waddlesplash>
anything needing EH_FRAME will have to depend on only binaries past a certain rebuild
<waddlesplash>
older binaries will work, just not with e.g. .NET/Mono
<x512[m]>
It will be also nice to enable eh_frame_hdr.
<trungnt2910[m]>
Seems like a clean solution, but will be painful (it's hard to send all old Haiku binaries to the void, what about BeSly and other stuff like that?).
<waddlesplash>
it's not painful, we're not sending those binaries to the void
<waddlesplash>
they just won't be able to be linked to anything needing .NET or the like
<waddlesplash>
I'd imagine 99% of .NET/Mono applications will use system libraries + a handful of things from HaikuPorts
<x512[m]>
We can support both register_frame and eh_frame_hdr and prefer eh_frame_hdr.
<trungnt2910[m]>
painful for libunwind consumers, they can step on a bomb at any time.
<waddlesplash>
the bombs will be pretty infrequent and easily fixed
<waddlesplash>
if we get this in before beta4 there should be relatively few remaining binaries
<waddlesplash>
that .NET would ever link against that don't have EH_FRAME_HDR
<trungnt2910[m]>
When is beta4?
<waddlesplash>
"when it's ready"
<waddlesplash>
probably in a few months or less
<trungnt2910[m]>
The betas are getting faster and faster...
<x512[m]>
I still think that putting libunwind in libroot is good idea.
<trungnt2910[m]>
How're you dealing with gcc2 then?
<waddlesplash>
trungnt2910[m]: huh? we release a beta every year or so
<waddlesplash>
we don't?
<waddlesplash>
gcc2 stays exactly as it is
<waddlesplash>
how would a .NET application ever load a gcc2 binary? it won't, so it doesn't matter
<trungnt2910[m]>
waddlesplash: First beta, 2018 (according to Wiki), I started using Beta1 at 2019.
<trungnt2910[m]>
Alpha is like a decade before.
<x512[m]>
trungnt2910[m]: gcc2 use separate exception handling. And it is already present in libroot.
<waddlesplash>
no, 6 years
<waddlesplash>
alpha4 was 2012
<trungnt2910[m]>
s/at/in/
<waddlesplash>
trungnt2910[m]: yeah, then 2020, 2021 and now hopefully 2022
<x512[m]>
gcc2 links unwind runtime static library into libroot.so.
<waddlesplash>
keep in mind there's a pretty accelerated development pace starting last fall after I was brought on full-time
<waddlesplash>
so there's a ton more stuff for beta3 -> beta4 vs. the previous beta2 -> beta3
<trungnt2910[m]>
And what is "Haiku R1/Beta4.1" lol.
<x512[m]>
trungnt2910[m]: Hotfix?
<trungnt2910[m]>
It appeared on Wikipedia.
MajorBiscuit has joined #haiku
<waddlesplash>
yes, there was a 4.1
<waddlesplash>
there were a few nasty bugs in a4 that made a 4.1 worth the trouble
<waddlesplash>
these days we can just post updates to the beta channel and people can get them using pkgman/SoftwareUpdater
<waddlesplash>
couldn't do that on the alpha :)
<trungnt2910[m]>
But Beta4.1? What?
<waddlesplash>
I don't know, apparently someone made something up
<bbjimmy>
haiku just re-booted while browsing the net.
<bbjimmy>
x86_64 hrev56235
<nephele>
must have been the work of an enemy stand D:
<nephele>
bbjimmy: triple fault?
<bbjimmy>
?
<nephele>
rebooting without kdl
thomaslewis has left #haiku [#haiku]
<bbjimmy>
yes
<nephele>
well, that is quite hard to investigate, can you reproduce it?
<bbjimmy>
what syslog file should I look at? previous_syslog, syslog or syslog,old
<waddlesplash>
I just fixed one recently introduced KDL which I guess could be a triple fault, maybe
<waddlesplash>
or at least I can think of a potential scenario that it could turn into one, though no idea if it really would
<waddlesplash>
see if it still happens with tonight's nightly
<nephele>
syslog won't help for a triple fault
<waddlesplash>
previous_syslog could, though
<bbjimmy>
last entries...
<bbjimmy>
ps2: bad mouse data, trying resync
<bbjimmy>
Last message repeated 2 times.
<bbjimmy>
Last message repeated 2 times.
jmairboeck has joined #haiku
<bbjimmy>
starting the update
<bbjimmy>
but after I need to un-install ftppositive and re-install my local build to have a functioning app. :(
thomaslewis has joined #haiku
bbjimmy has quit [Quit: Vision[]: i've been blurred!]
bbjimmy has joined #haiku
<bbjimmy>
now on hrev56241
thomaslewis has left #haiku [#haiku]
HaikuUser has joined #haiku
HaikuUser is now known as Dio9sys
<Dio9sys>
Howdy howdy
<nephele>
hello
<Dio9sys>
Right now I'm running into a bit of a noob question, if it's ok to ask: I'm messing with the programming examples and trying to edit the fortune file in /boot/system/data/fortunes. When I open the fortunes up in nano though I get the message that the files are read only. I've tried using su to run nano as superuser but can't seem to find the default su credentials.
<nephele>
the default user is already root, the file is read only because it is *really* read only
thomaslewis has joined #haiku
<nephele>
everything installed with packages can't be changed without deinstalling or modifying the package itself, the files are always immutable
<Dio9sys>
ah, good to know
<Dio9sys>
Thanks
<nephele>
you can use /system/non-packaged/data/ instead
<Dio9sys>
oh thanks! I'll try that :)
<nephele>
or ~/config/non-packaged/data
<Dio9sys>
I'm too used to living in linux land where even read-only things can be edited if you try REALLY hard haha
<nephele>
trying really hard is unpacking the package somewhere, editing it, repackaging it :)
<Dio9sys>
fair!
<Dio9sys>
Now I just need to finish getting familiarized with everything and I'll be good to go.
<nephele>
heh, everything might take some time, but feel free to ask questions here if you want to know anything
thomaslewis has left #haiku [#haiku]
<Dio9sys>
I do have one other question, just to make sure I'm not going to go over already trodden ground. Is there a tool for being able to quickly type in the name of a program and have it open? The deskbar is useful but I'd love to be able to quickly type the name of the exact program I want to open instead of navigating the dropdowns
<Dio9sys>
If not, I guess that's my first project :)
<nephele>
I think there are a couple, but if you click on the "Application" menu in deskbar the file manager opens it and it uses type-ahead filtering
<nephele>
I think one app is called quicklaunch?
<waddlesplash>
yes, QuickLaunch
<waddlesplash>
which should really be integrated into Deskbar, there's a ticket about that
<Dio9sys>
Oh good! I'll look into that
<waddlesplash>
well, it's not going to be a trivial task to integrate it
<nephele>
I disagree with integrating it, i don't like it .-.
<waddlesplash>
why not?
<nephele>
I think deskbar should just be improved instead in it's workflow
<nephele>
deskbar should have type ahead filtering instead
<waddlesplash>
pretty much every single OS has this feature
<waddlesplash>
I use it all the time on Windows
<nephele>
Yes, and? having a popup somewhere in the middle of the screen is a bad experience
<waddlesplash>
it shouldn't be a popup in the middle of the screen
<nephele>
I want to open deskbar and immmideintly type
<waddlesplash>
it isn't on Windows
<waddlesplash>
yes...
<nephele>
Yes, "integrating quicklaunch" isn't that
<waddlesplash>
that's what I mean by "integrated"
<waddlesplash>
there's a quicklaunch search box inside the Deskbar menu
<nephele>
it's "adding type ahead filtering to deskbar", i doubt you could reuse much of any code of quicklaunch
<waddlesplash>
you could probably reuse about all of it...?
<Dio9sys>
Yeah, I'd love if deskbar had a search thing with autocomplete and good keyboard support so I could run some shortcut to pull up the dropdown, type what i need and have it all integrated right there
<nephele>
Why? type ahead filtering isn't code specific to quicklaunch, and the rest of the code is UI, which we don't reuse, and a way to search for apps... which we won't reuse because deskbar already does this
<waddlesplash>
QuickLaunch uses queries, this is a neat feature and one we should probably keep
<nephele>
I think quicklaunches implementation is lackluster and hard to use, i don't want this just bolted onto deskbar
<nephele>
let's do it properly instead
<nephele>
And I'd much rather have a curated list of applications in the deskbar, like it is now, with some more automation. Querries lead to the thing tracker already has: listing every application three times on a develop machine if you have haiku compiled somewhere
<nephele>
which would make deskbar even more unusable than it is now
<waddlesplash>
fair enough
<nephele>
(Unless, maybe, we can querry for "inside a package"? or aggressivly filter out duplicates? maybe...)
thomaslewis has joined #haiku
<waddlesplash>
we can query only packagefs, yes
<nephele>
Well, we kind of want to add stuff in ~/config/non-packaged/apps for example too
<nephele>
but this leads to the problem that Querries aren't made for paths, at all
<nephele>
i guess we could use a default whitelist of paths of which deskbar would accept the querry results or so...
austin987 has joined #haiku
<nephele>
Anyway, maybe we should start with moving the folders of apps you want to the top of the deskbar list?
austin_ has quit [Ping timeout: 480 seconds]
Dio9sys is now known as register
register is now known as Dio9sys
<Dio9sys>
ope
thomaslewis has left #haiku [#haiku]
thomaslewis has joined #haiku
Dio9sys has quit [Remote host closed the connection]
thomaslewis has left #haiku [#haiku]
HaikuUser has joined #haiku
HaikuUser is now known as Dio9sys
thomaslewis has joined #haiku
tuaris has quit [Read error: Connection reset by peer]
tuaris has joined #haiku
Vidrep_64 has quit [Quit: Vision[]: i've been blurred!]
thomaslewis has left #haiku [#haiku]
thomaslewis has joined #haiku
<Begasus>
g'night peeps
Begasus has quit [Quit: Leaving]
<nephele>
night begasus
jmairboeck has quit [Quit: Konversation terminated!]
<nekobot>
[haiku/haiku] 19453ce798a7 - freebsd_network: Unlock taskqueues before final destruction.
<nekobot>
[haiku/haiku] 41d93c5ed18f - freebsd_network: Do not deinitialize USB if we never initialized it.
<Dio9sys>
I have somehow managed to break my toolchain without really doing anything
<Dio9sys>
in a weird way, I love this sense of discovery
<waddlesplash>
what happened?
<Dio9sys>
I set up a new project in Paladin, changed the permissions on my projects folder so I can actually edit the files, and now I get this error:
<Dio9sys>
g++: fatal error: cannot execute 'cc1plus': execvp: No such file or directory compilation terminated.
<waddlesplash>
well, see if you actually have a cc1plus
<Dio9sys>
I deleted my Projects file, tried again, still the same error. google indicates an issue with compile flags though I haven't touched those at all
<waddlesplash>
or, possibly you broke PATH
thomaslewis has left #haiku [#haiku]
<Dio9sys>
possible
<Dio9sys>
I'm gonna do a quick reinstall and see if that works. I was playing a lot with system internals before this when I was learning how everything works lol
<Dio9sys>
brb
Dio9sys has quit [Quit: Vision[]: i've been blurred!]
<nephele>
uhh
<nephele>
don't reinstall
<nephele>
you don't really need to do that, like ever
Dio9sys has joined #haiku
<Dio9sys>
back. That seems to have fixed it. I must have either messed up $PATH or accidentally deleted something critical
<Dio9sys>
now to see if changing permissions on one file messes it up again haha
<waddlesplash>
you shouldn't ever need to reinstall
<waddlesplash>
as long as your system boots it's usually easily repaired
<Dio9sys>
Fair. It was just the easiest "kill it with fire" method while I'm still learning the file trees and whatnot
<Dio9sys>
I figure I'll look deeper into it later
<Dio9sys>
Interesting. I changed permissions on exactly one source file in paladin, edited the file to change where it pulls the fortunes from, and that seems to have ruined the PATH variable for paladin as a whole
<waddlesplash>
doesn't make any sense
<waddlesplash>
so, something else is going on
<waddlesplash>
but, I haven't used paladin in ages, so idk
<Dio9sys>
it doesn't make any sense, which is the interesting part
<Dio9sys>
but it also makes no sense that it creates a new project in your home folder and sets everything in it to read-only
<Dio9sys>
so not sure what's up with that
<waddlesplash>
probably it just copies the files directly from the packaged templates where they're RO
<waddlesplash>
and it doesn't update the permissions
Dio9sys has quit [Quit: Vision[0.10.3]: i've been blurred!]
<Dio9sys>
what IDEs do y'all use? I was mostly using paladin because it has built in templates for making haiku apps and I wanted to see how they were structured, but normally I use either vscode or just straight nano
<waddlesplash>
Qt Creator
<waddlesplash>
or yes, vim/nano
augiedoggie_ has quit [Ping timeout: 480 seconds]
augiedoggie has joined #haiku
thomaslewis has left #haiku [#haiku]
HaikuUser has joined #haiku
HaikuUser has quit []
<Dio9sys>
fair enough
Dio9sys has quit [Quit: Vision[0.10.3]: i've been blurred!]
Dio9sys has joined #haiku
thomaslewis has joined #haiku
<waddlesplash>
x512[m]: did you ever determine what the problem was with web browsers on WINE?
<mmu_man>
'yes' as an IDE? :D
thomaslewis has left #haiku [#haiku]
Dio9sys has quit [Quit: Vision[0.10.3]: i've been blurred!]
thomaslewis has joined #haiku
gouchi has quit [Remote host closed the connection]