bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: Debian Stretch: strndup.c build failure
Date: Tue, 7 Jan 2020 20:32:17 +0100	[thread overview]
Message-ID: <f664e62a-b1c9-c104-a624-90251df2d6dd@gmx.de> (raw)
In-Reply-To: <16795352.Q8omOGnAUH@omega>


[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]

Hi Bruno,

On 07.01.20 19:00, Bruno Haible wrote:
>> with the latest gnulib (a7903da07d3d18c23314aa0815adbb4058fd7cec) on
>> Debian Stretch:
>>
>> In file included from /usr/include/string.h:630:0,
>>                  from ./string.h:41,
>>                  from strndup.c:21:
>> strndup.c:26:1: error: expected identifier or '(' before '__extension__'
>>  strndup (char const *s, size_t n)
>>  ^
>>
>> config.log is at
>> https://gitlab.com/gnuwget/wget2/-/jobs/395706872/artifacts/file/config.log.
> 
> An invocation of AC_CHECK_FUNC is malfunctioning because of -Werror:
> 
> For this reason, -Werror is not supported at configuration-time in gnulib [1].
> 
> [1] https://lists.gnu.org/archive/html/bug-gnulib/2019-07/msg00081.html

Thanks for clarification :-)

Regards, Tim


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-01-07 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 14:24 Debian Stretch: strndup.c build failure Tim Rühsen
2020-01-07 15:41 ` Tim Rühsen
2020-01-07 18:00 ` Bruno Haible
2020-01-07 19:32   ` Tim Rühsen [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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f664e62a-b1c9-c104-a624-90251df2d6dd@gmx.de \
    --to=tim.ruehsen@gmx.de \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).