On 11/30/20 5:30 PM, Ken Moffat via blfs-support wrote:
On Fri, Nov 27, 2020 at 09:14:40PM +0000, Ken Moffat via blfs-support wrote:
On Fri, Nov 27, 2020 at 09:46:39PM +0100, Pierre Labastie via blfs-support
wrote:
On Fri, 2020-11-27 at 17:50 +0000, Ken Moffat via blfs-support wrote:
On Tue, Nov 10, 2020 at 06:34:21PM +0100, Christopher Gregory via
blfs-support wrote:
I notice that arch have dropped the need to make sysprof a
requirement. I have not found any patch to date to actually get it
to work. I am using the svn version of systemd blf from 2020-11-
01. There has been no update to sysprof so I could not see if a
later version worked.
Starting a fresh sub-thread to reply to this, because we were
floundering. I've just hit this, and apart from Christopher's post
google found
https://github.com/mesonbuild/meson/issues/7929
Seems to be a problem with meson-0.56.0, apparently will be fixed
with 0.56.1 by
https://github.com/mesonbuild/meson/commit/2b923f532c3e16687910fecb09cedb80a76597cf.diff
but that didn't make any difference for me.
Just to be sure: it is not enough to just patch meson and recompile
libsoup. Sysprof has to be recompiled to after the change to meson: the
problem is in the .pc file for sysprof (-pthread not present in the
"public" part of the .pc file).
Ah, I missed that (rebuilt meson, retried libsoup).
I'll upload the patch to patches, but I really don't think we need
to recommend sysprof for libsoup.
ĸen
Xi and I were the ones who found the issue. If you don't have sysprof
installed, on our systems, libsoup downloaded a git copy of
libsysprof-capture-4. Turning sysprof off is an option of course, but it
does remove some functionality and it remains to be seen (I guess I'll
see here in a day or two since I'm doing a full rebuild for systemd-247)
what having that functionality removed actually does...
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
