Bug 106300 - pine bad source code
pine bad source code
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: pine (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-10-05 04:58 EDT by d.binderman
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-10-05 13:43:30 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 2003-10-05 04:58:31 EDT
Description of problem:

Hello there,

I just tried to compile package pine-4.44-18 from Redhat 9.0
with compiler flag -Wall.

The compiler said

pico_os.c:1120: warning: `0' flag ignored with precision and `%d' printf format
pico_os.c:1154: warning: `0' flag ignored with precision and `%d' printf format
pico_os.c:1336: warning: `0' flag ignored with precision and `%d' printf format
pico_os.c:1349: warning: `0' flag ignored with precision and `%d' printf format
help.c:1346: warning: `0' flag ignored with precision and `%x' printf format
help.c:1533: warning: operation on `i' may be undefined
help.c:1533: warning: operation on `i' may be undefined
help.c:1533: warning: operation on `i' may be undefined

Sounds like a few things worth fixing.



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


How reproducible:


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


Expected results:


Additional info:
Comment 1 Mike A. Harris 2003-10-05 13:43:30 EDT
This is something that should be reported to the University of Washington
pine development team.  Red Hat does not do development on pine.  Currently,
pine has been deprecated from the distribution in rawhide, and will not be
present in future distributions (Fedora Core 1).

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