Re: Lot's of warnings when using GCC 4.0

[Dawid Gajownik]

Dnia 02/22/2005 03:33 AM, Użytkownik Marcus Brinkmann napisał:

> Can you try changing the return type to "const char *" in that file 
> (remove the second const)?

Of cource I can :) It did the trick - it suppressed most of the
warnings: http://80.55.221.90/~gajownik/hurd/diff-gcc4-after-fix.txt
I also changed libl4/l4/syscall.h in the same way, so the output from
the compilation has less warnings and looks like that:
http://80.55.221.90/~gajownik/hurd/hurd-l4-gcc-4.0.0-20050217-fixed2.log
There are still some left:
http://80.55.221.90/~gajownik/hurd/warnings-gcc4.txt
but from what I've read on this list, it's nothing to worry about,
because some parts are not yet implemented, etc.

Thanks!

-- 

  ^_*

Index: libl4/l4/syscall.h
===================================================================
RCS file: /cvsroot/hurd/hurd-l4/libl4/l4/syscall.h,v
retrieving revision 1.6
diff -u -p -r1.6 syscall.h
--- libl4/l4/syscall.h  6 Oct 2004 19:05:43 -0000       1.6
+++ libl4/l4/syscall.h  22 Feb 2005 19:27:29 -0000
@@ -91,7 +91,7 @@
 #define _L4_ERR_NO_MEM                 _L4_WORD_C(8)
 
 
-static inline const char *const
+static inline const char *
 _L4_attribute_always_inline
 _L4_strerror (_L4_word_t err_code)
 {
Index: libl4/l4/gnu/syscall.h
===================================================================
RCS file: /cvsroot/hurd/hurd-l4/libl4/l4/gnu/syscall.h,v
retrieving revision 1.2
diff -u -p -r1.2 syscall.h
--- libl4/l4/gnu/syscall.h      4 Apr 2004 23:39:54 -0000       1.2
+++ libl4/l4/gnu/syscall.h      22 Feb 2005 19:27:29 -0000
@@ -80,7 +80,7 @@
 #define L4_ERR_KIP_AREA                        _L4_ERR_KIP_AREA
 #define L4_ERR_NO_MEM                  _L4_ERR_NO_MEM
 
-static inline const char *const
+static inline const char *
 _L4_attribute_always_inline
 l4_strerror (l4_word_t err_code)
 {

signature.asc
Description: OpenPGP digital signature