public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Multiple Simulators Link Failure on Head
Date: Mon, 23 Mar 2015 16:34:00 -0000	[thread overview]
Message-ID: <20150323163427.GD8039@vapier> (raw)
In-Reply-To: <55102407.4010806@oarcorp.com>

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]

On 23 Mar 2015 09:32, Joel Sherrill wrote:
> On 03/22/2015 05:46 PM, Joel Sherrill wrote:
> > On 3/22/2015 9:29 PM, Mike Frysinger wrote:
> >> On 20 Mar 2015 13:13, Joel Sherrill wrote:
> >>> 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.
> >> when it fails, can you attach the full build log ?
> >>
> >> what gcc version are you using ?  there might be some misbehavior with the usage
> >> of extern inline.  i think the code base expects gnu_inline semantics but just
> >> uses "extern inline" directly.  maybe try including -fgnu89-inline in your
> >> CFLAGS and see if that helps ?
> > I am not in good position to send build logs or try the alternative CFLAGS
> > until another long build finishes.
> >
> > But the idea of the gcc version sounds promising. I am building with a gcc
> > from near the head. The default version of C has changed to C11 and I
> > know that has caused a few odd issues with RTEMS. Maybe this has
> > impacted the the compilation of this method.
> >
> > $ gcc --version
> > gcc (GCC) 5.0.0 20150211 (experimental)
> >
> >
> > I will try the suggestions as soon as I can.
>
> I can confirm that lm32 and other targets built with the native
> Fedora compiler.
> 
> $ gcc --version
> gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)
> 
> But failed with I switched to using the more recent native I
> listed above.
> 
> I can provide a log if you want but that should be enough to
> reproduce this.

ok, i guess i have to stop being lazy and get Gentoo's gcc-5 snapshots working 
again
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-03-23 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 13:16 Joel Sherrill
2015-03-20 15:38 ` Mike Frysinger
2015-03-20 16:08   ` Joel Sherrill
2015-03-20 18:13   ` Joel Sherrill
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 [this message]

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=20150323163427.GD8039@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb@sourceware.org \
    --cc=joel.sherrill@oarcorp.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).