From: Mike Frysinger <vapier@gentoo.org>
To: linasvepstas@gmail.com
Cc: libc-ports@sourceware.org, gcc@gcc.gnu.org,
GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: gcc vs. glibc bootstrapping of libgcc_eh.a
Date: Fri, 11 Nov 2011 22:23:00 -0000 [thread overview]
Message-ID: <201111111723.40351.vapier@gentoo.org> (raw)
In-Reply-To: <CAHrUA35L03DW0Pw=n34dpLY-WsUEqL9XsUBWzjY3w8y+hjDN+w@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 813 bytes --]
On Friday 11 November 2011 16:27:18 Linas Vepstas wrote:
> Thanks Mike, silly me, it seems that crosstool_ng is exactly what I need!
>
> Off-topic, but .. anyone have a clue about why my canadian-cross of
> gcc is picking up its own internal limits.h, instead of glibc's
> limits.h? Since gcc's limits.h doesn't have ‘SSIZE_MAX’ which
> gcc/config/host-linux.c wants. I suppose I can just google the
> answer, can't I?
gcc is supposed to provide a limits.h. but at the end of that file, it does:
#include_next <limits.h>
this way you get both the gcc and the glibc defines.
what you're asking about is semi-common, but it's been so long since i solved
that issue that i don't remember the answer off the top of my head. i do know
that crosstool-ng takes care of it for you ;).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-11-11 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:29 Linas Vepstas
2011-11-09 17:53 ` Chris Metcalf
2011-11-10 2:50 ` Mike Frysinger
2011-11-11 21:27 ` Linas Vepstas
2011-11-11 21:43 ` Ian Lance Taylor
2011-11-11 22:23 ` 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=201111111723.40351.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=linasvepstas@gmail.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).