qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure
Date: Mon, 21 Sep 2020 16:08:26 +0200	[thread overview]
Message-ID: <437d5c39-0a27-b261-102b-0da64734966a@redhat.com> (raw)
In-Reply-To: <20200921133840.sby75zn7unds2q3a@mozz.bu.edu>

On 21/09/20 15:38, Alexander Bulekov wrote:
> Hi Paolo,
> These are the builds with clang coverage enabled.
> The normal fuzzing builds are succeeding now (log from this morning:
> https://oss-fuzz-build-logs.storage.googleapis.com/log-a426424c-cae4-407a-ae7b-205a9ae59286.txt
> )
> 
> I already send a patch that seems to fix the coverage build failure, but
> I can't explain why it does the trick. 
> Message-Id: <20200909220516.614222-1-alxndr@bu.edu>
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg03639.html

The reason for the bug is the -Wl,-lm in QEMU_LDFLAGS.  Putting the
tricky flags first actually makes sense, so I'll queue it.

Paolo



      reply	other threads:[~2020-09-21 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=0a88cf92d34dc9db91727cc9bd0dc58b=d9ca53ad17e3d19752f355e6c3ba1ecc=oss-fuzz@monorail-prod.appspotmail.com>
     [not found] ` <0000000000003aa8d805afd00f24@google.com>
2020-09-21 12:10   ` Issue 25514 in oss-fuzz: qemu: Coverage build failure Paolo Bonzini
2020-09-21 13:38     ` Alexander Bulekov
2020-09-21 14:08       ` Paolo Bonzini [this message]

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=437d5c39-0a27-b261-102b-0da64734966a@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alxndr@bu.edu \
    --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).