string.h conflicting types warnings

string.h conflicting types warnings

[Matt Porter]

Hi,
                     
I'm working on a standalone driver and have been running into these
warnings lately.  Whilst compiling Mac-on-Linux I also got these
warnings as well.  Searching around I only found some netbsd folks
gettings these same warnings.  Anyone have an idea where this comes from? 
                     
Thanks - Matt
                     
------------
                    
cc -DLINUX -D__KERNEL__ -DMODULE -Wall -O2 -I/usr/include  -I.  -c
stack_linux.c -o stack_linux.o
In file included from /usr/include/linux/signal.h:64,
                 from /usr/include/linux/sched.h:23,
                 from cnet_linux.h:52,
                 from globals.h:200,
                 from stack_linux.c:39:
/usr/include/linux/string.h:31: warning: conflicting types for built-in
function `memset'
/usr/include/linux/string.h:32: warning: conflicting types for built-in
function `memcpy'
/usr/include/linux/string.h:35: warning: conflicting types for built-in
function `memcmp'

--
Matt Porter
mmporter@home.com
This is Linux Country. On a quiet night, you can hear Windows reboot.


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: string.h conflicting types warnings

[Daniel Jacobowitz]

On Thu, Aug 19, 1999 at 02:12:33PM -0700, Matt Porter wrote:
> 
> Hi,
>                      
> I'm working on a standalone driver and have been running into these
> warnings lately.  Whilst compiling Mac-on-Linux I also got these
> warnings as well.  Searching around I only found some netbsd folks
> gettings these same warnings.  Anyone have an idea where this comes from? 

> /usr/include/linux/string.h:31: warning: conflicting types for built-in
> function `memset'

Easy.  Anything that is including linux/string.h should be a module -
otherwise it needs to rearrange its choice of include files.  Any
module should use the settings from the kernel makefiles, which
include:
 -mmultiple -mstring -ffixed-r2 -fno-builtins

It's that last one you really want.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: string.h conflicting types warnings

[Matt Porter]

On Fri, 20 Aug 1999, Daniel Jacobowitz wrote:
> On Thu, Aug 19, 1999 at 02:12:33PM -0700, Matt Porter wrote:
> > I'm working on a standalone driver and have been running into these
> > warnings lately.  Whilst compiling Mac-on-Linux I also got these
> > warnings as well.  Searching around I only found some netbsd folks
> > gettings these same warnings.  Anyone have an idea where this comes from? 
> 
> > /usr/include/linux/string.h:31: warning: conflicting types for built-in
> > function `memset'
> 
> Easy.  Anything that is including linux/string.h should be a module -
> otherwise it needs to rearrange its choice of include files.  Any
> module should use the settings from the kernel makefiles, which
> include:
>  -mmultiple -mstring -ffixed-r2 -fno-builtins
> 
> It's that last one you really want.

That's it.   Only difference is that it is actually "-fno-builtin" for
anybody else reading this...  
 
Thanks,

--
Matt Porter                                       Motorola Computer Group
matt_porter@mcg.mot.com                           CIBU Linux Support


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]