From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Philip Belemezov <philip@belemezov.net>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH 1 of 2] libc/eglibc: [OS X] Don't Use __block as a Name of an Argument
Date: Sat, 13 Apr 2013 09:56:00 -0000 [thread overview]
Message-ID: <20130413095609.GA4599@free.fr> (raw)
In-Reply-To: <5168E388.1000603@belemezov.net>
Philip, All,
On Sat, Apr 13, 2013 at 07:48:08AM +0300, Philip Belemezov wrote:
> On 13.04.2013 00:51, Yann E. MORIN wrote:
> >On Tue, Mar 26, 2013 at 05:25:31PM +0200, Philip Belemezov wrote:
> >># HG changeset patch
> >># User Philip Belemezov <philip@belemezov.net>
> >># Date 1364300812 -7200
> >># Node ID fcdf7fc7fd1c00715c3d9651ff00d805ecfb8aa8
> >># Parent 0fc56e62cecf07e4cdaf866ee24d6893c4ade436
> >>libc/eglibc: [OS X] Don't Use __block as a Name of an Argument
> >>
> >>Apple's GCC defines __block as
> >>
> >>#define __block __attribute__((__blocks__(byref)))
> >>
> >>which causes compilation to fail (attribute cannot be applied to argument).
> >
> >I do not understand why this patch is needed at all: we're not building
> >(e)glibc with the Apple-patched native gcc, but with a plain gcc that we
> >just build ourselves in the process.
> >
> >Unless I missed something... Can you elaborate, please?
>
> I don't have the details any more, but I believe this was happening during
> the bootstrap phase, before the target gcc has been built.
The only case where we may do something in (e)glibc without having a
target gcc is to install the libc headers when using LinuxThreads, which
have not be supported in (e)glibc for some time (some years, now).
In all other cases, building anything libc involves having a target gcc
first.
The only reason we'd use the native compiler (and hence your
Apple-severed version of gcc) would be if (e)glibc needed to build a
program that runs on your build machine, and I am not aware of such a
case ( but I am sometimes easily proven wrong! ;-) )
> Let me reproduce the failure and see where exactly it choke.
Thank you for investigating! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-04-13 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 15:28 [PATCH 0 of 2] [OS X] Fix Compilation of eglibc-2.17 Philip Belemezov
2013-03-26 15:28 ` [PATCH 1 of 2] libc/eglibc: [OS X] Don't Use __block as a Name of an Argument Philip Belemezov
2013-04-12 21:51 ` Yann E. MORIN
2013-04-13 4:48 ` Philip Belemezov
2013-04-13 9:56 ` Yann E. MORIN [this message]
2013-04-14 8:13 ` Philip Belemezov
2013-03-26 15:28 ` [PATCH 2 of 2] libc/eglibc: [OS X] Don't Redefine Already Defined Types in rpc/types.h Philip Belemezov
2013-04-12 21:57 ` Yann E. MORIN
2013-04-13 6:29 ` Titus von Boxberg
2013-04-13 16:10 ` Philip Belemezov
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=20130413095609.GA4599@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=philip@belemezov.net \
/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).