All of lore.kernel.org
 help / color / mirror / Atom feed
From: cliff white <cliffw@osdl.org>
To: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: gcc confused about static inline. - route.c
Date: Mon, 28 Mar 2005 13:23:14 -0800	[thread overview]
Message-ID: <20050328132314.480b8b1d@es175> (raw)


Building the gkernel bits, have this error:

net/ipv4/route.c: In function `rt_remove_balanced_route':
net/ipv4/route.c:151: sorry, unimplemented: inlining failed in call to 'compare_keys': function body not available
net/ipv4/route.c:540: sorry, unimplemented: called from here

route.c has this define at line 151
:
static inline int compare_keys(struct flowi *fl1, struct flowi *fl2);

function body is defined starting at line 861. 

We are using gcc 3.4.2 right now, is there a way to fix this?
thanks
cliffw

-- 
"Ive always gone through periods where I bolt upright at four in the morning; 
now at least theres a reason." -Michael Feldman

             reply	other threads:[~2005-03-28 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 21:23 cliff white [this message]
2005-03-28 21:41 ` gcc confused about static inline. - route.c Dave Jones
2005-03-28 22:59   ` cliff white
2005-03-28 21:53 ` Francois Romieu
2005-03-28 23:00   ` cliff white

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=20050328132314.480b8b1d@es175 \
    --to=cliffw@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.