#3 [QA] poor programming practices - implicit declaration

closed-fixed
nobody
None
5
2011-01-04
2010-11-19
Anton
No

Please fix the follow warning messages:

>>> Completed installing rdd-3.0.1 into /var/tmp/portage/app-forensics/rdd-3.0.1/image/

* QA Notice: file does not exist:
*
* dodoc: doc/*.txt does not exist
ecompressdir: bzip2 -9 /usr/share/man

* QA Notice: Package has poor programming practices which may compile
* fine but exhibit random runtime failures.
* ewfwriter.c:152: warning: implicit declaration of function ‘libewf_handle_initialize’
* ewfwriter.c:154: warning: implicit declaration of function ‘libewf_error_free’
* ewfwriter.c:173: warning: implicit declaration of function ‘libewf_handle_open’
* ewfwriter.c:183: warning: implicit declaration of function ‘libewf_handle_set_format’
* ewfwriter.c:190: warning: implicit declaration of function ‘libewf_handle_set_media_type’
* ewfwriter.c:197: warning: implicit declaration of function ‘libewf_handle_set_compression_values’
* ewfwriter.c:205: warning: implicit declaration of function ‘libewf_handle_set_segment_file_size’
* ewfwriter.c:224: warning: implicit declaration of function ‘libewf_handle_close’
* ewfwriter.c:225: warning: implicit declaration of function ‘libewf_handle_free’
* ewfwriter.c:243: warning: implicit declaration of function ‘libewf_handle_write_buffer’
* ewfwriter.c:272: warning: implicit declaration of function ‘libewf_handle_set_md5_hash’
* ewfwriter.c:285: warning: implicit declaration of function ‘libewf_handle_set_sha1_hash’
* ewfwriter.c:299: warning: implicit declaration of function ‘libewf_handle_write_finalize’
* ../src/ewfwriter.c:152: warning: implicit declaration of function ‘libewf_handle_initialize’
* ../src/ewfwriter.c:154: warning: implicit declaration of function ‘libewf_error_free’
* ../src/ewfwriter.c:173: warning: implicit declaration of function ‘libewf_handle_open’
* ../src/ewfwriter.c:183: warning: implicit declaration of function ‘libewf_handle_set_format’
* ../src/ewfwriter.c:190: warning: implicit declaration of function ‘libewf_handle_set_media_type’
* ../src/ewfwriter.c:197: warning: implicit declaration of function ‘libewf_handle_set_compression_values’
* ../src/ewfwriter.c:205: warning: implicit declaration of function ‘libewf_handle_set_segment_file_size’
* ../src/ewfwriter.c:224: warning: implicit declaration of function ‘libewf_handle_close’
* ../src/ewfwriter.c:225: warning: implicit declaration of function ‘libewf_handle_free’
* ../src/ewfwriter.c:243: warning: implicit declaration of function ‘libewf_handle_write_buffer’
* ../src/ewfwriter.c:272: warning: implicit declaration of function ‘libewf_handle_set_md5_hash’
* ../src/ewfwriter.c:285: warning: implicit declaration of function ‘libewf_handle_set_sha1_hash’
* ../src/ewfwriter.c:299: warning: implicit declaration of function ‘libewf_handle_write_finalize’
* tewfwriter.c:398: warning: implicit declaration of function ‘libewf_handle_get_media_type’
* tewfwriter.c:407: warning: implicit declaration of function ‘libewf_handle_get_format’
* tewfwriter.c:415: warning: implicit declaration of function ‘libewf_handle_get_compression_values’
* tewfwriter.c:426: warning: implicit declaration of function ‘libewf_handle_get_segment_file_size’
* tewfwriter.c:445: warning: implicit declaration of function ‘libewf_handle_get_md5_hash’
* tewfwriter.c:457: warning: implicit declaration of function ‘libewf_handle_get_sha1_hash’
* tewfwriter.c:472: warning: implicit declaration of function ‘libewf_handle_read_buffer’

* Please do not file a Gentoo bug and instead report the above QA
* issues directly to the upstream developers of this software.
* Homepage: http://www.sf.net/projects/rdd

Discussion

  • rddadmin

    rddadmin - 2011-01-03

    This is probably caused by not having the API v2 available in libewf. Please configure and build libewf with the --enable-v2-api.

     
  • rddadmin

    rddadmin - 2011-01-03
    • status: open --> open-fixed
     
  • Anton

    Anton - 2011-01-04
    • status: open-fixed --> closed-fixed
     
  • Anton

    Anton - 2011-01-04

    I confirm the problem is gone with api v2. Thank you for the hint.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks