Rekall is a database front-end. It is not itself a database -- data is stored somewhere else, in an SQL server, and Rekall is fundamentally just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and so on). It is database agnostic, and does not have any preferred database in the sense that Access
Rekall is a database front-end. It is not itself a database -- data is stored somewhere else, in an SQL server, and Rekall is fundamentally just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and so on). It is database agnostic, and does not have any preferred database in the sense that Access® uses the Jet® database engine. This <a href="http://forums.gentoo.org/viewtopic.php?t=108035">discussion</a> on the Gentoo forums provides a sample ebuild.
please attach an ebuild
Created attachment 21173 [details] rekall-2.2.0_beta0.ebuild for +xbase support the ebuilds in Bug 34108 are necessary
Created attachment 21174 [details] doc-rekall-Makefile.in.diff - patch needed for rekall ebuild
Created attachment 21175 [details, diff] doc-rekall-Makefile.am.diff - patch needed for rekall ebuild
Rekall won't build with Python 2.3.2. This, and fixing the dependency on python works for me: sed -i -e 's:python |:python2.2 |:' configure Also, I get a runtime error when setting up a database. It won't find the mysql lib for me. I'm using dev-db/mysql-4.0.13-r3
I had to add the symlinks libkbase_driver_mysql..so -> libkbase_driver_mysql.so.0.0.0 and libkbase_driver_pgsql..so -> libkbase_driver_pgsql.so in /usr/lib to make the database-drivers work. And i am still having only the "Servers"-Tab in the "Objects"-Panel (no Tables, Queries, etc ...)
Rob: I forgot adding --enable-dynamic-python. >And i am still having only the "Servers"-Tab in the "Objects"-Panel Hm, empty db or something like this? I opened an existing mysql db and don't miss any 'object'. Do you get any error messages when executing rekall from cmd? The symlinks for mysql exist here, but not for pgsql.
Hokay, briefly; this is what has been fixed as of rekall-2.2.0-beta0-4 (this ebuild is for beta0) The whole 'libkbase_(mysql|postgres)' driver not found thing is caused by a bug in qt-3.1; Basically qt 3.1's QLibrary instantition method is screwed up. The Makefile.(am|in) patches aren't needed- the $(SGMLPFX) bug has been fixed as of beta0-4. Further, removing line '$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)...' isn't the correct way of doing it- documentation still needs a common dir. Even w/ the common dir being installed (by changing '$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common' to '$(LN_S) common'), the documentation isn't installed correctly- no HTML, just sgml. I'm working on a fix for that at the moment... Finally, the python-2.3 issues should now be fixed also. I'll upload a correct ebuild once I've completed testing and fixed the html documentation installation. If you'ver created the libkbase_*_driver..so symlink, please remove it after upgrading- it's not the correct way of doing it, and further, portage won't remove it on it's own.
Forgot to mention, for beta0-4, the code has been switched to use KdeLoad instead of QLibrary; that effectively fixes the qt-3.1 bug people where having.
Brian: Sorry for this quick & dirty ebuild. ;) I just thought someone would come along with ideas about the sgml/html thing and maybe some input about qt only compilation, because I don't have machine with qt but not kde here.
Created attachment 21884 [details] rekall-2.2.0_beta04.ebuild If there is anyone willing to test, here's an updated ebuild with the fixes mentioned by Brian. Also removed these CVS directories all over the tree.
I get the following using the latest ebuild: /bin/sh ../../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I./../tkkde -I/usr/kde/3.1/include -I/usr/qt/3/include -I/usr/X11R6/include -D__KB_KDE=0 -D__KB_TKC=1 -D__KB_EMBEDDED=0 -DROOTDIR=\"\" -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -DNDEBUG -DNO_DEBUG -O2 -march=athlon-xp -O3 -mfpmath=sse -pipe -fno-exceptions -fno-check-new -c -o kb_database.lo `test -f 'kb_database.cpp' || echo './'`kb_database.cpp rm: cannot remove `': Invalid argument kb_serverinfo.cpp: In function `KBFactory* getDriverFactory(const QString&)': kb_serverinfo.cpp:82: `KBLibLoader' undeclared (first use this function) kb_serverinfo.cpp:82: (Each undeclared identifier is reported only once for each function it appears in.) kb_serverinfo.cpp:82: `loader' undeclared (first use this function) kb_serverinfo.cpp:82: syntax error before `::' token kb_serverinfo.cpp:83: `KBLibrary' undeclared (first use this function) kb_serverinfo.cpp:83: `lib' undeclared (first use this function) kb_serverinfo.cpp:108: invalid use of undefined type `struct KBFactory' kb_classes.h:140: forward declaration of `struct KBFactory' kb_serverinfo.cpp: In function `KBDBAdvanced* getDriverAdvanced(const QString&)': kb_serverinfo.cpp:125: invalid use of undefined type `struct KBFactory' kb_classes.h:140: forward declaration of `struct KBFactory' kb_serverinfo.cpp: In function `KBServer* getDriverServer(const QString&)': kb_serverinfo.cpp:137: invalid use of undefined type `struct KBFactory' kb_classes.h:140: forward declaration of `struct KBFactory' kb_serverinfo.cpp: In member function `KBServer* KBServerInfo::getServer(KBError&)': kb_serverinfo.cpp:667: invalid use of undefined type `struct KBFactory' kb_classes.h:140: forward declaration of `struct KBFactory' make[3]: *** [kb_serverinfo.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory `/var/tmp/portage/rekall-2.2.0_beta04/work/rekall-2.2.0-beta0-4/libs/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/rekall-2.2.0_beta04/work/rekall-2.2.0-beta0-4/libs' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/rekall-2.2.0_beta04/work/rekall-2.2.0-beta0-4' make: *** [all] Error 2 !!! ERROR: dev-db/rekall-2.2.0_beta04 failed. !!! Function kde_src_compile, Line 137, Exitcode 2 !!! died running emake, kde_src_compile:make
Graeme: If you don't have +kde USE flag included, it is more or less expected to fail. Have you?
Haha, that's what happens when I try to get things done late at night. Yeah, it build fine with the KDE use flag.
Created attachment 22604 [details] rekall 2.2.0-beta1 ebuild Nothing too special to it. Specific broken parts of it still. /usr/share/doc/HTML/en/rekall/ should have HTML installed into it- sgml is all good and nice, but HTML is the intention... haven't fixed it yet, been too busy. I'd suggest hard dep'ing this ebuild to kde, rather then qt. I've yet to get rekall working correctly linked just against qt. Only other change was removal of the equivalent find ${D} -type -d -name CVS -exec rm {} \; from the ebuild- it isn't needed, merely unused dirs/files.
Created attachment 22605 [details] the *correct* 2.2.0_beta1 ebuild I meant to upload the first time... Pardon, uploaded wrong ebuild. gah. So yeah, python has been pushed back to 2.1.3 in this- I've gotten it working back to 2.1.3, although via the rekall ml I've heard people doing it as far back as 1.5. YMMV however.
>I'd suggest hard dep'ing this ebuild to kde, rather then qt. Me too, but there are requests in forums.g.o about a non-kde version. ( http://forums.gentoo.org/viewtopic.php?t=108035 )
Doesn't build with USE="-kde": checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! !!! ERROR: app-office/rekall-2.2.0_beta1 failed. !!! Function kde_src_compile, Line 117, Exitcode 1 !!! died running ./configure, kde_src_compile:configure
I was able to successfully emerge the ebuild and connect to a mysql database on localhost. Beyond that I haven't done much more. See http://gentoo-mp.blogspot.com/ for the steps I followed.
This ebuild works w/ one caveat- qt support _does not_ work, and is related to the src. I've been using this ebuild w/ a few modifications (mainly w/ strip'ing disabled and --enable-debug=full), and have yet to crash it against kde. I'd be up for adding this to the tree keyworded ~x86 if the qt use flag was removed and it was dep'd against kde. Currently qt only compilation doesn't work, and won't with modifications imo. Thoughts? This is somewhat debatable to add into the tree due to some issues w/ postgres support (check the rekall and rekall-dev mailing list archives if your curious about them). At the moment I've been working at getting rekall going w/ OSX, once I'm done w/ that I was hoping to do some work to fix the qt only support.
Sorry Brian, but I "lost" this bug. I'm not subscribed to the mailing lists, so I don't know, if there is any progress. Beta 3 compiles fine (kde gui) and as long no one wants to fix the --with-gui=qt3 stuff, I'm fine to drop it. But I think the xbase ebuilds, I made (Bug 34108) should be incorporated into the rekall ebuild. No other application needs them. What do you think?
No problem, I've been attempting to get rekall up and running on osx in the meantime :) Combining xbase into rekall makes sense, although we'll run into the bonobo-activation type annoyance if they ever need to be split out. It also may be a wee bit tricky getting rekall to compile w/ xbase along the way- rekalls configuration/build expects xbase to be installed already. Probably easy to step around, but worth noting. There still is a few issues w/ beta3- the configure options for pgsql include/libraries is kinda-sort broken (./configure --help lists --with-pgsql-libraries, when it's currently --with-pgsqllibdir). Also, if the user enables pgsql/mysql, rekall's configure will disable that db support if the configuration test fails, rather then throwing a fit and stopping. I've submitted a patch to rekall-dev that enables configure to throw a fit if a db plugin is explicitly enabled, but unable to be configured. Aside from that, I've started looking into qt only support- doesn't mean I've made any headway :) By chance, did you have any complaints from the doc compilation? Last I tried a vanilla beta3, it crapped out w/ a docs complaint. The source I'm playing with isn't complaining about it, but that's not saying I've fixed the problem... Aside from that, the admin.(kde/qt)3/detect-autoconf.sh are a bit behind in automake/autoconf versions. The only time it will be an issue is if the ebuild ever needed to regenerate makefiles/configure, so it *shouldn't* affect users (just developers). Hmm. looking at it, at least for the version I'm running it's having issues finding the rekall help files/handbook...
>It also may be a wee bit tricky... Right. Didn't thought about it. So keeping it simple seems to be the better way. Raising the workload just to save a few ebuilds isn't desirable. I didn't had problems with the docs, but the sed -i -e 's/$(LN_S) $(kde_libs_htmldir)\/$(KDE_LANG)\/common/$(LN_S) common/' ${S}/doc/rekall/Makefile.in fix is still needed.
Created attachment 29414 [details] rekall-2.2.0_beta3.ebuild (non qt)
WARNING: I just read
WARNING: I just read¹ that the rekall website was hacked (including the implementation of a trojan installation routine using the internet explorer mhtml bug, but this shouldn't affect anyone here), fixed silently and hacked again. At the moment the website is offline, but there was no information given and it is not sure, if the rekall sources are affected. Don't know anything about the information about the time frame. I couldn't find any rootkit or other traces of malicious software, but I only have the beta4 tarball, so I can't compare it with older sources. Please DON'T USE THE ATTACHED EBUILDS at the moment, even though the sources my be fetchable again. [1] http://www.heise.de/newsticker/meldung/46757 (sorry, german)
Created attachment 29991 [details, diff] rekall-2.2.0-beta3-enable-db.patch Few notes- you're missing the specific enabling for the drivers- the config should enable them anyways, but best to be anal- also, instead of use odbc && myconf="${myconf} --enable-odbc=yes --enable-iodbc=yes" \ || myconf="${myconf} --enable-odbc=no --enable-iodbc=no" you could do myconf="${myconf} `use_enable odbc` `use_enable odbc iodbc`" Also attaching a patch to make the configure script throw a fit if a driver module is enabled, but unable to be configured. As for the site being hacked, it actually was fooled with twice- there is a mention on the main page regarding it- no comment regarding the src, basically somebody screwed w/ the forums.
Also, rekall 2.2.0-beta4 is out :)
Do you know, if the tarballs were modified, when the site was hacked, Brian? I got no answer on my email, yet. What's your beta4 digest?
Created attachment 31403 [details] rekall-2.2.0_beta4.ebuild Hello all! I use rekall for 2 months and i have to say: it's great! Anyway - I have done my own version of ebuild, based on the one I have found here. It's nothing new in it - it's rather an ebuild cleanup. Hope You will find it usefull. Regards, Przemek PS. Sorry for any mistakes I have made - I'm still learning english ;-)
Comment on attachment 31403 [details] rekall-2.2.0_beta4.ebuild ebuild cleanup? Hello all! I use rekall for 2 months and i have to say: it's great! Anyway - I have done my own version of ebuild, based on the one I have found here. It's nothing new in it - it's rather an ebuild cleanup. Hope You will find it usefull. Regards, Przemek PS. Sorry for any mistakes I have made - I'm still learning english ;-)
*** Bug 54995 has been marked as a duplicate of this bug. ***
Created attachment 35694 [details] rekall-2.2.0.ebuild 2.2.0 *final* ebuild, please add it at least.
Created attachment 35695 [details] rekall-2.3.0_beta0.ebuild Beta version, if added should be masked out.
Any dev's willing to take maintainership of this? I've spent a fair amount of time dealing w/ rekall (specifically porting it), although I don't use it on a day to day basis. Added, the upcoming conversion of the build system to scons in 2.3 is something that mildly seems scary :) So yeah, /me pokes all who are around, victims^WBrave souls who care to take this on? Not a huge amount of bugs pop up, although what does is typically upstream bugs. Aside from that, the final release is basically beta4 + header changes.
committed 2.2.0 - please open a new request for the 2.3.0 beta. I don't have the time to grok scons now and the new features of the beta are not very usable according to the website, so it's pretty low priority on my list, though.
I have emerge rekall and work well. I propose to enable stable
