qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: total fail on FreeBSD 14.0 amd64 regardless of compiler


From: Daniel P . Berrangé
Subject: Re: total fail on FreeBSD 14.0 amd64 regardless of compiler
Date: Mon, 10 Oct 2022 10:04:17 +0100
User-agent: Mutt/2.2.7 (2022-08-07)

On Mon, Oct 10, 2022 at 06:56:51AM +0000, Dennis Clarke wrote:
> 
> re: https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg01249.html
> 
> Using GCC 12 is even worse :
> 
> [2040/6841] Compiling C object qemu-system-aarch64.p/softmmu_main.c.o
> [2041/6841] Linking target qemu-system-aarch64
> FAILED: qemu-system-aarch64
> /usr/local/bin/g++12 -m64 -mcx16 @qemu-system-aarch64.rsp
> /usr/local/bin/ld: libqemuutil.a.p/util_filemonitor-inotify.c.o: undefined
> reference to symbol 'inotify_init1'
> /usr/local/bin/ld: /usr/local/lib/libinotify.so.0: error adding symbols: DSO
> missing from command line

This is trying to tell us that inotify_init1 is in libinotify.so.0
but we have not put -linotify on the command line for the link
step.  On Linux these are a standard part of glibc, but on FreeBSD
they are separate.

I'm thinking that in previous FreeBSD we probably got this linked
indirectly, but something in 14.0 has become stricer, wanting it
listed explicitly.

IOW, a meson.build change is likely needed to  add -linotify on
FreeBSD.


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]