From: L A Walsh <lkml@tlinx.org>
To: util-linux@vger.kernel.org
Subject: FYI...build "ok", thought some warnings, annoyances in 2.32...
Date: Tue, 01 May 2018 21:27:26 -0700 [thread overview]
Message-ID: <5AE93E2E.9040506@tlinx.org> (raw)
Everything seemed to build, though with warnings and some
annoyances.
It _seems_ most of the warnings are of low importance.
At the annoyance level: of the 8 utils I tried to build statically,
0 worked: "complete static linking is impossible in this configuration".
I wonder if this is a 'SUSE-ism'?
(The problem of static building isn't unique to utils-linux, FWIW...)
Thanks!
-linda
output during make of warnings follows:
libblkid/src/superblocks/zfs.c: In function ‘probe_zfs’:
libblkid/src/superblocks/zfs.c:254:14: warning: ‘offset’ may be used
uninitialized in this function [-Wmaybe-uninitialized]
--
libmount/src/monitor.c: In function ‘userspace_monitor_close_fd’:
libmount/src/monitor.c:202:62: warning: unused parameter ‘mn’
[-Wunused-parameter]
--
libmount/src/monitor.c: In function ‘kernel_monitor_close_fd’:
libmount/src/monitor.c:433:59: warning: unused parameter ‘mn’
[-Wunused-parameter]
--
libfdisk/src/sun.c: In function ‘fdisk_new_sun_label’:
libfdisk/src/sun.c:1152:63: warning: unused parameter ‘cxt’
[-Wunused-parameter]
--
libfdisk/src/sgi.c: In function ‘fdisk_new_sgi_label’:
libfdisk/src/sgi.c:1181:63: warning: unused parameter ‘cxt’
[-Wunused-parameter]
--
libfdisk/src/dos.c: In function ‘fdisk_new_dos_label’:
libfdisk/src/dos.c:2467:63: warning: unused parameter ‘cxt’
[-Wunused-parameter]
--
libfdisk/src/bsd.c: In function ‘fdisk_new_bsd_label’:
libfdisk/src/bsd.c:1031:63: warning: unused parameter ‘cxt’
[-Wunused-parameter]
--
libfdisk/src/gpt.c: In function ‘fdisk_new_gpt_label’:
libfdisk/src/gpt.c:3143:63: warning: unused parameter ‘cxt’
[-Wunused-parameter]
--
CCLD losetup.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD mount.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD umount.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD blkid.static
libtool: warning: complete static linking is impossible in this
configuration
--
disk-utils/fdisk.c: In function ‘ask_number’:
disk-utils/fdisk.c:294:11: warning: ‘num’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
--
disk-utils/fdisk.c: In function ‘ask_number’:
disk-utils/fdisk.c:294:11: warning: ‘num’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
--
CCLD fdisk.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD sfdisk.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD unshare.static
libtool: warning: complete static linking is impossible in this
configuration
--
CCLD nsenter.static
libtool: warning: complete static linking is impossible in this
configuration
next reply other threads:[~2018-05-02 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 4:27 L A Walsh [this message]
2018-05-03 8:46 ` FYI...build "ok", thought some warnings, annoyances in 2.32 Karel Zak
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=5AE93E2E.9040506@tlinx.org \
--to=lkml@tlinx.org \
--cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.