https://sourceware.org/bugzilla/show_bug.cgi?id=29107
Xi Ruoyao <xry111 at xry111 dot site> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at xry111 dot site
--- Comment #2 from Xi Ruoyao <xry111 at xry111 dot site> ---
(In reply to Nick Clifton from comment #1)
> (In reply to Toolybird from comment #0)
>
> > Any thoughts? Thanks.
>
> Don't run the testsuites in parallel ? :-)
>
> OK, so not helpful. Instead some questions - if you run the builds in
> parallel, but then the checks sequentially, does everything work. How about
> the other way around (sequential builds, parallel tests) ?
>
> The thing that struck me about the error message was that it looks like the
> opcodes library is in the process of being built whilst the tests are
> running. So maybe - just a theory - the gprofng testsuite is triggering a
> *re-build* of the opcodes library for some reason. (Because of some strange
> makefile dependency maybe ?)
The reason is gprofng tests installs libopcodes.so into a chroot environment,
and libtool (a stupid thing trying to be *too* clever, I must add) relinks a
shared object being installed.
> Another wild guess - maybe adding the .NOTPARALLEL: pseudo-target to the
> gprofng Makefile.am would help ? Just before the check-DEJAGNU: target ?
I'll try.
--
You are receiving this mail because:
You are on the CC list for the bug.
