From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: newlib-cygwin build fails on dumper
Date: Thu, 14 Mar 2024 10:10:51 -0600 [thread overview]
Message-ID: <9599b8e1-6d67-4b00-b7af-c412298d78af@SystematicSW.ab.ca> (raw)
Hi folks,
During newlib-cygwin build to test patches, with latest current stable packages
as of last weekend, and yesterday's repo main/master, get a warning, then errors
building dumper:
...
CC libc/reent/libc_a-getentropyr.o
/usr/src/newlib-cygwin/newlib/libc/reent/getentropyr.c: In function ‘_getentropy_r’:
/usr/src/newlib-cygwin/newlib/libc/reent/getentropyr.c:48:14: warning: implicit
declaration of function ‘_getentropy’; did you mean ‘getentropy’?
[-Wimplicit-function-declaration]
48 | if ((ret = _getentropy (buf, buflen)) == -1 && errno != 0)
| ^~~~~~~~~~~
| getentropy
...
CXX dumper-dumper.o
In file included from /usr/src/newlib-cygwin/winsup/utils/dumper.cc:23:
/usr/include/bfd.h:2748:1: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2748 | ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bfd.h:2751:1: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2751 | ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bfd.h:2753:27: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2753 | file_ptr bfd_tell (bfd *) ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bfd.h:2757:37: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2757 | int bfd_stat (bfd *, struct stat *) ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bfd.h:2759:37: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2759 | int bfd_seek (bfd *, file_ptr, int) ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bfd.h:2770:1: error: expected initializer before
‘ATTRIBUTE_WARN_UNUSED_RESULT’
2770 | ATTRIBUTE_WARN_UNUSED_RESULT;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[5]: *** [Makefile:782: dumper-dumper.o] Error 1
make[5]: Leaving directory '/usr/src/build64/x86_64-pc-cygwin/winsup/utils'
...
$ uname -srvmo
CYGWIN_NT-10.0-19045 3.5.1-1.x86_64 2024-02-27 11:54 UTC x86_64 Cygwin
$ cygcheck -c `sed 's!,!!g' <<< 'binutils, cygwin, libgcc1, libintl8, libzstd1,
zlib0, autoconf, automake, cocom, cygport, dblatex, dejagnu, docbook-xml45,
docbook-xsl, docbook2X, gcc-g++, gettext-devel, libiconv, libiconv-devel,
libzstd-devel, make, mingw64-x86_64-gcc-g++, mingw64-x86_64-zlib, patch, perl,
python39-lxml, python39-ply, texlive-collection-fontsrecommended,
texlive-collection-latexrecommended, texlive-collection-pictures, xmlto,
zlib-devel'`
Cygwin Package Information
Package Version Status
autoconf 15-2 OK
automake 11-1 OK
binutils 2.42-1 OK
cocom 0.996-2 OK
cygport 0.36.8-1 OK
cygwin 3.5.1-1 OK
dblatex 0.3.12-2 OK
dejagnu 1.6.3-1 OK
docbook-xml45 4.5-1 OK
docbook-xsl 1.77.1-1 OK
docbook2X 0.8.8-1 OK
gcc-g++ 11.4.0-1 OK
gettext-devel 0.22.4-1 OK
libgcc1 11.4.0-1 OK
libiconv 1.17-1 OK
libiconv-devel 1.17-1 OK
libintl8 0.22.4-1 OK
libzstd-devel 1.5.5-1 OK
libzstd1 1.5.5-1 OK
make 4.4.1-2 OK
mingw64-x86_64-gcc-g++ 11.4.0-1 OK
mingw64-x86_64-zlib 1.3.1-1 OK
patch 2.7.6-17 OK
perl 5.36.3-1 OK
python39-lxml 4.7.1-1 OK
python39-ply 3.11-3 OK
texlive-collection-fontsrecommended 20230313-1 OK
texlive-collection-latexrecommended 20230313-1 OK
texlive-collection-pictures 20230313-1 OK
xmlto 0.0.28-1 OK
zlib-devel 1.3.1-1 OK
zlib0 1.3.1-1 OK
Any ideas what might be going wrong here or what I may be missing?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2024-03-14 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 16:10 Brian Inglis [this message]
2024-03-15 9:10 ` Corinna Vinschen
2024-03-15 16:51 ` Brian Inglis
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=9599b8e1-6d67-4b00-b7af-c412298d78af@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/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).