All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Benno Schulenberg <bensberg@justemail.net>, Karel Zak <kzak@redhat.com>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [ANNOUNCE] util-linux v2.26-rc2
Date: Thu, 05 Feb 2015 18:11:12 -0600	[thread overview]
Message-ID: <54D406A0.2060904@gmail.com> (raw)
In-Reply-To: <1423172910.109711.223698217.4EC40FCF@webmail.messagingengine.com>

Benno Schulenberg wrote:
>
> On Wed, Feb 4, 2015, at 12:53, Karel Zak wrote:
>>
>> The util-linux release v2.26-rc2 is available at
>>
>>    ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.26
>
> It compiles without error, but shows these warnings along the way:
>
> libfdisk/src/dos.c: In function 'add_partition':
> libfdisk/src/dos.c:1204: warning: format '%ju' expects type 'uintmax_t', but argument 4 has type 'long unsigned int'
>
> sys-utils/ipcs.c: In function ‘do_shm’:
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:241: warning: dereferencing pointer ‘shm_info’ does break strict-aliasing rules
> sys-utils/ipcs.c:223: note: initialized from here
>
> sys-utils/ipcutils.c: In function ‘ipc_shm_get_limits’:
> sys-utils/ipcutils.c:92: warning: dereferencing pointer ‘shminfo’ does break strict-aliasing rules
> sys-utils/ipcutils.c:91: warning: dereferencing pointer ‘shminfo’ does break strict-aliasing rules
> sys-utils/ipcutils.c:90: warning: dereferencing pointer ‘shminfo’ does break strict-aliasing rules
> sys-utils/ipcutils.c:89: note: initialized from here

You do not say what compiler or architecture you are using.  I am using 
gcc-4.9.2 and both sys-utils/ipcs.c and sys-utils/ipcutils.c build for 
me without any warnings.

My build of dos.c is done with:

/bin/sh ./libtool  --tag=CC   --mode=compile gcc -std=gnu99 
-DHAVE_CONFIG_H -I.  -include config.h -I./include 
-DLOCALEDIR=\"/usr/share/locale\" -D_PATH_LOCALSTATEDIR=\"/run\" 
-I./libuuid/src -I./libfdisk/src -I./libfdisk/src -I./libblkid/src -g 
-O2 -MT libfdisk/src/libfdisk_la-dos.lo -MD -MP -MF 
libfdisk/src/.deps/libfdisk_la-dos.Tpo -c -o 
libfdisk/src/libfdisk_la-dos.lo `test -f 'libfdisk/src/dos.c' || echo 
'./'`libfdisk/src/dos.c

and it does not provide any warnings either.

My host is a Intel(R) Core(TM) i7.

   -- Bruce

  reply	other threads:[~2015-02-06  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 11:53 [ANNOUNCE] util-linux v2.26-rc2 Karel Zak
2015-02-05 21:48 ` Benno Schulenberg
2015-02-06  0:11   ` Bruce Dubbs [this message]
2015-02-06  9:37   ` Karel Zak
2015-02-15 20:02 ` Benno Schulenberg
2015-02-15 20:50   ` Ruediger Meier
2015-02-15 21:21     ` Benno Schulenberg
2015-02-15 21:27     ` Bruce Dubbs
2015-02-15 21:20   ` Bruce Dubbs

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=54D406A0.2060904@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=bensberg@justemail.net \
    --cc=kzak@redhat.com \
    --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.