GNOME Bugzilla – Bug 781092
Can't build with meson on Arch Linux: libm not found
Last modified: 2017-06-25 20:57:59 UTC
Trying to invoke "meson build" (tried 0.39.1 & git) fails on Arch with: Meson encountered an error in file meson.build, line 56, column 0: C library 'libm' not found
(In reply to ar from comment #0) > Trying to invoke "meson build" (tried 0.39.1 & git) fails on Arch with: > > Meson encountered an error in file meson.build, line 56, column 0: > C library 'libm' not found So you are missing a library. Are you building with JHBuild? Otherwise, nautilus cannot be build without building all its dependencies of course.
Which C library are you using?
glibc 2.25 (x64) nautilus built fine before the switch to meson. Aren't using JHBuild though, wasn't aware that's now a requirement.
(In reply to ar from comment #3) > glibc 2.25 (x64) > > nautilus built fine before the switch to meson. > > Aren't using JHBuild though, wasn't aware that's now a requirement. Well, it works for me fine (I use Arch). JHBuild is not a requirement as far as this goes.
No, not a requirement. But if you are missing a library, either to have to build it/install it or use a tool like JHBuild that does it for you.
(In reply to Carlos Soriano from comment #5) > No, not a requirement. But if you are missing a library, either to have to > build it/install it or use a tool like JHBuild that does it for you. Yeah, try building with JHBuild. In any case, I don’t believe it’s an issue on our side. Double-check your environment variables and the existence of libm (glibc ships it).
Dunno then. jhbuild gives me ~2.5 dozen nonsensical missing system packages, guess I still need to configure it right. libm exists, otherwise I'd be in a wealth of pain anyway :) Also… reverting the autotools removal (ie. 857a90c and the libgd move ec2af08) and using it again makes nautilus build properly again.
I suggest that you prod Meson devs directly regarding this on IRC. That’s #mesonbuild on freenode. You could also join #nautilus on GIMPNet and maybe we can help you there. Closing this as NOTGNOME, at least for now.
I'm having this same problem on newish Fedora 26 beta, I created bug 784189 with a patch that fixes the problem. I'm marking this bug as duplicate of that (even if older) because of the patch attached there. *** This bug has been marked as a duplicate of bug 784189 ***