<Not-d5e4>
[haikuports/haikuports] threedeyes 337a2a1 - qthaikuplugins: bump version
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
gouchi has joined #haiku
gouchi has quit []
HaikuUser has joined #haiku
HaikuUser has quit []
diver1 has joined #haiku
Diver is now known as Guest813
diver1 is now known as Diver
Begas_ has joined #haiku
Guest813 has quit [Ping timeout: 480 seconds]
<Begasus>
jmairboeck, if you read the logs .. this is the error I get when building texlive (INSTALL part) ... mv: cannot stat '/packages/texlive-2022-1/.self/data/texlive/texmf-dist/fonts/tfm/zhmetrics/uniyou/uniyousl2d.tfm': No such file or directory
<Begasus>
Don't ask me to many times to run the install part ;) (takes half a day) :P
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
Begas_ has quit [Quit: Vision[]: Gone to the dogs!]
<Anarchos>
Begasus i should try...
selfish- has joined #haiku
selfish has quit [Read error: Connection reset by peer]
parodper has left #haiku [#haiku]
floof58 has joined #haiku
frkzoid has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<Begasus>
You know how it works Anarchos ;)
<Begasus>
PS, this was/is on 32bit here
<ermo[m]>
Just set up an €5/month donation for the Haiku foundation. Here's hoping it'll make some small difference. Out of curiosity, who handles donations?
<ermo[m]>
ah, leavengood
<ermo[m]>
And it's even a non-profit. Nice.
x10z has joined #haiku
frkazoid333 has quit [Ping timeout: 480 seconds]
freddietilley has quit [Quit: WeeChat 3.5]
floof58 has quit [Quit: floof58]
floof58 has joined #haiku
eroux has joined #haiku
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mmu_man has joined #haiku
Babaj has joined #haiku
<Anarchos>
Begasus yes
<Anarchos>
hello mmu_man
Babaj has quit [Quit: Leaving]
_Dario_ has joined #haiku
<Anarchos>
Why g++ suggests me to replace a local variable by 'sin' ?? --> App.cpp:76:36: error: 'sig' was not declared in this scope; did you mean 'sin'? 76 | Signature *sig = cast_as(Signature::Instantiate(&message), Signature);
<ermo[m]>
Anarchos: because sin is a math function that g++ knows and has a levenshtein distance of 1?
<Anarchos>
ermo[m] that i guess, but why doesn't it understand it is a local var declaration ?
<ermo[m]>
no idea
<Anarchos>
the class Signature is defined it Signature.h, which is included.
* ermo[m]
needs to get his haiku hardware situation sorted
<Anarchos>
maybe i should compile with '-save-temps'
<ermo[m]>
any rough compile time estimates for the entire haiku os nightly image with a hexacore ph II 1090T?
<ermo[m]>
vs. Ph II 955BE?
* ermo[m]
assumes most people here use more modern hardware with haiku
<Anarchos>
ermo[m] i have a pentium 4 and a compaq from 2000 if i want to test
<Anarchos>
the pentium 4 is able to boot on PXE, not sure for the compaq
<ermo[m]>
I got rid of the (working) p4 I had sadly. 2 GiB of RAM! Wild!
<Anarchos>
oh my ubuntu server has a whole 768Mb :)
<ermo[m]>
Currently using a Q9400 w/4 GiB of DDR3-1600 running at DDR3-1400 speeds (chipset limitation)
<ermo[m]>
for Haiku I mean. Is that enough for compilation without it taking days to complete?
<Anarchos>
sure
<Anarchos>
my core i3 takes 20min to compile, maybe less
<ermo[m]>
so it should take an hour or so for me basically
<ermo[m]>
(with the Q9400)
<Anarchos>
ermo[m] anyway it take 8hours on my AMD C50 if i compile the toolchain, 1 or 2hours without.
<ermo[m]>
C50? That's a 1GHz dual core APU ... right?
<Anarchos>
right
<Anarchos>
ermo[m] i am on it right now
<ermo[m]>
so assuming identical scaling, that'd be 4 hours (for double the cores) and then a speed jump of ~3x from core speed, so 1hr20m for me including toolchain (assuming that i/o scaling is linear)
<ermo[m]>
which it might not be
<ermo[m]>
I can compile nightly from within Haiku, right?
<Anarchos>
right
* ermo[m]
begins checks out the build documentation
<ermo[m]>
*checking
<Anarchos>
i always compile it from haiku
<ermo[m]>
Nice. `shutdown -r` works in an ssh session.
<ermo[m]>
and the keychain port works flawlessly. What a lovely surprise.
Anarchos has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Ping timeout: 480 seconds]
mmu_man has quit [Ping timeout: 480 seconds]
tuaris has joined #haiku
Anarchos has joined #haiku
<Anarchos>
ermo[m] sorry, haiku crashed
<ermo[m]>
=)
<ermo[m]>
I'm just getting stuff cloned on my end
<Anarchos>
git clone ?
<ermo[m]>
yerp
<ermo[m]>
used `git clone --depth=1 --recurse-submodules --shallow-submodules <repo>`
<ermo[m]>
just to get started quickly
<ermo[m]>
just a quick note: I don't need to compile the custom Haiku jam version if I build from Haiku, right?
<ermo[m]>
(I assume that's only necessary when cross-compiling from non-Haiku OS hosts?)
<ermo[m]>
Jam 2.5-haiku-20111222. OS=HAIKU. Copyright 1993-2002 Christopher Seiwald. <- output of `jam -v` on my haiku box
<Anarchos>
ermo[m] right no need to recompile jam
bbjimmy has joined #haiku
* ermo[m]
wonders how to get the buildtools ./configure script to accept CFLAGS and CXXFLAGS of "-march=native"
<ermo[m]>
specifying on the cmdline as env vars didn't appear to take..
Babaj has joined #haiku
<Anarchos>
no need to do that
<Anarchos>
just do "./configure" and that's it !
jmairboeck has joined #haiku
<jmairboeck>
Begasus, good evening! In which section of the build does the error occur? Do you have a complete build log or some more context?
<ermo[m]>
Anarchos: IME, -march=native everywhere increases perf 5-10% over x86_64 baseline, which is why I'd want it in the tooling too if possible (shortening compile times by 5-10% is significant if we're talking 80 -> 70 minutes for instance)
<ermo[m]>
but I'll figure it out
<Anarchos>
ermo[m] no idea on how to achieve that configuration
<jmairboeck>
ermo[m]: you can probably add that somewhere in build/scripts/build_cross_tools_gcc4 in the haiku repo
ablyss has quit [Quit: Leaving]
<ermo[m]>
jmairboeck: oooh, that looks promising
* ermo[m]
checks
Babaj has quit [Quit: Leaving]
<ermo[m]>
jmairboeck: is the build_cross_tools_gcc4 script the "everything > gcc2" build script for the toolchain?
<jmairboeck>
yes, I think so
<ermo[m]>
there should be a note saying this in the header ...
* ermo[m]
adds task to his build-notes.txt document
aakashi2001 has joined #haiku
Begasus_32 has quit [Quit: Vision[]: i've been blurred!]
<Begasus>
jmairboeck, I think about after creating the debug packages, closed the other laptop down earlier
<Begasus>
Heading down here, in an hour visit to the clinic
<Begasus>
cu peeps!
Begasus has quit [Quit: Leaving]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Anarchos has quit [Quit: Vision[]: i've been blurred!]
<AlienSoldier>
then google will ahve to shutdown gmail because nobody will use it anymore
<ermo[m]>
jmairboeck: your suggestion appears to be a good one -- toolchain is compiling with the manually added flags in `build/scripts/build_cross_tools_gcc4` in the `haiku/` repo
<waddlesplash>
AlienSoldier: this only matters if your data goes through third party servers.
<waddlesplash>
it shouldn't affect pegasus mail at all.
<AlienSoldier>
i hope so
<ermo[m]>
say ... why does the toolchain compilation appear to be single-threaded rather than attempting to use all my cores?
<waddlesplash>
you have to specify -j to ./configure
<waddlesplash>
if you want multijob toolchain builds
<ermo[m]>
that's ... interesting (and not documented)
<waddlesplash>
mm, pretty sure it is?
<waddlesplash>
it's definitely in ./configure --help
<ermo[m]>
or, well, I didn't run './configure --help'
<ermo[m]>
waddlesplash: but thanks for the hint in any case (even if I should have caught it myself).
<waddlesplash>
np
<ermo[m]>
compiling on haiku is cool -- I'm impressed at how responsive the system appears to remain
<nephele>
-j <cores> is a quite common thing in build systems
<ermo[m]>
like, the gui is as snappy as ever even under heavy load. Nice.
<ermo[m]>
nephele: yes, I just found it odd to see it used with ./configure
<nephele>
normally configure does not build anything
<ermo[m]>
I typically see it used with make/cmake/ninja/waf/etc.
<ermo[m]>
that was kinda my point =)
<waddlesplash>
ermo[m]: "snappy even under heavy load": yes, imagine that! what a concept!
<waddlesplash>
Linux has really ruined everyone's expectations here, it's such a disaster
<nephele>
almost like the scheduler makes decisions based to that end...
<ermo[m]>
The only thing close to it that I've experienced is FreeBSD
<ermo[m]>
which performs nicely under heavy load and memory pressure
<nephele>
FreeBSD is very nice too, for a desktop system you have to turn a lot of knobs though :(
<ermo[m]>
where loonix can go "nope, don't want to talk to you right now, I'm busy with this _really important thing_"
<ermo[m]>
and you're like "well, yes, you're writing an image to an USB disk, but ... really?"
<nephele>
ermo: maybe its time to upgrade to $(current_cores *2) cpu system
<ermo[m]>
and then the workaround is "sudo nice -n19 ionice -c3 dd (...)" because CFS and whatever else the schedulers are named are, in a word, braindead in terms of user expectations of interactivity
<ermo[m]>
for reference, -c3 to ionice is "idle priority I/O"
<nephele>
There is a kernel called "liquorix" that includes all the "desktop" scheduling stuff and patchsets like muqss, with that linux on the desktop is almost bearable for responsiveness
<nephele>
of course this doesn't eliminate the input latency user space adds in many places...
<ermo[m]>
Yeah, I used muqss on the CPU I'm currently using for Haiku (in the Linux 4.19 days)
<ermo[m]>
that was very nice actually
<ermo[m]>
that and BFQ for I/O IIRC
<ermo[m]>
sure, it was slower under load (duh), but things still felt smooth
<nephele>
(Quite happy Haiku does /not/ have a compositor running all the time... If this is absolutely required for the uhm 3d accel I hope it will only have to run while the 3d accell is running, dont want to loose this low input latency (though we can probably go a bit lower in places)
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
x10z has joined #haiku
<ermo[m]>
is haiku/build/jam/ArchitectureRules the correct place to add -march=native for the haiku build itself?
<ermo[m]>
or am I supposed to add it somewhere else if I want it?
Vidrep_64 has joined #haiku
lorglas has joined #haiku
<nephele>
you don't need to add that
<nephele>
The code is supposed to, if it is possible to use newer cpu features, build two versions, with one beeing used if needed. So it will run on the older cpu fine but run faster on the newer one. IIRC
<Vidrep_64>
Hi nephele
<nephele>
Hi Vidrep_64
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ermo[m]>
Ah. UserBuildConfig is my friend. There's even a UserBuildConfig.readme. Nice.
lorglas has quit [Quit: Vision[]: i've been blurred!]
<ermo[m]>
note to self, don't add '-g' when building haiku as it breaks the floppy size (used for the anyboot iso?)
jmairboeck has quit [Quit: Konversation terminated!]
Atomozero has joined #haiku
<waddlesplash>
yes
<waddlesplash>
use SetConfigVar DEBUG on specific directories
<waddlesplash>
see UserBuildConfig example/readme
HaikuUser has joined #haiku
HaikuUser has quit []
Atomozero has quit []
mmu_man has joined #haiku
<ermo[m]>
ack
<ermo[m]>
waddlesplash: I've been trying to use the jam '-d' flag to show more compilation info -- do you happen to know which invocation I need to use to see output equivalent to e.g. make?
<ermo[m]>
(with VERBOSE=1)
<ermo[m]>
i.e. CFLAGS etc.
<ermo[m]>
or just full cmdline cc invocation really
<waddlesplash>
it's one of the -d I'm pretty sure
<waddlesplash>
what are you trying to do?
<ermo[m]>
I would like to see if my UserBuildConfig additions have "taken" (-march=native)
<ermo[m]>
I've set CCFLAGS and C++FLAGS there
<waddlesplash>
that won't work, probably
<waddlesplash>
they can only be set per-directory
<ermo[m]>
hrm
<waddlesplash>
the global values are HAIKU_CCFLAGS_$(architecture)
<waddlesplash>
check your generated/build/BuildConfig for the exact variable names in use
<ermo[m]>
ah, cheers, that's useful!
<ermo[m]>
I remember fiddling with gcc graphite loop optimisations a couple of years ago
<ermo[m]>
(was reminded by it because BuildConfig has that option set to 0)
jason123onirc has quit [Ping timeout: 480 seconds]
<ermo[m]>
waddlesplash: looks like command output is shown with -dx
jason123onirc has joined #haiku
<ermo[m]>
waddlesplash: ok, so adding CCFLAGS to 'haiku/build/jam/UserBuildConfig' seems to take (according to 'jam -q -dx @nightly-anyboot')
<ermo[m]>
but the HAIKU_CC(...) stuff doesn't
<ermo[m]>
Devesh Raut:
<ermo[m]>
oops, sorry
<ermo[m]>
¯\_(ツ)_/¯
Vidrep_64 has quit [Quit: Vision[]: i've been blurred!]
<nekobot>
[haiku/haiku] 514c42d7408d - intel_extreme: improve DpAux support on HSW/SNB/IVB
JakeSays has joined #haiku
x10z has joined #haiku
DKnoto has quit [Ping timeout: 480 seconds]
DKnoto has joined #haiku
mmu_man has quit [Remote host closed the connection]
vdamewood_ has quit [Read error: Connection reset by peer]
vdamewood has joined #haiku
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
x10z has joined #haiku
mmu_man has joined #haiku
AlaskanEmily has joined #haiku
<ermo[m]>
Huh. Not bad. I extrapolated it would take 1h20m (80m) to compile both toolchain and haiku on ye olde Q9400@2.8GHz. As it turns out, it took 38m21s for the toolchain and 34m plus change for haiku, so 73m overall. Nice.
B2IA has quit [Quit: Vision[]: i've been blurred!]
alex-soto[m] has left #haiku [#haiku]
B2IA has joined #haiku
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ClaudioM has joined #haiku
B2IA has quit [Quit: Vision[]: i've been blurred!]