From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Questions about gcc linker errors in crypto sub-directory
Date: Tue, 27 Sep 2016 13:51:55 +0100 [thread overview]
Message-ID: <20160927125155.GO3967@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B03D93DC@SZXEMA503-MBS.china.huawei.com>
On Mon, Sep 26, 2016 at 09:19:36AM +0000, Gonglei (Arei) wrote:
>
>
>
>
>
> > -----Original Message-----
> > From: Daniel P. Berrange [mailto:berrange@redhat.com]
> > Sent: Monday, September 26, 2016 5:14 PM
> > To: Gonglei (Arei)
> > Cc: qemu-devel@nongnu.org
> > Subject: Re: Questions about gcc linker errors in crypto sub-directory
> >
> > On Mon, Sep 26, 2016 at 09:03:45AM +0000, Gonglei (Arei) wrote:
> > > Hi Daniel,
> > >
> > > I'm coding cryptodev-vhost-user.c as a new cryptodev backend,
> > > but the gcc report some linker errors:
> > >
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_crypto_cleanup':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:87:
> > undefined reference to `vhost_dev_cleanup'
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_crypto_init':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:126:
> > undefined reference to `vhost_dev_init'
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_user_opened':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:187:
> > undefined reference to `qemu_chr_find'
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:194:
> > undefined reference to `qemu_chr_fe_claim_no_fail'
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_user_event':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:213:
> > undefined reference to `qemu_chr_set_reconnect_time'
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_user_init':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:257:
> > undefined reference to `qemu_chr_add_handlers'
> > > crypto/cryptodev-vhost-user.o: In function
> > `qcrypto_cryptodev_vhost_user_finalize':
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:353:
> > undefined reference to `qemu_chr_add_handlers'
> > > /mnt/sdb/gonglei/qemu.git/qemu/crypto/cryptodev-vhost-user.c:354:
> > undefined reference to `qemu_chr_fe_release'
> > > collect2: ld returned 1 exit status
> > > make: *** [qemu-nbd] Error 1
> > >
> > > Currently I only change the crypto/Makefile.objs:
> > >
> > > diff --git a/crypto/Makefile.objs b/crypto/Makefile.objs
> > > index b9ad26a..575f64e 100644
> > > --- a/crypto/Makefile.objs
> > > +++ b/crypto/Makefile.objs
> > > @@ -28,6 +28,7 @@ crypto-obj-y += block-qcow.o
> > > crypto-obj-y += block-luks.o
> > > crypto-obj-y += cryptodev.o
> > > crypto-obj-y += cryptodev-builtin.o
> > > +crypto-obj-y += cryptodev-vhost-user.o
> >
> > The $(crypto-obj-y) variable is intended to only contain general purpose
> > crypto code, since it needs to be linked to all QEMU programs. Your
> > cryptodev file is specific to system emulators, so must only be linked
> > to the system emulator targets. Thus, it should not be added to the
> > crypto-obj-y variable.
> >
> > It probably needs to be added to either common-obj-y or obj-y - I can't
> > remember which is "best"
> >
> common-obj-y is fine! So all cryptodev stuff should be use
> $( crypto-obj-y) variable, right? I'll change them in the next version.
Looking at this again, it actually makes me think that your
cryptodev stuff would be better in the backends/ directory.
That would mean the crypto/ directory is kept as the place for
generic crypto infrastructure, and avoiding system emulator
specific device backend code. The backends/Makefile.objs is
already setup to use common-obj-y and builds various other
device backend models.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-09-27 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 9:03 [Qemu-devel] Questions about gcc linker errors in crypto sub-directory Gonglei (Arei)
2016-09-26 9:13 ` Daniel P. Berrange
2016-09-26 9:19 ` Gonglei (Arei)
2016-09-27 12:51 ` Daniel P. Berrange [this message]
2016-09-28 1:42 ` Gonglei (Arei)
2016-09-28 9:09 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160927125155.GO3967@redhat.com \
--to=berrange@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).