Levi Burton wrote:
Greetings,
I was curious what compiler versions people have had the best luck with.
I am currently using: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-113)
I am considering upgrading via RPM to what appears to be 3.2
(gcc-3.2-7.i386.rpm). Good idea? Bad Idea?
Thanks!
Greetings,
I was curious what compiler versions people have had the best luck with.
I am currently using: gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-113)
I am considering upgrading via RPM to what appears to be 3.2
(gcc-3.2-7.i386.rpm). Good idea? Bad Idea?
Thanks!
Levi
On 4 Jan 2003 [EMAIL PROTECTED] wrote:
> Hi all,
>
> Another day.. another release :)
>
> * fixed plugin stuff to work with 2.9x C++ symbols
> * fixed fltk compile
> * added an alsa-patch-bay.desktop
> * fixed fltk segfault
>
> http://pkl.net/~node/alsa-patch-bay.html
>
Ah, you solved the probl
04/01/03 19:07, Steve Harris wrote:
> On Sat, Jan 04, 2003 at 02:51:13 +0100, Pascal Haakmat wrote:
> > My proposal loses us nothing: because plugin authors need to use the
> > PortName field to describe port values _anyway_ (to aid non
> > RDF-capable hosts) it makes sense to agree on a best way
On Sat, 2003-01-04 at 12:17, Fernando Pablo Lopez-Lezcano wrote:
> On Sat, 2003-01-04 at 01:49, Andrew Morton wrote:
> >
> > There's no sign of a deadlock or a livelock in these traces. It just
> > looks like these tasks are asleep and not waking up.
> >
> > > Each time I break into the debugger
On Sat, 2003-01-04 at 01:49, Andrew Morton wrote:
> Fernando Pablo Lopez-Lezcano wrote:
> > 4)
> > schedule +1ab
> > sleep_on +45
> > bread +20
> > __mark_inode_dirty +d9
> > pipe_write +1b9
> > poll_freewait +44
> > sys_write +9f
> > system_call +33
> >
> > So the system seems to be stuck in __ma
On Sat, Jan 04, 2003 at 02:51:13 +0100, Pascal Haakmat wrote:
> But it is not solving the problems:
>
> 1. The PortName still needs to describe the possible values for non
> RDF-capable hosts.
Any host that cares to that extent would also benefit from the other
features of RDF.
> 2. The host st
On Sat, Jan 04, 2003 at 01:31:21 +, Bob Ham wrote:
> While we're on that, I'm adding lrdf support to jack rack and I'm
> wondering where the ladspa descriptions should be gotten from. The
> showtaxonomy uses "file:ladspa.rdfs" and "file:example.rdf" URIs. How
> should a proper host be contruc
> I want to play sound samples (sorry for using 'wav', I just want
>to play raw sound samples) that are resident in memory. I want to play
>the samples (not read or write files). Which is the most convenient and
>easy to use library for this purpose?
i'm not trying to be a PITA, but you
On Saturday 04 January 2003 16.51, Vandana wrote:
> I want to play sound samples (sorry for using 'wav', I just want
> to play raw sound samples) that are resident in memory. I want to
> play the samples (not read or write files). Which is the most
> convenient and easy to use library for this purp
I want to play sound samples (sorry for using 'wav', I just want
to play raw sound samples) that are resident in memory. I want to play
the samples (not read or write files). Which is the most convenient and
easy to use library for this purpose?
On Sat, 4 Jan 2003, Erik de Castro Lop
04/01/03 12:23, Steve Harris wrote:
> On Sat, Jan 04, 2003 at 09:51:20 +0100, Pascal Haakmat wrote:
> > Hi all,
> >
> > It appears as though LADSPA at the moment lacks a means to provide
> > names for control values (this topic has probably crossed the list
> > before so I'll try to keep it short
On Sat, 2003-01-04 at 12:23, Steve Harris wrote:
> However no hosts can read RDF yet. http://plugin.org.uk/lrdf/ for code.
> It can also do a number of other metadata tasks incuding categorisation.
> I think its better to solve all these problems at once.
While we're on that, I'm adding lrdf supp
On Sat, Jan 04, 2003 at 09:51:20 +0100, Pascal Haakmat wrote:
> Hi all,
>
> It appears as though LADSPA at the moment lacks a means to provide
> names for control values (this topic has probably crossed the list
> before so I'll try to keep it short).
>
> The common solution for this problem (e.g
On Sat, 2003-01-04 at 08:51, Pascal Haakmat wrote:
> Therefore (if such a thing does not already exist) I propose to extend
> the LADSPA specification with a convention: if a PortName matches the
> following regular expression: .+ \((\d+=.+,)*(\d+=.+)+\) (in words:
> any sequence of characters foll
Fernando Pablo Lopez-Lezcano wrote:
>
> ...
> 4)
> schedule +1ab
> sleep_on +45
> bread +20
> __mark_inode_dirty +d9
> pipe_write +1b9
> poll_freewait +44
> sys_write +9f
> system_call +33
>
> So the system seems to be stuck in __mark_inode_dirty, whatever that is.
No, that's just stack gunk.
T
Hi all,
Another day.. another release :)
* fixed plugin stuff to work with 2.9x C++ symbols
* fixed fltk compile
* added an alsa-patch-bay.desktop
* fixed fltk segfault
http://pkl.net/~node/alsa-patch-bay.html
Bob
Hi all,
It appears as though LADSPA at the moment lacks a means to provide
names for control values (this topic has probably crossed the list
before so I'll try to keep it short).
The common solution for this problem (e.g. as used in Steve Harris'
plugin collection) is to use an integer control p
18 matches
Mail list logo
