All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] 64bit-portability-issue
Date: Sat, 28 Dec 2013 15:43:10 +0100	[thread overview]
Message-ID: <52BEE37E.1060600@linux.intel.com> (raw)
In-Reply-To: 52BED799.3020805@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

On 12/28/2013 2:52 PM, denisart benjamin2 wrote:
>
> Hello everyone,
>
> I'm a openSUSE maintainer and I have an issue with powertop 2.5 about
> implicit implementation, classic stdio.h,... Obviously, I tried to patch
> event-parce.c but it doesn't work
>
> I: Program is using implicit definitions of functions getting
>     pointers or implemented by macros. These functions need to use their
>     correct prototypes to allow correct argument passing on e.g. x86_64 .
>     - Implicit memory/string functions need #include <string.h>.
>     - Implicit *printf functions need #include <stdio.h>.
>     - Implicit *printf functions need #include <stdio.h>.
>     - Implicit *read* functions need #include <unistd.h>.
>     - Implicit *recv* functions need #include <sys/socket.h>.
> W: powertop implicit-pointer-decl event-parse.c:856
> E: powertop 64bit-portability-issue event-parse.c:5120
>
adding Steve since this is his upstream code...

btw this code will be a standalone upstream library very soon...
... I assume OpenSUSE will include this library ?


             reply	other threads:[~2013-12-28 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 14:43 Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-28 13:52 [Powertop] 64bit-portability-issue denisart benjamin2

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=52BEE37E.1060600@linux.intel.com \
    --to=powertop@lists.01.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 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.