qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Guenter Roeck" <linux@roeck-us.net>,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] Problems building and installing qemu v4.1.0-rc1 in single step
Date: Thu, 11 Jul 2019 09:48:07 +0200	[thread overview]
Message-ID: <dc31e591-3b22-8626-10b2-48597f56ee0a@redhat.com> (raw)
In-Reply-To: <20190711010742.GA810@roeck-us.net>

Hi Guenter,

Cc'ing Markus/Dan/Alex

On 7/11/19 3:07 AM, Guenter Roeck wrote:
> On Wed, Jul 10, 2019 at 03:01:53PM -0700, Guenter Roeck wrote:
>> Hi,
>>
>> when trying to run "make -j30 install" from a clean tree on v4.1.0-rc0, I get
>> _lots_ of undefined symbol errors.
>>
>> If I run "make -j30" followed by "make -j30 install", make succeeds, but then
>> I get linker errors such as the following when running "make -j30 install".

Seems similar to this report:
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg01860.html

>>
>> /usr/bin/ld: final link failed: File truncated
>> /usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.26.1 internal error,
>> 	aborting at ../../bfd/merge.c:905 in _bfd_merged_section_offset

This seems new, what is your host?

"File truncated" reminds me out-of-space issues.

FWIW sometimes I'm having some weird issue when calling "make
check-tcg". Docker is used to build target binaries, but apparently it
tries to compile some host object instead and fails, but I don't reach
the linking.
Just to clear this out, do you see any docker started?

>>
>> Running "make -j30" followed by "make install" succeeds.
>>
> 
> Correction: This doesn't always work either. Sometimes I still get a linker
> error. If that happens, another round of "make; make install" succeeds.
> 
> Guenter
> 
>> This looks like "make install" may have bad dependencies. Has anyone else
>> experienced this problem ?
>>
>> Thanks,
>> Guenter
> 


  reply	other threads:[~2019-07-11  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 22:01 [Qemu-devel] Problems building and installing qemu v4.1.0-rc1 in single step Guenter Roeck
2019-07-11  1:07 ` Guenter Roeck
2019-07-11  7:48   ` Philippe Mathieu-Daudé [this message]
2019-07-11 13:33     ` Guenter Roeck
2019-07-11 15:38       ` Markus Armbruster
2019-07-11 16:11         ` Guenter Roeck
2019-07-12  6:02           ` Markus Armbruster

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=dc31e591-3b22-8626-10b2-48597f56ee0a@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=linux@roeck-us.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).