From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: string.h conflicting types warnings
Date: Fri, 20 Aug 1999 01:04:45 -0400 [thread overview]
Message-ID: <19990820010445.A7322@them.org> (raw)
In-Reply-To: <Pine.LNX.3.96.990819141202.8759P-100000@liberty.chnd1.az.home.com>; from Matt Porter on Thu, Aug 19, 1999 at 02:12:33PM -0700
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. ]]
next prev parent reply other threads:[~1999-08-20 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-19 21:12 string.h conflicting types warnings Matt Porter
1999-08-20 5:04 ` Daniel Jacobowitz [this message]
1999-08-20 22:30 ` Matt Porter
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=19990820010445.A7322@them.org \
--to=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).