From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] openvmtools: new package
Date: Mon, 15 Sep 2014 15:56:52 +0200 [thread overview]
Message-ID: <20140915155652.5a575f39@free-electrons.com> (raw)
In-Reply-To: <CABbD_XBqsG91xOVimTEXT2rC-=A-E8Jjwt0KH20xrK9hDoOihA@mail.gmail.com>
Dear K?roly Kasza,
On Mon, 15 Sep 2014 15:51:50 +0200, K?roly Kasza wrote:
> Found it.
> This is because of gcc 4.8's intended behaviour on sizeof() function in
> cases when calling on a pointer.
> See https://gcc.gnu.org/gcc-4.8/porting_to.html "New warnings for pointer
> access".
> It also exists as an unconfirmed bug:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54381.
> This behaviour is only gcc 4.8, while 4.9 and pre-4.8 versions shouldn't do
> this (Sourcery uses 4.7 and 4.6, I used the own toolchain w/ 4.9)
>
> On the open-vm-tools mail list, it came up
> http://sourceforge.net/p/open-vm-tools/mailman/message/32550520/ , but they
> used -Wno-sizeof-pointer-memaccess for compilation - basically silencing
> the warning.
>
> Would you recommend using -Wno-sizeof-pointer-memaccess in the .mk file or
> just use a 1 line patch to syncDriverPosix.c - dereferencing
> gRemoteFSTypes[i] with an asterisk?
Thanks for the investigation!
As the solution, I would change the package to not use -Werror. Maybe
it has a configure option to do so? If not, adding one would be good
(so that the patch could potentially be upstreamed), or just changing
the package to not use -Werror at all.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-09-15 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 16:13 [Buildroot] [PATCH v7] openvmtools: new package Karoly Kasza
2014-09-08 9:10 ` Károly Kasza
2014-09-13 21:47 ` Peter Korsgaard
2014-09-14 17:58 ` Károly Kasza
2014-09-15 7:21 ` Thomas Petazzoni
2014-09-15 11:19 ` Károly Kasza
2014-09-15 11:38 ` Thomas Petazzoni
2014-09-15 13:51 ` Károly Kasza
2014-09-15 13:56 ` Thomas Petazzoni [this message]
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=20140915155652.5a575f39@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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