From: Christer Solskogen <christer.solskogen@gmail.com>
To: libc-alpha@sourceware.org
Subject: Warnings during make check
Date: Wed, 23 Jun 2021 11:27:34 +0200 [thread overview]
Message-ID: <sauuq6$7a5$1@ciao.gmane.io> (raw)
Hi!
Are these types of warnings OK to ignore or should they be fixed?
Ubuntu 21.04 - gcc version 10.3.0 - binutils 2.36.1 - running "make
check" on glibc master.
/usr/bin/ld: /tmp/glibc-build/stdlib/test-canon2.o: in function
`do_prepare':
/tmp/glibc/stdlib/test-canon2.c:51: warning: the use of `mktemp' is
dangerous, better use `mkstemp' or `mkdtemp'
/usr/bin/ld: /tmp/glibc-build/stdio-common/temptest.o: in function `main':
/tmp/glibc/stdio-common/temptest.c:14: warning: the use of `tempnam' is
dangerous, better use `mkstemp'
/usr/bin/ld: /tmp/glibc-build/stdio-common/tst-tmpnam.o: in function
`do_test':
/tmp/glibc/stdio-common/tst-tmpnam.c:31: warning: the use of `tmpnam' is
dangerous, better use `mkstemp'
/usr/bin/ld: /tmp/glibc-build/stdio-common/tst-gets.o: in function
`do_test':
/tmp/glibc/stdio-common/tst-gets.c:35: warning: the `gets' function is
dangerous and should not be used.
/usr/bin/ld: /tmp/glibc-build/elf/tst-leaks1-static.o: in function
`do_test':
/tmp/glibc/elf/tst-leaks1.c:14: warning: Using 'dlopen' in statically
linked applications requires at runtime the shared libraries from the
glibc version used for linking
/usr/bin/ld: /tmp/glibc-build/elf/tst-ifunc-textrel.o: warning:
relocation in read-only section `.text'
--
chs
next reply other threads:[~2021-06-23 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:27 Christer Solskogen [this message]
2021-06-23 9:30 ` Florian Weimer
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='sauuq6$7a5$1@ciao.gmane.io' \
--to=christer.solskogen@gmail.com \
--cc=libc-alpha@sourceware.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).