Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: gdb@sourceware.org
Subject: Re: Multiple Simulators Link Failure on Head
Date: Fri, 20 Mar 2015 18:13:00 -0000	[thread overview]
Message-ID: <550C6342.104@oarcorp.com> (raw)
In-Reply-To: <20150320153851.GG11803@vapier>

This looks to be an issue with the "make -j8".
I did it again with "-j8" and it failed. I did a simple "make clean all"
in that directory and it failed again.

I then changed my script to drop the -j8 and it built ok again.

My suspicion is something in the dependencies isn't 100% right
and there is a race condition. sim/common/cconfig.h is the same
in a tree built with -j1 vs -j8.

--joel

On 3/20/2015 10:38 AM, Mike Frysinger wrote:
> On 20 Mar 2015 08:16, Joel Sherrill wrote:
>> Multiple targets fail to link with sim_addr_range_hit_p. The
>> targets are:
> are you doing incremental builds ?  or did you build entirely from scratch ?  
> some changes landed recently that would break incremental, so you should build 
> the sim dir from scratch.
>
> how exactly did you run configure ?  how about `make` ?
>
> i build every sim target myself and run their testsuites before i push new sim 
> commits ...
> -mike

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985



  parent reply	other threads:[~2015-03-20 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 13:16 Joel Sherrill
     [not found] ` <20150320153851.GG11803@vapier>
2015-03-20 16:08   ` Joel Sherrill
2015-03-20 18:13   ` Joel Sherrill [this message]
2015-03-20 19:18     ` Mike Frysinger
2015-03-20 20:15     ` Mike Frysinger
2015-03-22 22:29     ` Mike Frysinger
2015-03-22 22:46       ` Joel Sherrill
2015-03-23 14:32         ` Joel Sherrill
2015-03-23 16:34           ` Mike Frysinger

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=550C6342.104@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gdb@sourceware.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