From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gnutls fails to compile with error: 'gets' undeclared ?
Date: Wed, 23 Jan 2013 19:15:31 +0100 [thread overview]
Message-ID: <CAB_54W758vqE64oSR5oePBQRqCgb8mfvQhX+-x69uxF_1jB0Sw@mail.gmail.com> (raw)
In-Reply-To: <1408264.f3WDjG5Lnz@dabox>
[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]
Hi,
2013/1/23 Tim Sander <tim@krieglstein.org>
> Hi
>
> I am again using the OSELAS.Toolchain-2012.12.0
> arm-1136jfs-linux-gnueabihf-
> gcc with the extra linker flags: -Wl,--copy-dt-needed-entries. I get a
> little
> further to the gnutls package. It fails to compile with:
> arm-1136jfs-linux-gnueabihf-gcc -DHAVE_CONFIG_H -I. -I.. -I../intl -g -O2
> -MT
> read-file.lo -MD -MP -MF .deps/read-file.Tpo -c read-file.c -fPIC -DPIC -o
> .libs/read-file.o
> In file included from read-file.h:26:0,
> from read-file.c:21:
> ./stdio.h:1030:1: error: 'gets' undeclared here (not in a function)
>
Which gnutls version do you use?
There is already a patch in
patches/gnutls-2.12.20 /
0001-check-if-gets-is-defined-before-doing-something-with.patch
to handle this kind of error.
> The gets is defined in the header with some cxx exeption flag so i tried
> adding
> a --std= option but without any success. But as this header is part of the
> toolchain i guess its a toolchain problem?
>
> Best regards
> Tim
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
[-- Attachment #1.2: Type: text/html, Size: 1743 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-23 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:21 Tim Sander
2013-01-23 18:15 ` Alexander Aring [this message]
2013-01-23 22:51 ` [ptxdist] gnutls fails to compile with error: 'gets' undeclared? Tim Sander
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=CAB_54W758vqE64oSR5oePBQRqCgb8mfvQhX+-x69uxF_1jB0Sw@mail.gmail.com \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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