From f5fc1384e97eb11bf1f0e61308554da5883209d2 Mon Sep 17 00:00:00 2001
From: Rob Landley
Date: Fri, 15 Sep 2006 04:08:25 +0000
Subject: So, in the cornucopia of superfulous warning directives I didn't add
 to the tree, we have the warning about failed inlines (which with our inline
 limit set to zero means any usage of the "inline" keyword at all).  Note that
 setting the inline limit to zero, and using -Werror, both predated adding the
 warning about inlines to the tree.  So whatever checkin added that did
 nothing but break the tree.  But oh well.

The second category of superfluous warnings is warning about functions with
no previous declaration.  Apparently, if you add ALWAYS_INLINE to an empty
function definition, it considers the sucker undeclared as far as the
warning is concerned.  (I.E. it's a buggy warning.  I try not to ask the
compiler to generate warnings it can't competently generate.)

This is why I removed "inline" (unbreak allbareconfig), and couldn't replace it
with "ALWAYS_INLINE" (still broke allbareconfig).
---
 networking/wget.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'networking')

diff --git a/networking/wget.c b/networking/wget.c
index f0ef3e4..181ea93 100644
--- a/networking/wget.c
+++ b/networking/wget.c
@@ -36,7 +36,7 @@ enum {
 	STALLTIME = 5
 };
 #else
-static inline void progressmeter(int flag) {}
+static void progressmeter(int flag) {}
 #endif
 
 static void close_and_delete_outfile(FILE* output, char *fname_out, int do_continue)
-- 
cgit v1.1