Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-04-11
Date: Tue, 12 Apr 2016 12:16:47 +0100	[thread overview]
Message-ID: <570CD91F.5010504@imgtec.com> (raw)
In-Reply-To: <20160412063023.99284102755@stock.ovh.net>

Hello everyone,

On 12/04/16 07:30, Thomas Petazzoni wrote:
> Build statistics for 2016-04-11

>     mips64el |                   stunnel-5.31 | NOK | http://autobuild.buildroot.net/results/b5d7902ac070c66bb39fa17579628f814d95c11d/

the error looks like this:

prototypes.h:628:5: error: conflicting types for 'getnameinfo'

This is because getnameinfo() is redefined. It's already provided by the
toolchain, and stunnel tries to provide it as well.

The configure script checks if the toolchain already provides
getnameinfo() in order to not redefine it. So, why that check doesn't work?

It doesn't work because when the compiler is called in order to perform
the check, some unsupported flags are passed to it. The offending flags
are the ones related to stack smashing protection, which is unsupported
in the IMG Codescape toolchain used in that build. Then the check fails
due to that reason, and stunnel thinks that the toolchain doesn't
provide getnameinfo() therefore it defines its own.

So, the real problem is that stunnel thinks the toolchain has SSP
support when it actually doesn't have it.

The following patch fixes the problem:

http://patchwork.ozlabs.org/patch/597701/

Regards,

Vincent.

      reply	other threads:[~2016-04-12 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-04-11 Thomas Petazzoni
2016-04-12 11:16 ` Vicente Olivert Riera [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=570CD91F.5010504@imgtec.com \
    --to=vincent.riera@imgtec.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