Package: runit
Version: 2.1.1-6.2
Severity: normal
Dear Maintainer,
if you build runit on a 64-bit system, you'll see a couple of warnings
when compiling utmpset.c:
utmpset.c:38:9: warning: passing argument 1 of ‘time’ from incompatible
pointer type
if (time(&ut.ut_time) == -1) break;
In file included from utmpset.c:2:0:
/usr/include/diet/time.h:44:8: note: expected ‘time_t *’ but
argument is of type ‘int32_t *’
I haven't actually used utmpset since the sad day when I noticed that
runit-run was gone, but I think it's a safe guess that on systems
with the wrong endianness utmpset will write absurd values of ut.ut_time.
No idea if anyone is actually relying on ut_time :)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages runit depends on:
ii procps 1:3.3.9-7
Versions of packages runit recommends:
pn fgetty <none>
Versions of packages runit suggests:
pn socklog-run <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
