- Thread Starter
- #76
If you use poudriere, you'll always have a complete log![]()
Synth has got logs too. Having rebuilt the same ports again without LTO, the logs have been overwritten.
Anyway, I do not believe that LTO can be a big benefit...
Yup.
If you use poudriere, you'll always have a complete log![]()
Anyway, I do not believe that LTO can be a big benefit...
… Firefox with LTO. …
… to get a reliable reading seems hard. I have not seen any e-mail client benchmarks…
And I can confirm this on an independent installation. The build ends with:FYI, thunderbird failing with LTO is already reported.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255311
ld: error: undefined hidden symbol: JS::CleanupQueuedFinalizationRegistry(JSContext*, JS::Handle<JSObject*>)
>>> referenced by Unified_cpp_xpcom_base0.cpp
>>> lto.tmp:(mozilla::CleanupFinalizationRegistriesRunnable::Run())
ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
Yeah, that is weird - I always turn the debugging option off when I compile my ports, and I have yet to see that being a problem. Well, some ports still fail to compile for me, so that's an option to try next time... ?Speaking of LTO, I encountered something bizarre after enabling it in the configuration menu for the libreoffice port and keeping default values for this port's other configuration options. I compiled the port, but libreoffice crashed every time I tried to start it. Then I added WITH_DEBUG=yes to poudriere's make.conf, and, while keeping the LTO configuration option enabled, I re-compiled the port... And this time there were no crashes when I was running libreoffice. I have no idea why WITH_DEBUG=yes resulted in LTO-enabled libreoffice that didn't crash. By the way, WITH_DEBUG=yes still resulted in a stripped soffice.bin binary! This is all so bizarre and mysterious.
Just to clarify - this is the disabling of the timeout (the timeout on the text output from the build itself) recommended in Post #34 of this thread earlier, correct?:I have disabled the timeout in synth and will go out and not watch it.
The timeout is in the synth code, if you want a no timeout rebuild ports-mgmt/synth with the option WATCHDOG off
Last time I check, the watchdog of synth will kill the build if there is no output during a certain time. What may happen is that the build is still in progress, but there is no output.