public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Cc: crossgcc@sourceware.org
Subject: Re: mips 32 24kec eabi. . .
Date: Mon, 06 Jul 2015 10:07:00 -0000	[thread overview]
Message-ID: <20150706100707.GE17734@vapier> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6B9FB2981@ex-mb1.corp.adtran.com>

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

On 02 Jul 2015 18:14, ANDY KENNEDY wrote:
> I derived a patch that I stole from the ARM folks for their eabi
> settings.  I have the ability to make an elf toolchain that is eabi.
> When attempting to build a Linux glibc toolchain, I get errors on the
> tuple for building the base glibc as it doesn't understand
> mipsel-linux-gnueabi.  Digging into the goings on I see the error
> -mabicalls conflicts with -mabi=eabi.  I have searched every way I can
> think of to locate the -mabicalls (which is the same as -mnoabicalls if
> you didn't already know that) but it is not physically located in the
> source of ct-ng.  Where is this coming from?
> 
> The comments around the selection for eabi state that this is not
> applicable for mips, however, for my embedded processor, it is.  In
> fact, this is a valid configuration according to the information from
> gcc and (I think) also glibc. . .
> 
> Anyone have any ideas on where we are getting the -mabicalls?

glibc itself enforces one of three -mabi settings:
sysdeps/mips/mips32/Makefile:CC += -mabi=32
sysdeps/mips/mips64/n32/Makefile:CC += -mabi=n32
sysdeps/mips/mips64/n64/Makefile:CC += -mabi=64

that's going to conflict with -mabi=eabi.
-mike

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

  reply	other threads:[~2015-07-06 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 18:14 ANDY KENNEDY
2015-07-06 10:07 ` Mike Frysinger [this message]
2015-07-06 16:00   ` ANDY KENNEDY
2015-07-06 16:42     ` Mike Frysinger
2015-07-06 17:40       ` ANDY KENNEDY
2015-07-07  4:21         ` 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=20150706100707.GE17734@vapier \
    --to=vapier@gentoo.org \
    --cc=ANDY.KENNEDY@adtran.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).