From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Cc: Akira Fujita <a-fujita@rs.jp.nec.com>,
Takashi Sato <t-sato@yk.jp.nec.com>
Subject: [LTP] ext4/e4defrag.c testcases compilation error
Date: Tue, 23 Mar 2010 14:50:22 +0530 [thread overview]
Message-ID: <20100323092022.GD4384@linux.vnet.ibm.com> (raw)
Hi,
While building ext4 testcases i am getting following error, let me know if
anyone aware about this with handy solution, else will work later today on this.
gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
-I/root/ltp-dev-next/testcases/kernel/include -I../../../../../include
-I../../../../../include -L../../../../../lib e4defrag.c -lltp -lm -o
e4defrag
e4defrag.c:165: error: expected specifier-qualifier-list before ‘__u64’
e4defrag.c:179: error: expected specifier-qualifier-list before ‘__u64’
e4defrag.c:185: error: expected specifier-qualifier-list before ‘__s32’
e4defrag.c:194: error: expected specifier-qualifier-list before ‘__u64’
e4defrag.c:206: error: expected specifier-qualifier-list before ‘__u64’
e4defrag.c:224: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘__le16’
e4defrag.c:225: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘__le32’
e4defrag.c:226: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘__le64’
e4defrag.c:232: error: expected specifier-qualifier-list before ‘__le32’
e4defrag.c:331: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘log_groups_per_flex’
e4defrag.c:332: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘blocks_per_group’
e4defrag.c:333: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘feature_incompat’
e4defrag.c:342: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before
‘ext2fs_swab32’
e4defrag.c: In function ‘page_in_core’:
e4defrag.c:541: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c:542: error: ‘struct move_extent’ has no member named ‘len’
e4defrag.c: In function ‘defrag_fadvise’:
e4defrag.c:588: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c: In function ‘file_frag_count’:
e4defrag.c:667: error: ‘struct fiemap’ has no member named ‘fm_start’
e4defrag.c:668: error: ‘struct fiemap’ has no member named ‘fm_length’
e4defrag.c:669: error: ‘struct fiemap’ has no member named ‘fm_flags’
e4defrag.c:675: error: ‘struct fiemap’ has no member named ‘fm_mapped_extents’
e4defrag.c: In function ‘insert_extent_by_logical’:
e4defrag.c:766: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:766: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:768: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:769: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:769: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:777: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:777: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:781: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:782: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:783: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:788: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:789: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:789: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c: In function ‘insert_extent_by_physical’:
e4defrag.c:824: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:824: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:826: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:827: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:827: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:835: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:835: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:839: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:840: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:841: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:846: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:847: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:847: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c: In function ‘join_extents’:
e4defrag.c:899: error: ‘__u64’ undeclared (first use in this function)
e4defrag.c:899: error: (Each undeclared identifier is reported only once
e4defrag.c:899: error: for each function it appears in.)
e4defrag.c:899: error: expected ‘;’ before ‘len’
e4defrag.c:909: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:910: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:911: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:919: error: ‘struct fiemap_extent_group’ has no member named ‘len’
e4defrag.c:919: error: ‘len’ undeclared (first use in this function)
e4defrag.c:920: error: ‘struct fiemap_extent_group’ has no member named ‘start’
e4defrag.c:921: error: ‘struct fiemap_extent_group’ has no member named ‘end’
e4defrag.c:929: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:938: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c: In function ‘get_file_extents’:
e4defrag.c:953: error: ‘__u32’ undeclared (first use in this function)
e4defrag.c:953: error: expected ‘;’ before ‘i’
e4defrag.c:956: error: ‘__u64’ undeclared (first use in this function)
e4defrag.c:956: error: expected ‘;’ before ‘pos’
e4defrag.c:975: error: ‘struct fiemap’ has no member named ‘fm_extents’
e4defrag.c:977: error: ‘struct fiemap’ has no member named ‘fm_length’
e4defrag.c:978: error: ‘struct fiemap’ has no member named ‘fm_flags’
e4defrag.c:979: error: ‘struct fiemap’ has no member named ‘fm_extent_count’
e4defrag.c:982: error: ‘struct fiemap’ has no member named ‘fm_start’
e4defrag.c:982: error: ‘pos’ undeclared (first use in this function)
e4defrag.c:987: error: ‘i’ undeclared (first use in this function)
e4defrag.c:987: error: ‘struct fiemap’ has no member named ‘fm_mapped_extents’
e4defrag.c:993: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:995: error: ‘struct fiemap_extent_data’ has no member named ‘logical’
e4defrag.c:997: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:1008: error: ‘struct fiemap_extent’ has no member named ‘fe_logical’
e4defrag.c:1009: error: ‘struct fiemap_extent’ has no member named ‘fe_length’
e4defrag.c:1014: error: ‘struct fiemap’ has no member named ‘fm_mapped_extents’
e4defrag.c:1016: error: ‘struct fiemap_extent’ has no member named ‘fe_flags’
e4defrag.c: In function ‘get_physical_count’:
e4defrag.c:1055: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:1055: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:1056: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c: In function ‘get_superblock_info’:
e4defrag.c:1198: error: ‘SUPERBLOCK_OFFSET’ undeclared (first use in this
function)
e4defrag.c: In function ‘get_best_count’:
e4defrag.c:1224: error: ‘feature_incompat’ undeclared (first use in this
function)
e4defrag.c:1225: error: ‘log_groups_per_flex’ undeclared (first use in this
function)
e4defrag.c:1227: error: ‘blocks_per_group’ undeclared (first use in this
function)
e4defrag.c: In function ‘file_statistic’:
e4defrag.c:1369: error: ‘struct fiemap_extent_data’ has no member named
‘physical’
e4defrag.c:1370: error: ‘struct fiemap_extent_data’ has no member named
‘logical’
e4defrag.c:1371: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c: In function ‘call_defrag’:
e4defrag.c:1493: error: ‘struct move_extent’ has no member named ‘donor_fd’
e4defrag.c:1500: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c:1500: error: ‘struct fiemap_extent_data’ has no member named
‘logical’
e4defrag.c:1502: error: ‘struct move_extent’ has no member named ‘donor_start’
e4defrag.c:1502: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c:1503: error: ‘struct move_extent’ has no member named ‘len’
e4defrag.c:1503: error: ‘struct fiemap_extent_data’ has no member named ‘len’
e4defrag.c:1504: error: ‘struct move_extent’ has no member named ‘moved_len’
e4defrag.c:1550: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c:1550: error: ‘struct move_extent’ has no member named ‘moved_len’
e4defrag.c:1551: error: ‘struct move_extent’ has no member named ‘donor_start’
e4defrag.c:1551: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c:1553: error: ‘struct move_extent’ has no member named ‘orig_start’
e4defrag.c: In function ‘file_defrag’:
e4defrag.c:1723: error: ‘struct fiemap_extent_group’ has no member named ‘start’
e4defrag.c:1724: error: ‘struct fiemap_extent_group’ has no member named ‘len’
e4defrag.c: In function ‘main’:
e4defrag.c:1879: error: ‘blocks_per_group’ undeclared (first use in this
function)
e4defrag.c:1880: error: ‘feature_incompat’ undeclared (first use in this
function)
e4defrag.c:1881: error: ‘log_groups_per_flex’ undeclared (first use in this
function)
e4defrag.c:1961: error: ‘struct ext4_super_block’ has no member named
‘s_blocks_per_group’
e4defrag.c:1962: error: ‘struct ext4_super_block’ has no member named
‘s_feature_incompat’
e4defrag.c:1963: error: ‘struct ext4_super_block’ has no member named
‘s_log_groups_per_flex’
make[1]: *** [e4defrag] Error 1
make[1]: Leaving directory
`/root/ltp-dev-next/testcases/kernel/fs/ext4-new-features/ext4-online-defrag'
make: *** [all] Error 2
--
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-03-23 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:20 Rishikesh K Rajak [this message]
2010-03-23 16:41 ` [LTP] ext4/e4defrag.c testcases compilation error Garrett Cooper
2010-03-23 19:44 ` Subrata Modak
2010-03-26 4:56 ` Rishikesh K Rajak
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=20100323092022.GD4384@linux.vnet.ibm.com \
--to=risrajak@linux.vnet.ibm.com \
--cc=a-fujita@rs.jp.nec.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=t-sato@yk.jp.nec.com \
/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.