From: cliff white <cliffw@osdl.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: gcc confused about static inline. - route.c
Date: Mon, 28 Mar 2005 15:00:13 -0800 [thread overview]
Message-ID: <20050328150013.013b20fc@es175> (raw)
In-Reply-To: <20050328215337.GA14089@electric-eye.fr.zoreil.com>
On Mon, 28 Mar 2005 23:53:37 +0200
Francois Romieu <romieu@fr.zoreil.com> wrote:
> cliff white <cliffw@osdl.org> :
> [...]
> > We are using gcc 3.4.2 right now, is there a way to fix this?
>
> http://marc.theaimsgroup.com/?l=bk-commits-head&m=111188776823016&w=2
>
Whumps.
Thanks, i missed this email.
Didn't know it was already fixed.
cliffw
> --
> Ueimor
>
--
"Ive always gone through periods where I bolt upright at four in the morning;
now at least theres a reason." -Michael Feldman
prev parent reply other threads:[~2005-03-28 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 21:23 gcc confused about static inline. - route.c cliff white
2005-03-28 21:41 ` Dave Jones
2005-03-28 22:59 ` cliff white
2005-03-28 21:53 ` Francois Romieu
2005-03-28 23:00 ` cliff white [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=20050328150013.013b20fc@es175 \
--to=cliffw@osdl.org \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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 NNTP newsgroup(s).