From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: Jeff Law <law@redhat.com>, Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Denis Chertykov <chertykov@gmail.com>,
Eric Christopher <echristo@gmail.com>,
Matthew Fortune <matthew.fortune@imgtec.com>,
"David Edelsohn" <dje.gcc@gmail.com>,
Alexandre Oliva <aoliva@redhat.com>,
Kaz Kojima <kkojima@gcc.gnu.org>,
Oleg Endo <olegendo@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: RE: [BUILDROBOT] "error: null argument where non-null required" on multiple targets
Date: Mon, 21 Dec 2015 14:20:00 -0000 [thread overview]
Message-ID: <FD3DCEAC5B03E9408544A1E416F112420192CF21FE@NA-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <5672F976.1090609@redhat.com>
> -----Original Message-----
> From: Jeff Law [mailto:law@redhat.com]
> Sent: Thursday, December 17, 2015 1:06 PM
> To: Jan-Benedict Glaw
> Cc: Moore, Catherine; Denis Chertykov; Eric Christopher; Matthew Fortune;
> David Edelsohn; Alexandre Oliva; Kaz Kojima; Oleg Endo; Jonathan Wakely;
> gcc-patches
> Subject: Re: [BUILDROBOT] "error: null argument where non-null required"
> on multiple targets
>
> On 12/16/2015 03:46 AM, Jan-Benedict Glaw wrote:
> > On Tue, 2015-12-15 10:43:58 -0700, Jeff Law <law@redhat.com> wrote:
> >> On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote:
> >>> On Mon, 2015-12-14 18:54:28 +0000, Moore, Catherine
> <Catherine_Moore@mentor.com> wrote:
> >>>> Is there an easy way to reproduce the MIPS problems that you
> >>>> reported? I don't seem to be able to do it with a cross-compiler
> >>>> targeting mipsel-elf.
> >>>
> >>> What's your build compiler? For these builds, where it showed up,
> >>> I'm using a freshly compiles HEAD/master version. So basically,
> >>> compile a current GCC for your build machine:
> >> Right. This is something that only shows up when using the trunk to
> >> build the crosses.
> >>
Thanks -- I have now reproduced the problem.
prev parent reply other threads:[~2015-12-21 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 21:48 Jan-Benedict Glaw
2015-12-14 18:54 ` Moore, Catherine
2015-12-14 20:07 ` Jan-Benedict Glaw
2015-12-15 17:44 ` Jeff Law
2015-12-16 10:46 ` Jan-Benedict Glaw
2015-12-17 18:05 ` Jeff Law
2015-12-17 18:34 ` config-list.mk and obsoleted configurations (was: [BUILDROBOT] "error: null argument where non-null required" on multiple targets) Jan-Benedict Glaw
2015-12-17 18:39 ` config-list.mk and obsoleted configurations Jeff Law
2015-12-17 18:58 ` Jan-Benedict Glaw
2015-12-17 19:53 ` Jeff Law
2015-12-17 20:33 ` Trevor Saunders
2015-12-17 21:02 ` Jeff Law
2015-12-21 14:20 ` Moore, Catherine [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=FD3DCEAC5B03E9408544A1E416F112420192CF21FE@NA-MBX-04.mgc.mentorg.com \
--to=catherine_moore@mentor.com \
--cc=aoliva@redhat.com \
--cc=chertykov@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=echristo@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=jwakely@redhat.com \
--cc=kkojima@gcc.gnu.org \
--cc=law@redhat.com \
--cc=matthew.fortune@imgtec.com \
--cc=olegendo@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).