From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: 'Bryan Hundven' <bryanhundven@gmail.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: RE: Brokenness for Mips32 Little?
Date: Mon, 27 Apr 2015 22:49:00 -0000 [thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C6B9F61664@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <CAJ+oik3W0EjVRXBc0ZtSWb5+tw0ofcfbWUqCsiTe1+GG6UBFNQ@mail.gmail.com>
> -----Original Message-----
> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
> Sent: Monday, April 27, 2015 5:42 PM
> To: ANDY KENNEDY
> Cc: crossgcc@sourceware.org
> Subject: Re: Brokenness for Mips32 Little?
>
> Andy,
>
> On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> >> Sorry for the breakage. That's my fault. Luckily, it's temporary.
> > No problem. Easy workaround.
>
> As a side note:
> https://sourceware.org/ml/crossgcc/2015-04/msg00003.html
>
> Have you seen problems like this building mipsel?
>
> Thanks,
>
> -Bryan
Not like that. I have seen other issues (when attempting from 1.18.0) but
the tip seems to build without much issues (with the noted exception).
When doing 1.18.0 (against a newlib) I got strange conflicts and configure
reported that xgcc (I think) couldn't create executables. I didn't dig too deep
as I was in a hurry and figured I should grab a later release (or in this case
the tip).
Sorry man,
Andy
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2015-04-27 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:32 ANDY KENNEDY
2015-04-27 22:37 ` Bryan Hundven
2015-04-27 22:38 ` ANDY KENNEDY
2015-04-27 22:42 ` Bryan Hundven
2015-04-27 22:49 ` ANDY KENNEDY [this message]
2015-04-27 22:50 ` Bryan Hundven
2015-04-27 23:06 ` ANDY KENNEDY
2015-04-27 23:09 ` Bryan Hundven
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=F9C551623D2CBB4C9488801D14F864C6B9F61664@ex-mb1.corp.adtran.com \
--to=andy.kennedy@adtran.com \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).