Bug 115164 - Missing -Wformat flag on compilation ?
Missing -Wformat flag on compilation ?
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: mgetty (Show other bugs)
1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-07 09:22 EST by d.binderman
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-20 14:41:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description d.binderman 2004-02-07 09:22:08 EST
Description of problem:

I just tried to compile package mgetty-1.1.30-4 from Fedora.

The compiler said

1.

locks.c(193): warning #267: the format string requires additional
arguments

The source code is

        lprintf( L_ERROR, "can't open %d for read/write" );

Missing trailing parameter.

2.

shell.c(33): warning #268: the format string ends before this argument

The source code is

          lprintf(L_MESG, "%s: Executing shell %s", program_name,
shell_script,
cvd.voice_shell.d.p);

Two %s, three parameters.

3.

answer.c(578): warning #267: the format string requires additional
arguments

The source code is

               lprintf(L_WARN, "%s: Beep command failed");

Duplicate.

4.

answer.c(757): warning #267: the format string requires additional
arguments

Source code is

                    lprintf(L_WARN, "%s: Beep command failed");

Duplicate.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jason Vas Dias 2004-08-20 14:41:38 EDT
Just clearing out old bugs here.
This is now fixed in mgetty-1.1.31-2 
(printf statements now supply correct number of arguments).

Note You need to log in before you can comment on or make changes to this bug.