On Tue, 2020-09-29 at 23:16 +0100, Ross Burton wrote: > Previously this recipe was changed to do debug builds because > otherwise insane > warns that the binary is already stripped. > > However, debug builds for boost.build also pass -O0. It turns out > that given > how large Boost is (or, how bad boost.build is) doing a release build > with -O3 > knocks a third off the walltime for a Boost package in my test, > mainly by reducing > how long it spends deciding that nothing needs to be rebuilt in > do_install: > > PKG TASK ABSDIFF RELDIFF WALLTIME1 -> WALLTIME2 > boost do_install -330.7s -69.2% 477.6s -> 146.9s > boost do_compile -7.1s -2.7% 269.3s -> 262.2s > > Replace debug mode with INSANE_SKIP=already-stripped.
This isn't so simple unfortunately. If the binaries are stripped, we can't do the debug symbols processing, the src packages are empty and so on, it has knock on repercussions. Can we stop the -O0 in debug builds somehow? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142916): https://lists.openembedded.org/g/openembedded-core/message/142916 Mute This Topic: https://lists.openembedded.org/mt/77207077/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
