Re: [Tracker] Building the current cvs version.

[Anders Aagaard <aagaande gmail com>]

Jamie McCracken wrote:
> Anders Aagaard wrote:
>
> > Checked out a clean version now and that fixed it.
> >
> > > > And when taking that out I get the error:
> > > > aclocal: macro `AM_PROG_MKDIR_P' required but not defined
> > > > aclocal: macro `AM_PROG_MKDIR_P' required but not defined
> > > > in the libextractor directory.
> > > dont remove dirs please!
> > I just did a clean checkout and I still get that error.
> you are probably missing some standard automake macros then
>
> try upgrading automake?
I have these automake releases installed : 1.9.6-r2 1.8.5-r3 1.7.9-r1 
1.6.3 1.4_p6 1.5
> or google for more info on that macro
Tried that first and couldn't find much information.  I noticed that 
gnome-autogen is called aclocal-1.7.  I have gnome-common version 2.12, 
is that version number supposed to be sync'ed with gnome releases? 
Because if it is I'm way outdated.
> You can download a different version of libextractor and use that 
> (tracker will not build its internal libextractor in that case)
I have libextractor installed, and tracker is still trying to build the 
internal one. (libextractor version 0.5.14 to be specific).
> > > > Attaching a theoretically working implementation of ionice.  
> > > > trackerd.c would have to run the ionice_init() function.  I would 
> > > > have tested it and made it a bit cleaner if I could get the cvs 
> > > > version compiled at all :P
> > > > Most of the code for ionice is gotten from the snippet in the 
> > > > Documentation/block/ioprio.txt file in the linux kernel.
> > > Correct me If I am wrong, but does not ionice default to the cpu nice 
> > > value (which is +10 for tracker and +19 for text filters)?
> > Just tried a nice --adjustment 19 on a process now, and used ionice -p 
> > <process> to check the ionice level.  And it reported ioclass none, 
> > ioprio 0.  (which in the kernel translates to ioclass best effort, 
> > ioprio 4)
> > > AFAIK, its linux specific and only in 2.6.13+ so I can't really 
> > > depend on it.
> > Might be possible to get configure to check for this, but I'm horrible 
> > at autotools.
> me too! I hate the auto-foo shit (I always end up copying stuff from 
> other packages!)
> I dont have ionice support in my kernel so I cant really implement this 
> but Im happy to accept patches that does (with auto-foo and #ifdefs)
I'll see if I can overcome my hate of autotools and figure this out.