Re: [PATCH-for-5.2 v3 2/4] hw/9pfs: Fix Kconfig dependency problem between 9pfs and Xen

[Greg Kurz <groug@xxxxxxxx>]

On Thu, 5 Nov 2020 13:15:59 +0100
Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> wrote:

> On 11/4/20 6:54 PM, Greg Kurz wrote:
> > On Wed, 04 Nov 2020 13:18:09 +0100
> > Christian Schoenebeck <qemu_oss@xxxxxxxxxxxxx> wrote:
> > 
> >> On Mittwoch, 4. November 2020 12:57:04 CET Philippe Mathieu-Daudé wrote:
> >>> Commit b2c00bce54c ("meson: convert hw/9pfs, cleanup") introduced
> >>> CONFIG_9PFS (probably a wrong conflict resolution). This config is
> >>> not used anywhere. Backends depend on CONFIG_FSDEV_9P which itself
> >>> depends on CONFIG_VIRTFS.
> >>>
> >>> Remove the invalid CONFIG_9PFS and use CONFIG_FSDEV_9P instead, to
> >>> fix the './configure --without-default-devices --enable-xen' build:
> >>>
> >>>   /usr/bin/ld: libcommon.fa.p/hw_xen_xen-legacy-backend.c.o: in function
> >>> `xen_be_register_common': hw/xen/xen-legacy-backend.c:754: undefined
> >>> reference to `xen_9pfs_ops' /usr/bin/ld:
> >>> libcommon.fa.p/fsdev_qemu-fsdev.c.o:(.data.rel+0x8): undefined reference 
> >>> to
> >>> `local_ops' /usr/bin/ld:
> >>> libcommon.fa.p/fsdev_qemu-fsdev.c.o:(.data.rel+0x20): undefined reference
> >>> to `synth_ops' /usr/bin/ld:
> >>> libcommon.fa.p/fsdev_qemu-fsdev.c.o:(.data.rel+0x38): undefined reference
> >>> to `proxy_ops' collect2: error: ld returned 1 exit status
> >>>
> >>> Fixes: b2c00bce54c ("meson: convert hw/9pfs, cleanup")
> >>> Suggested-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>
> >>> Acked-by: Greg Kurz <groug@xxxxxxxx>
> >>> Tested-by: Greg Kurz <groug@xxxxxxxx>
> >>> Signed-off-by: Philippe Mathieu-Daudé <philmd@xxxxxxxxxx>
> >>
> >> Acked-by: Christian Schoenebeck <qemu_oss@xxxxxxxxxxxxx>
> >>
> > 
> > Phil,
> > 
> > Same questioning as Connie. Do you intend to get this merged or should
> > Christian or I take care of that ?
> 
> Same answer too =) If you are preparing a pull request, please go ahead!
> 

Heh I've just seen your answer.

Christian,

Maybe you can add this patch in your next PR ?

> Thanks,
> 
> Phil.
>