Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 260074 - app-emacs/mew-6.1 __open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments
Summary: app-emacs/mew-6.1 __open_missing_mode' declared with attribute error: open wi...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Emacs project
URL: http://hardened.gentooexperimental.or...
Whiteboard:
Keywords:
Depends on:
Blocks: fortify-source
  Show dependency tree
 
Reported: 2009-02-23 22:08 UTC by Magnus Granberg
Modified: 2009-02-23 23:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Build log of mew-6.1 (app-emacs_mew-6.1.log,12.96 KB, text/plain)
2009-02-23 22:09 UTC, Magnus Granberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Granberg gentoo-dev 2009-02-23 22:08:56 UTC
Compile with GCC 4.3.3 (FORTIFY_SOURCE=2)
man open:
mode specifies the permissions to use in case a new file is created.  This
argument must be supplied when O_CREAT is specified in flags;


Reproducible: Always

Steps to Reproduce:
1.Compile tha package with gcc 4.3.3 from portage
2.
3.

Actual Results:  
incm.c:640: warning: ignoring return value of 'write', declared with attribute warn_unused_result
In function 'open',
    inlined from 'lock_mbox' at incm.c:630,
    inlined from 'process_mbox' at incm.c:670,
    inlined from 'process' at incm.c:847:
/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments
make[1]: *** [incm.o] Error 1

Expected Results:  
Would compile fine.
Comment 1 Magnus Granberg gentoo-dev 2009-02-23 22:09:38 UTC
Created attachment 182949 [details]
Build log of mew-6.1
Comment 2 Ulrich Müller gentoo-dev 2009-02-23 23:20:45 UTC
Version bumped to 6.2, where the issue should be fixed.
Thanks for reporting it.