[sleuthkit-developers] Fwd: Re: fiwalk compilation error using --with-libewf parameter
Brought to you by:
carrier
Menu
▾
▴
[sleuthkit-developers] Fwd: Re: fiwalk compilation error using --with-libewf parameter
|
From: Willi B. <wil...@gm...> - 2013-08-05 22:27:37
|
Sorry, meant to reply all.
---------- Forwarded message ----------
From: "Willi Ballenthin" <wil...@gm...>
Date: Aug 5, 2013 6:26 PM
Subject: Re: [sleuthkit-developers] fiwalk compilation error using
--with-libewf parameter
To: "Simson Garfinkel" <si...@ac...>
Cc:
CPPFLAGS are the flags for the C preprocessor, while CXXFLAGS are the flags
for the C++ compiler.
I'm aware that the issue is not visible if libewf is installed in a
standard location, however the documentation describes the optional flag
for LIBEWF_HOME. So, perhaps its a bug with the documentation and the
non-standard library location shouldn't be supported?
Thanks,
Willi
On Aug 5, 2013 6:08 PM, "Simson Garfinkel" <si...@ac...> wrote:
> Possibly the LIBEWF_HOME is apparently in some Makefiles but not others. I
> suspect that the problem will go away of the include file was installed in
> a standard location.
>
> You shouldn't be adding -I to CFLAGS or CXXFLAGS; it should be added to
> CPPFLAGS, since -I is a cpp issue.
>
> I didn't make the current Makefile that fiwalk is using; that was built by
> Kevin Fairbanks. Perhaps he can help.
>
>
>
> [Mucha ~]$ grep -l -r LIBEWF_HOME gits/sleuthkit
> gits/sleuthkit/bindings/java/build-windows.xml
> gits/sleuthkit/framework/INSTALL_win.txt
> gits/sleuthkit/framework/msvcpp/build-deps.pl
> gits/sleuthkit/framework/msvcpp/framework/framework.vcproj
> gits/sleuthkit/framework/msvcpp/framework/framework.vcxproj
> gits/sleuthkit/framework/msvcpp/Makefile
> gits/sleuthkit/release/release-win.pl
> gits/sleuthkit/win32/blkcalc/blkcalc.vcxproj
> gits/sleuthkit/win32/blkcat/blkcat.vcxproj
> gits/sleuthkit/win32/blkls/blkls.vcxproj
> gits/sleuthkit/win32/blkstat/blkstat.vcxproj
> gits/sleuthkit/win32/BUILDING.txt
> gits/sleuthkit/win32/callback-cpp-sample/callback-cpp-sample.vcxproj
> gits/sleuthkit/win32/callback-sample/callback-sample.vcxproj
> gits/sleuthkit/win32/fcat/fcat.vcxproj
> gits/sleuthkit/win32/ffind/ffind.vcxproj
> gits/sleuthkit/win32/fls/fls.vcxproj
> gits/sleuthkit/win32/fsstat/fsstat.vcxproj
> gits/sleuthkit/win32/hfind/hfind.vcxproj
> gits/sleuthkit/win32/icat/icat.vcxproj
> gits/sleuthkit/win32/ifind/ifind.vcxproj
> gits/sleuthkit/win32/ils/ils.vcxproj
> gits/sleuthkit/win32/img_cat/img_cat.vcxproj
> gits/sleuthkit/win32/img_stat/img_stat.vcxproj
> gits/sleuthkit/win32/istat/istat.vcxproj
> gits/sleuthkit/win32/jcat/jcat.vcxproj
> gits/sleuthkit/win32/jls/jls.vcxproj
> gits/sleuthkit/win32/libtsk/libtsk.vcxproj
> gits/sleuthkit/win32/mmcat/mmcat.vcxproj
> gits/sleuthkit/win32/mmls/mmls.vcxproj
> gits/sleuthkit/win32/mmstat/mmstat.vcxproj
> gits/sleuthkit/win32/posix-cpp-sample/posix-cpp-sample.vcxproj
> gits/sleuthkit/win32/posix-sample/posix-sample.vcxproj
> gits/sleuthkit/win32/tsk_comparedir/tsk_compare.vcxproj
> gits/sleuthkit/win32/tsk_gettimes/tsk_gettimes.vcxproj
> gits/sleuthkit/win32/tsk_jni/tsk_jni.vcxproj
> gits/sleuthkit/win32/tsk_loaddb/tsk_loaddb.vcxproj
> gits/sleuthkit/win32/tsk_recover/tsk_recover.vcxproj
> [Mucha ~]$
>
>
> On Aug 5, 2013, at 2:54 PM, Brian Carrier <ca...@sl...> wrote:
>
> > Simson, any ideas on this? I haven't looked at the fiwalk auto stuff
> much.
> >
> > On Jul 30, 2013, at 11:10 PM, Willi Ballenthin <wil...@gm...>
> wrote:
> >
> >> I've been building TSK with libewf support using the --with-libewf
> parameter, but I think there may be a bug in the makefile generated for
> fiwalk. On my Ubuntu/Debian system with both gcc and g++, g++ is chosen to
> compile fiwalk:
> >>
> >> me$ LIBEWF_HOME=$(pwd)/../libewf/build ./configure
> --with-libew$(pwd)/../libewf/build/ --prefix=$(pwd)/build/;
> >> me$ LIBEWF_HOME=$(pwd)/../libewf/build make
> >> ...snip...
> >> g++ -DHAVE_CONFIG_H -I. -I../../../tsk -I../../.. -Wall -g -O2
> -MT fiwalk.o -MD -MP -MF .deps/fiwalk.Tpo -c -o fiwalk.o fiwalk.cpp
> >> In file included from fiwalk.cpp:39:0:
> >> fiwalk.h:94:20: fatal error: libewf.h: No such file or directory
> >> compilation terminated.
> >>
> >> We see from the build step that the libewf include directory is not
> provided. Taking a look at the generated makefile, I have:
> >>
> >> CFLAGS = -g -O2 -pthread -I/usr/local/include
> -I/home/me/Desktop/autopsy-dev/sleuthkit/../libewf/build//include
> >> ...snip...
> >> CXXFLAGS = -g -O2
> >>
> >> I found that by copying the include directive over to the CXXFLAGS
> definition in the fiwalk makefile, the compilation completed successfully.
> >>
> >> Unfortunately, I haven't used Automake before, so I cannot give advice
> confidently. However, by looking at the source files, I conjecture adding a
> line to configure.ac around line 176 will fix the issue:
> >>
> >> AS_IF([test "x$with_libewf" != "xno"],
> >> # Test the dir if they specified something beyond yes/no
> >> [AS_IF([test "x$with_libewf" != "xyes"],
> >> [AS_IF([test -d ${with_libewf}/include],
> >> [CFLAGS="$CFLAGS -I${with_libewf}/include"
> >> CXXFLAGS="$CXXFLAGS -I${with_libewf}/include" #
> <<<<<<< ADD THIS HERE
> >> LDFLAGS="$LDFLAGS -L${with_libewf}/lib"],
> >> # Dir given was not correct
> >> [AC_MSG_FAILURE([libewf directory not found at
> ${with_libewf}])])
> >>
> >> Is this, in fact, a bug, and is the proposed fix reasonable?
> >>
> >> Thanks,
> >> Willi
> >>
> ------------------------------------------------------------------------------
> >> Get your SQL database under version control now!
> >> Version control is standard for application code, but databases havent
> >> caught up. So what steps can you take to put your SQL databases under
> >> version control? Why should you start doing it? Read more to find out.
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> >> sleuthkit-developers mailing list
> >> sle...@li...
> >> https://lists.sourceforge.net/lists/listinfo/sleuthkit-developers
> >
>
>
|
