All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: qemu-devel@nongnu.org, i.maximets@samsung.com,
	heetae82.ahn@samsung.com, quintela@redhat.com,
	dgilbert@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] fix tests/migration/stress build
Date: Fri, 29 Sep 2017 11:46:57 +0100	[thread overview]
Message-ID: <20170929104657.GC11930@redhat.com> (raw)
In-Reply-To: <1506679874-22284-1-git-send-email-a.perevalov@samsung.com>

On Fri, Sep 29, 2017 at 01:11:13PM +0300, Alexey Perevalov wrote:
> This small commit fixes build of tests/migration/stress on Ubuntu16.04
> (on RHEL7.4 the same situation, after typical configure with following options
> --target-list=x86_64-linux-user,i386-linux-user,x86_64-softmmu,i386-softmmu \
> --enable-numa --enable-kvm --enable-vhost-net --enable-tpm --enable-debug \
>  --disable-gtk )
> PTHREAD_LIB is empty after successfully compiled pthread sample in configure.
> tests/migration/stress relay on it, but -pthread is not there
> and linker fails trying to resolve pthread symbols.
> 
> I still have a questions:
> 1. Is there a better way to obtain -thread option from QEMU_CFLAGS
> 2. Is linker options really necessary for stress application, because only -O3
> is used, so w/o linker options in Makefile there is no need in PTHREAD_LIB
> at all, I mean in whole project.
> 3. LINKPROG will be expanded into c++ firstly, and -static in
> tests/Makefile.include will require static libstdc++, but configure doesn't
> check it and in case of missing libstdc++-static.x86_64 (RHEL package name),
> build will fail with the following message: "ld: cannot find -lstdc++",
> I think here reasonably to use just $(CC) instead of LINKPROG, stress.c is on C.

Yeah, changing to $(CC) is fine - and adding -lpthread to the end of the
args instead of $PTHREAD_LIB

> 
> Also ./tests/migration/guestperf.py can not be started w/o
> super user privileges, and reports in this case something useless like this:
> Error: [Errno 104] Connection reset by peer

IIRC, that's an Ubuntu problem - they pointlessly restrict their
/boot/vmlinuz files so you can't read them as non-root. Use the
--kernel arg to point to a readable image. There's no need for
the test to run privileged

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 :|

  parent reply	other threads:[~2017-09-29 10:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170929101124eucas1p25695c76db8f17ef8181ee2b3051bba98@eucas1p2.samsung.com>
2017-09-29 10:11 ` [Qemu-devel] [PATCH] fix tests/migration/stress build Alexey Perevalov
2017-09-29 10:11   ` [Qemu-devel] [PATCH] configure: correctly define PTHREAD_LIB Alexey Perevalov
2017-09-29 10:40     ` Daniel P. Berrange
2017-09-29 12:52       ` Alexey Perevalov
2017-09-29 13:05         ` Daniel P. Berrange
2017-09-29 13:47           ` Alexey Perevalov
2017-09-29 14:38             ` Daniel P. Berrange
2017-10-02  8:30               ` [Qemu-devel] [PATCH] fix tests/migration/stress build in case of absend static libc++ Alexey Perevalov
2017-10-02  8:30               ` [Qemu-devel] [PATCH] Makefile: don't use LINKPROG for tests/migration/stress Alexey Perevalov
2017-10-02 11:14                 ` Peter Maydell
2017-10-02 11:17                   ` Daniel P. Berrange
2017-10-02 11:19                     ` Peter Maydell
2017-10-02 11:21                       ` Daniel P. Berrange
2017-09-29 10:46   ` Daniel P. Berrange [this message]
2017-09-29 15:05     ` [Qemu-devel] [PATCH] fix tests/migration/stress build Alexey Perevalov

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=20170929104657.GC11930@redhat.com \
    --to=berrange@redhat.com \
    --cc=a.perevalov@samsung.com \
    --cc=dgilbert@redhat.com \
    --cc=heetae82.ahn@samsung.com \
    --cc=i.maximets@samsung.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.