Re: libewf support on MacOS X
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
|
|
|
Re: libewf support on MacOS X
by Simson Garfinkel-3
::
Rate this Message:
|
|
|
Re: libewf support on MacOS X
by Brian Carrier-2
::
Rate this Message:
|
|
|
Re: libewf support on MacOS X
by Simson Garfinkel-3
::
Rate this Message:
Hi, Brian,
Actually, if the user specified --prefix=$HOME, my fix handles it. But I agree that it is useful to be able to specify libewf and afflib locations. Simson On Nov 6, 2009, at 12:19 PM, Brian Carrier wrote: > Hi Simson, > > Your fix doesn't solve the problem at hand though. In this case, the > user has installed libewf in his home directory. Adding more system > locations to search won't solve that. I think the existing code > exists because 'configure' was finding libraries that were in > directories that the complier was not configured to look at (and > this fix added those to the build process instead of making the user > change their setup). > > I created issue 2893521 to add a feature to 'configure' so that you > can specify the locations of libewf and afflib if they aren't found > from the search. > > thanks, > brian > > > > > > On Nov 5, 2009, at 11:50 AM, Simson Garfinkel wrote: > >> This is actually pretty standard, Rob. Your problems go away if >> libewf >> is installed in a normal location that TSK's configure file checks. >> >> Currently Sleuthkit only checks /usr/bin and /usr/local/bin: >> >> # Not all compilers include /usr/local in the include and link path >> if test -d /usr/local/include; then >> CFLAGS="$CFLAGS -I/usr/local/include" >> LDFLAGS="$LDFLAGS -L/usr/local/lib" >> fi >> >> AFFLIB tests many additional directories: >> >> # Bring additional directories where things might be found into our >> # search path. I don't know why autoconf doesn't do this by default >> for spfx in /usr/local /opt/local /sw ${prefix} ; do >> echo checking ${spfx}/include >> if test -d ${spfx}/include; then >> CPPFLAGS="-I${spfx}/include $CPPFLAGS" >> LDFLAGS="-L${spfx}/lib $LDFLAGS" >> fi >> done >> >> You might want to ask Brian C. to add my tests to the SleuthKit >> distribution. >> >> Simson >> >> >> On Nov 5, 2009, at 7:36 AM, Rob Joyce wrote: >> >>> I've used CPPFLAGS and LDFLAGS to make SleuthKit link against libewf >>> successfully on OS X. e.g., >>> >>> LDFLAGS="-L/path/to/ewf/lib" CPPFLAGS="-I/path/to/ewf/include" >>> ./configure [options] >>> >>> Not the most elegant, but it works. >>> >>> _Rob >>> >>> >>> ---- >>> >>> Date: Sun, 18 Oct 2009 22:11:43 -0400 >>> From: John Howland <john.d.howland@...> >>> Subject: [sleuthkit-users] libewf support on MacOS X >>> To: sleuthkit-users@... >>> >>> Preface: I'm a total newb; today is my first day playing around with >>> tsk. >>> >>> Two questions: >>> >>> 1. Has anyone successfully built tsk on MacOS X with libewf support? >>> If >>> so, how? >>> >>> I did a plain vanilla source install of libewf on OS X 10.5. I then >>> built tsk, successfully. However, it seems to think E01s are raw >>> images. It looks like configure is at least seeing libewf, given >>> this >>> snippet: >>> >>> ... >>> checking libewf.h usability... yes >>> checking libewf.h presence... yes >>> checking for libewf.h... yes >>> checking for libewf_open in -lewf... no >>> configure: creating ./config.status >>> ... >>> >>> 'img_stat -i list' only gives the following, though: >>> >>> Supported image format types: >>> raw (Single raw file (dd)) >>> split (Split raw files) >>> >>> Any pointers would be much appreciated. >>> >>> 2. This is probably more of a stretch, but is there any way to tell >>> the sleuthkit's configure script to look in a specific directory for >>> the libewf install? For example, I'd like to be able to install >>> tsk+libewf in ~/cftools on systems where I don't have administrative >>> privileges, where ~/cftools would be akin to /usr/local. >>> >>> thanks! >>> >>> John >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and >>> focus on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> sleuthkit-users mailing list >>> https://lists.sourceforge.net/lists/listinfo/sleuthkit-users >>> http://www.sleuthkit.org >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports >> 2008 30-Day >> trial. Simplify your report design, integration and deployment - >> and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> sleuthkit-users mailing list >> https://lists.sourceforge.net/lists/listinfo/sleuthkit-users >> http://www.sleuthkit.org > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ sleuthkit-users mailing list https://lists.sourceforge.net/lists/listinfo/sleuthkit-users http://www.sleuthkit.org |
|
|
Re: libewf support on MacOS X
by John Howland-3
::
Rate this Message:
|
|
|
Re: libewf support on MacOS X
by Brian Carrier-2
::
Rate this Message:
|
|
|
Re: libewf support on MacOS X
by Simson Garfinkel-3
::
Rate this Message:
|
smime.p7s (3K) | Free embeddable forum powered by Nabble | Forum Help |
