From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libssh2: fix build failure due to pointer dereferencing ambiguity
Date: Sun, 16 Sep 2018 16:11:49 +0200 [thread overview]
Message-ID: <20180916161149.3cd01686@windsurf> (raw)
In-Reply-To: <20180913080854.81306-1-giulio.benetti@micronovasrl.com>
Hello,
On Thu, 13 Sep 2018 10:08:54 +0200, Giulio Benetti wrote:
> When dereferencing from *aes_ctr_cipher, being a pointer itself,
> ambiguity can occur with compiler and build can fail reporting:
> openssl.c:574:20: error: ?*aes_ctr_cipher? is a pointer; did you mean to use ?->??
> *aes_ctr_cipher->nid = type;
>
> Add a patch to sorround every *aes_ctr_cipher-> occurence with
> paranthesis like this (*aes_ctr_cipher)->
>
> Fixes:
> http://autobuild.buildroot.net/results/97c/97c43dd2122f55f3166683aa1b29ce1ca54bcb9c/
> http://autobuild.buildroot.net/results/4b7/4b728d275f1399e3cb72d40482076ee54b35852a/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> ...ferencing-ambiguity-potentially-caus.patch | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
> create mode 100644 package/libssh2/0003-openssl-fix-dereferencing-ambiguity-potentially-caus.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-16 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 20:56 [Buildroot] [PATCH 1/1] package/libssh2: bump version Bernd Kuhls
2018-09-12 8:30 ` Thomas Petazzoni
2018-09-12 14:33 ` Thomas Petazzoni
2018-09-13 6:16 ` Bernd Kuhls
2018-09-13 6:56 ` Giulio Benetti
2018-09-13 8:08 ` [Buildroot] [PATCH] libssh2: fix build failure due to pointer dereferencing ambiguity Giulio Benetti
2018-09-16 14:11 ` 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=20180916161149.3cd01686@windsurf \
--to=thomas.petazzoni@bootlin.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