> > > Could you try the cinelerra packages I made for slack 12?
> > > http://slack.sarava.org/packages/slackware/slackware-12.0/media/video/cinelerra/
> > >
> > > Patches and compile script:
> > > http://slack.sarava.org/slackbuilds/media/video/cinelerra/
> >
> > I might see about giving this a go myself in the next few weeks.
> >
> > Over the weekend I happened to have access to a Slackware 12 box and
> > decided to check this "freezing" thing out myself (my main PC is still
> > Slackware 10.2 for various unrelated reasons).  I should also note that I
> > used HV's cinelerra since I didn't have an updated snapshot of CV handy.
> 
> slack 10.2 uses a glibc that likes cinelerra.

Correct.  Before moving that box to slack 12.0 I wanted to test this
cinelerra issue out first hand.

> > I found that I needed to apply a few changes to the Makefiles, mainly
> > associated with the use of "\;" in "$(shell ...)" constructs - under
> > Slackware 12 the backslash is no longer needed.  I did not apply any other
> > patches, and Cinelerra built fine and installed without hassle.=20
> 
> cinelerra builds fine on slack 12.0 too.

I can't speak for CV, but HV definitely needs some patching, albeit entirely
trivial.

> > I then started it and it appeared to operate normally - no freezing up
> > of the splash screen or anything.  I didn't have the time to give it a
> > really extensive workout but the initial impressions were that things
> > were working for me.
> 
> nice!
> i'm running cinelerra ok here too (w/ my patch).

Right.  My point here was that I *didn't* have to use your patch to prevent
the splash screen lockup - I'm running stock Cinelerra-HV with my trivial
Makefile patches so it could build.  This puzzles me somewhat since it
suggests that the cause of the lockup is dependent on other external issue
which perhaps is exasperated by glibc 2.5.  What it might be however is a
total mystery to me.

> > At this stage I don't know whether this indicates the freeze is due to
> > something only in CV, if I'm just lucky, or if there's some other
> > condition which triggers the freeze.  I'm just throwing this finding out
> > there in case it's useful to anyone.
> 
> imho, its related to the locking code for threads.
> 
> > In case it's important this was all under kernel 2.6.22.1-rt9 running the
> > fvwm2 window manager.
> 
> i'm running e17 w/ stock patrick kernel.

Hmm, ok.  I *think* slack 12.0's default kernel is now compiled for SMP, and
the machine I'm running on is also compiled for SMP (CPU is a dual-core).
Excepting some obscure kernel issue that's been recently fixed (or an HV/CV
difference) the environment should therefore be almost exactly the same, so
it's a bit puzzling why I don't see the lockup and you do.

Regards
  jonathan

_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Reply via email to