Re: [Qemu-devel] Problems building and installing qemu v4.1.0-rc1 in single step

[Guenter Roeck]

Hi,

On 7/11/19 12:48 AM, Philippe Mathieu-Daudé wrote:
> 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
Yes, that looks like the same problem.

Reverting the following commits fixes the problem for me.

8d358a5 Makefile: Fix "make clean" in "unconfigured" source directory
        (possibly for context to be able to revert the next patch)
1338a4b Makefile: Reuse all's recursion machinery for clean and install

> > > /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.
No, the affected file is really truncated (or empty). The file system has
some 200+ GB of free space on an NVME drive. The error message above is
a side effect. Host is Ubuntu 16.01 running gcc 7.4 with binutils 2.26.1;
CPU is Ryzen 2700X.

For sure, the internal linker error is a binutils problem, but that should
not distract from the real issue.

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

No, there is nothing virtual involved. Also, again, the problem is only seen
with "make -j X".

Guenter

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