From: Paolo Bonzini <1896096@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1896096] Re: Git version: Build process is broken in block_curl.c.o
Date: Fri, 18 Sep 2020 16:38:29 -0000 [thread overview]
Message-ID: <CAHFMJ7ve2_UMwzNGvYjK=pQdrAz2S-UfnaNaeQ53kvLUgVwN+w@mail.gmail.com> (raw)
In-Reply-To: 160044557014.21075.1431968160944824398.malone@wampee.canonical.com
What's your new configure command line? Attach the config.log and make V=1
log again please.
That said, I noticed that the flags were included twice in the linker
command line so maybe you've only removed them in one place.
Il ven 18 set 2020, 18:20 Frederic Bezies <1896096@bugs.launchpad.net> ha
scritto:
> Even with LDFLAGS tweaking, it breaks. Anyway, thanks for your help
> here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896096
>
> Title:
> Git version: Build process is broken in block_curl.c.o
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1896096/+subscriptions
>
>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1896096
Title:
Git version: Build process is broken in block_curl.c.o
Status in QEMU:
Invalid
Bug description:
Gcc version: 10.2.0
Glusterfs: 8.1
Libguestfs: 1.42
Configure options used:
configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--libexecdir=/usr/lib/qemu \
--extra-ldflags="$LDFLAGS" \
--smbd=/usr/bin/smbd \
--enable-modules \
--enable-sdl \
--disable-werror \
--enable-slirp=system \
--enable-xfsctl \
--audio-drv-list="pa alsa sdl"
Error log attached. Here is the beginning:
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../lib/Scrt1.o: in function `_start':
(.text+0x24): undefined reference to `main'
/usr/bin/ld: libblock-curl.a(block_curl.c.o): in function `curl_block_init':
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1896096/+subscriptions
next prev parent reply other threads:[~2020-09-18 17:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 17:52 [Bug 1896096] [NEW] Git version: Build process is broken in block_curl.c.o Frederic Bezies
2020-09-18 8:49 ` [Bug 1896096] " Daniel Berrange
2020-09-18 9:17 ` Frederic Bezies
2020-09-18 9:45 ` Frederic Bezies
2020-09-18 9:59 ` Daniel Berrange
2020-09-18 11:09 ` Frederic Bezies
2020-09-18 11:50 ` Daniel Berrange
2020-09-18 12:11 ` Laurent Vivier
2020-09-18 12:15 ` Daniel Berrange
2020-09-18 13:50 ` Frederic Bezies
2020-09-18 14:13 ` Daniel Berrange
2020-09-18 14:47 ` Frederic Bezies
2020-09-18 15:00 ` Paolo Bonzini
2020-09-18 15:06 ` Frederic Bezies
2020-09-18 15:22 ` Paolo Bonzini
2020-09-18 15:25 ` Frederic Bezies
2020-09-18 15:26 ` Frederic Bezies
2020-09-18 15:30 ` Daniel Berrange
2020-09-18 15:40 ` Frederic Bezies
2020-09-18 15:46 ` Daniel Berrange
2020-09-18 16:00 ` Daniel Berrange
2020-09-18 16:03 ` Frederic Bezies
2020-09-18 16:12 ` Frederic Bezies
2020-09-18 16:38 ` Paolo Bonzini [this message]
2020-09-18 16:57 ` Daniel Berrange
2020-09-18 17:03 ` Frederic Bezies
2020-09-18 17:04 ` Frederic Bezies
2020-09-18 18:35 ` Paolo Bonzini
2020-09-18 21:55 ` Toolybird
2020-09-18 22:28 ` Peter Maydell
2020-09-19 6:37 ` Frederic Bezies
2020-09-19 8:54 ` Paolo Bonzini
2020-09-19 10:15 ` Frederic Bezies
2020-09-19 11:05 ` Paolo Bonzini
2020-09-19 11:11 ` Frederic Bezies
2020-09-19 22:31 ` Toolybird
2020-09-20 5:51 ` Paolo Bonzini
2020-09-20 6:49 ` Toolybird
2020-09-20 9:24 ` Paolo Bonzini
2020-09-20 9:30 ` Paolo Bonzini
2020-09-22 21:25 ` Toolybird
2020-09-22 21:30 ` Toolybird
2020-09-23 6:10 ` Paolo Bonzini
2020-09-23 21:46 ` Toolybird
2020-09-30 19:20 ` Frederic Bezies
2020-09-30 19:38 ` Paolo Bonzini
2020-10-02 20:59 ` Toolybird
2020-10-02 21:24 ` Paolo Bonzini
2020-10-05 13:57 ` Paolo Bonzini
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='CAHFMJ7ve2_UMwzNGvYjK=pQdrAz2S-UfnaNaeQ53kvLUgVwN+w@mail.gmail.com' \
--to=1896096@bugs.launchpad.net \
--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).