Re: Alsa Compile Problems & Checking for GTKMM

On Wed, 2004-02-04 at 15:20, David Hough wrote:
> On Wed, 04 Feb 2004 20:48:38 +0000, Robert Hart <[email protected]> 
> wrote:
> 
> > I think you might have broken the build if --enable-experimental wasn't
> > used.
> >
> > I will try a fresh CVS pull in case I landed in the middle of something,
> > but I am getting undefined symbols in the regular musicbrowser.
> 
> Stupid me for only checking it compiled, not if it actually ran. By the 
> way, in relation to the fix, do we really need any experimental code at 
> all in the normal browser? As far as I can tell it is only referenced in 
> musicsearch.cpp, and the seachPath command will only update the database 
> for browsermm and mdb, not for the old database and browser. It seems 
> rather pointless leaving the command in there, unless its the start of 
> porting the standard browser over to the mdb code?

--enable-experimental was  temporary fix to remove references
to browsermm/mdb code in the current code base.   After 2.2.5
goes out, I'll possibly add --enable-deprecated to allow
people to compile/use the older browser.  


> > Did you apply the alsa patch below? I have something similar in my tree
> > after reading a bug report on the debian bugs page, but I wasn't sure if
> > the fix was debian specific or not.
> 
> I haven't applied the patch, I didn't want to revert the previous patch 
> without asking first as chances are that the plugin needs to be switched 
> over to the new api at some point, and that may be the only actual change 
> needed. If no-one objects I will apply it sometime tommorow though.

The patch already should be in CVS.  I think Robert Hart applied it.

> > I am trying to find the crash on watch directory bug, but it's an
> > absolute stinker to debug. I think the seg-fault happens so quickly
> > after a new thread is created the gdb doesn't have a chance to attach to
> > the new thread. I got the impression from a previous e-mail of yours
> > that it works flawlessly for you.
> 
> I've never once had a problem with it. I haven't really used it since the 
> browsermm started using the mdb database though, as it only updates the 
> old database. I remember I used to occasionly get seg faults when doing a 
> manual search from the musicbrowser, but as I could never reproduce them I 
> just ignored it, it wasn't something I did very often after all.

I've noticed that it chokes on certain file names.  I am less inclined
to search/fix this as I expect it will not be  problem for the mdb 
code.


-- 
email:[email protected] office:(805)893-4276 http://www.cs.ucsb.edu/~kris



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn