From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] perl, sed and non-gsed
Date: Thu, 07 Apr 2005 17:39:13 +0200 [thread overview]
Message-ID: <42555421.2090401@gentoo.org> (raw)
In-Reply-To: <200504071728.14085@enterprise.flameeyes.is-a-geek.org>
Diego "Flameeyes" Pettenò wrote:
> On Thursday 07 April 2005 17:17, Luca Barbato wrote:
>
>>gcc is non standard and broken, ld is non standard. vim is non standard.
>
> Actually, pure gcc on OSX is broken. Just try to build yourself a vanilla gcc
> and try it with some C++ lib, it will fail because it needs a fix which is
> nog going to be applied upstream i don't know why.
>
last time I checked the maintree gcc has the fix for the 'consider
whatever .h as extern "C" ' ancient workaround, that now breaks C++
templates. the standard gcc provided by apple or the gcc from darwin
branch not.
lu
PS: once kito'll be back probably we could figure out how to fix the
issue and eventually have a working toolchain (overlayed probably) and
with a gcc-config, I do hope.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-07 15:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 16:06 [gentoo-dev] perl, sed and non-gsed Diego "Flameeyes" Pettenò
2005-03-28 16:34 ` David Morgan
2005-03-28 17:28 ` Jan Brinkmann
2005-03-28 17:31 ` Ciaran McCreesh
2005-03-28 17:43 ` Diego "Flameeyes" Pettenò
2005-03-28 17:51 ` Ciaran McCreesh
2005-03-28 18:38 ` Mike Frysinger
2005-03-28 17:52 ` Daniel Ostrow
2005-03-29 4:58 ` Aaron Walker
2005-03-29 15:23 ` Diego "Flameeyes" Pettenò
2005-03-29 16:56 ` Ciaran McCreesh
2005-03-29 17:13 ` Diego "Flameeyes" Pettenò
2005-03-29 18:04 ` Ciaran McCreesh
2005-03-29 18:18 ` Diego "Flameeyes" Pettenò
2005-03-29 18:16 ` Stephen Bennett
2005-03-29 18:55 ` Ciaran McCreesh
2005-04-06 21:08 ` Luca Barbato
2005-04-06 21:50 ` Diego "Flameeyes" Pettenò
2005-04-07 6:26 ` Brian Harring
2005-04-07 6:33 ` Luca Barbato
2005-04-07 10:22 ` Stroller
2005-04-07 11:04 ` Brian Harring
2005-04-07 12:02 ` Ciaran McCreesh
2005-04-07 12:29 ` Brian Harring
2005-04-07 12:36 ` Alec Warner
2005-04-07 12:46 ` Brian Harring
2005-04-07 12:51 ` Ciaran McCreesh
2005-04-07 13:15 ` Brian Harring
2005-04-07 13:23 ` Ciaran McCreesh
2005-04-07 13:17 ` Stefan Sperling
2005-04-07 13:23 ` Mike Frysinger
2005-04-07 13:57 ` Stefan Sperling
2005-04-07 13:24 ` Ciaran McCreesh
2005-04-07 13:36 ` [gentoo-dev] portage and operating from a non / prefix\x0f; was: " Brian Harring
2005-04-07 13:43 ` Ciaran McCreesh
2005-04-07 13:40 ` [gentoo-dev] " Stefan Sperling
2005-04-07 16:49 ` Lina Pezzella
2005-04-07 12:01 ` Ciaran McCreesh
2005-04-07 12:31 ` Diego "Flameeyes" Pettenò
2005-04-07 12:39 ` Ciaran McCreesh
2005-04-07 16:58 ` Lina Pezzella
2005-04-07 17:02 ` Ciaran McCreesh
2005-04-07 20:57 ` Lina Pezzella
2005-04-07 16:54 ` Lina Pezzella
2005-04-07 15:17 ` Luca Barbato
2005-04-07 15:21 ` Ciaran McCreesh
2005-04-07 15:28 ` Diego "Flameeyes" Pettenò
2005-04-07 15:39 ` Luca Barbato [this message]
2005-04-07 15:51 ` Diego "Flameeyes" Pettenò
2005-04-07 17:03 ` Lina Pezzella
2005-04-07 17:14 ` Luca Barbato
2005-04-07 20:58 ` Lina Pezzella
2005-03-28 17:57 ` Hasan Khalil
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=42555421.2090401@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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