TSK Error
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
TSK Error
by KJ #44
::
Rate this Message:
Hello,
I am getting the following error when running make on the TSK: /usr/bin/ld: cannot find -luuid collect2: ld returned 1 exit status make[3]: *** [libtsk3.la] Error 1 make[3]: Leaving directory `/home/kevin/forensic-tools/sleuthkit-3.0.1/tsk3' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/kevin/forensic-tools/sleuthkit-3.0.1/tsk3' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/kevin/forensic-tools/sleuthkit-3.0.1/tsk3' make: *** [all-recursive] Error 1 kevin@helix-box:~/forensic-tools/sleuthkit-3.0.1$ What is -luuid? Any help would be greatly appreciated. Thanks! Kevin ------------------------------------------------------------------------------ _______________________________________________ sleuthkit-users mailing list https://lists.sourceforge.net/lists/listinfo/sleuthkit-users http://www.sleuthkit.org |
|
|
|
|
|
Re: TSK Error
by RB-14
::
Rate this Message:
On Sun, Jun 28, 2009 at 15:49, K-Dawg<kdawg44@...> wrote:
> Well I got it to work. I did an apt-remove libewf and then everything was > fine. I tried to do a apt-get on the package and it said it was obsolete > (?). From what I read, this lib is used with EnCase stuff, which I will not > be using at all, so I should be fine. However, I am confused a bit at why I > still received the error when I did a ./configure --disable-ewf and it did > not go away until I actually removed it. This seems to be an oversight in the Sleuthkit autoconf script. Specifically, by using AC_CHECK_HEADERS it performs a compile check against libewf.h, which will try to link against e2fsprogs-libs for UUID generation. Since libewf.h is present but libuuid.so does not seem to be, you get the edge-case failure. I don't know enough about Helix's specific setup to comment on what space-saving steps they take, but it seems odd that libuuid.so isn't available. Regardless, it's a good illustration of why (generally speaking) LiveCD distributions aren't necessarily good for development work like compiling projects with complex dependencies from source. ------------------------------------------------------------------------------ _______________________________________________ sleuthkit-users mailing list https://lists.sourceforge.net/lists/listinfo/sleuthkit-users http://www.sleuthkit.org |
|
|
Re: TSK Error
by Brian Carrier-2
::
Rate this Message:
On Jun 29, 2009, at 12:07 AM, RB wrote: > On Sun, Jun 28, 2009 at 15:49, K-Dawg<kdawg44@...> wrote: >> Well I got it to work. I did an apt-remove libewf and then >> everything was >> fine. I tried to do a apt-get on the package and it said it was >> obsolete >> (?). From what I read, this lib is used with EnCase stuff, which I >> will not >> be using at all, so I should be fine. However, I am confused a bit >> at why I >> still received the error when I did a ./configure --disable-ewf and >> it did >> not go away until I actually removed it. > > This seems to be an oversight in the Sleuthkit autoconf script. > Specifically, by using AC_CHECK_HEADERS it performs a compile check > against libewf.h, which will try to link against e2fsprogs-libs for > UUID generation. Since libewf.h is present but libuuid.so does not > seem to be, you get the edge-case failure. Shouldn't it be libewf's responsibility to check that it can link against everything? It does not seem scalable to require TSK to verify everything that libewf needs. thanks, brian ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ sleuthkit-users mailing list https://lists.sourceforge.net/lists/listinfo/sleuthkit-users http://www.sleuthkit.org |
|
|
Re: TSK Error
by RB-14
::
Rate this Message:
On Thu, Jul 9, 2009 at 05:36, Brian Carrier<carrier@...> wrote:
> Shouldn't it be libewf's responsibility to check that it can link against > everything? It does not seem scalable to require TSK to verify everything > that libewf needs. Having thought on it more, I don't think it's either TSK's or libewf's responsibility. If libewf were being compiled, then yes - it should (and does) check for its dependencies. The problem arises when the distribution seems to have yanked the previously found dependency out from under libewf post-compile. This, of course, should be validated, but since the OP wasn't clear what version of Helix they were running and I don't have access to Helix3 (which I presume they were running), we're at something of an impasse. The "oversight" statement was an oversight itself, as I was thinking you could do a more cursory check (how, I'm not sure) for libewf.h, but if linking fails during configuration it'll also fail during compilation - a less stringent check would just delay the inevitable. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ sleuthkit-users mailing list https://lists.sourceforge.net/lists/listinfo/sleuthkit-users http://www.sleuthkit.org |
| Free embeddable forum powered by Nabble | Forum Help |
