similar to: No subject

Hi Jean-Marc, Not exactly. Under cross-compiling you circumvent this standard way by blindly assuming that it is present. That's what I recall. Patch we used to fix this is attached. On Thu, Oct 22, 2009 at 08:31, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > The way the libogg check is actually not something that's under my > control. It's installed on the

The way the libogg check is actually not something that's under my control. It's installed on the system as an autoconf .m4 file. Jean-Marc Alexander Chemeris a ?crit : > Hi Jean-Marc > >>From my experience with cross-compiling - IIRC, when cross-compiling > configure *assumes* that you have libogg unconditionally. So we had to > patch it to remove this check. I do

Try adding --without-lobogg to the configure script. Otherwise, just ignore the error because the important part (libspeex/) has already been built when the error is reported. Jean-Marc Ben Leslie a ?crit : > Hi all, > > I'm cross-compiling speex for a GNU/Linux ARM target. > > I want to compile only the libraries, and not the speex executables. > > I don't

Hi all, I'm cross-compiling speex for a GNU/Linux ARM target. I want to compile only the libraries, and not the speex executables. I don't have a libogg cross-compiled, and would prefer the need to have to set it up. Unfortunately: 1/ the speex executables depend on libogg header files, although, the speex executables are only compiled if the libogg header files are available 2/ the

Hi Jean-Marc

Full_Name: Drew Tyre Version: 1.4.0 OS: Win 2000 Submission from: (NULL) (140.253.74.225) When creating a rather complex plot, the resulting figures 'shrink' when either copied to the clipboard or saved as a metafile using the GUI menu. Also saving as postscript or pdf causes the same problem, as does printing the figure directly from the graphics window. Only the figure areas shrink,

On 02/04/2008, Alexander Chemeris <Alexander.Chemeris at sipez.com> wrote: > On 4/1/08, Keith Kyzivat <kkyzivat at sipez.com> wrote: > > IIRC, under ARM, I believe I was having issues with --without-libogg. > > I resorted to just downloading libogg sources, setting up my > > cross-compilation environment, and cross compiling it per the general build > >

on hp-ux 11 i see: $ date;ssh jenny Fri Oct 12 14:44:13 PDT 2001 Last successful login for stevesk: Fri Oct 12 10:45:42 PST8PDT 2001 on pts/2 Last unsuccessful login for stevesk: Mon Sep 24 22:55:53 PST8PDT 2001 Last login: Fri Oct 12 10:45:43 2001 from 172.31.1.53 You have mail. so solaris PAM is different. can other solaris+PAM users confirm this? On Fri, 12 Oct 2001, Benn Oshrin wrote:

IIRC, under ARM, I believe I was having issues with --without-libogg. I resorted to just downloading libogg sources, setting up my cross-compilation environment, and cross compiling it per the general build directions (./configure, make, make install), then went back to building speex -- everything worked like a charm for me then. So -- Conrad. *Make sure* that you have libogg cross-compiled and

hi i created two files in excel with a dbf format in a similar way. the first is opened in R, however, when i try to open the second. i received the following message: sites.can <- read.csv("SITES.csv") Error in read.table(file = file, header = header, sep = sep, quote = quote, : more columns than column names > The second file works with the same command

Hi, This patch make libogg detection a bit smarter if you're trying to cross-compile. What I want is to be able cross-compile Speex without OGG - right now it is not possible without som hacking of Speex build scripts, because if cross-compiling enabled speex silently assume that you have libogg compiled and installed. Such behaviour was used (as far as I could imagine) because with

Dear All, I have searched the following problem in the R help achives, and there did not seem to be solutio for it. The problem is how to break the axis in the xyplot (lattice plot). I read the posts using the package plotrix, buy it doesn't work with the xyplot, which is lattice based. A simple example is attached below: xyplot(c(1:10,100)~c(1:10,100)) What I would like to do is

Something to look into perhaps is Trolltech's 'qmake' tool. It fills the role of something like autotools or now defunct imake. As far as I understand, you can indeed use it for projects that don't do anything with the Qt libraries. Now, it may not have the support for multiple targets that it sounds like are needed for speex, and I know it doesn't have as comprehensive of

First patch fixes two typos in manual. Second patch adds few notes about latency, as promised. Hopefully I haven't added any typos and grammar errors :) On Wed, Jul 1, 2009 at 8:02 PM, Alexander Chemeris<Alexander.Chemeris at sipez.com> wrote: > Thank you for clarification. I attached a patch which (IMHO) > makes it more clear for everyone who just read Doxygen > docs.

On 12/20/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > Sorry, been busy with maintenance on Valin 2.0 and 3.0 :-) Just applied > your fix to the assembly. Can you confirm it works fine? Yep, it works fine. Thanks. > About including > assembly directly (.asm/.s instead of gcc inline asm), I'm OK in > principle if someone can show me how to do that cleanly

Thanks Tom. heatmap.2(mat, Rowv=NA, Colv=NA, col=redgreen, breaks=seq(-1,1,by=0.01), symm=TRUE, trace="none", dendrogram="none") that did the trick :) Begin forwarded message: From: "Leja, Thomas" Date: 29 March 2011 03:47:59 GMT+01:00 To: "Benton, Paul" Subject: Re: [R] comparing heatmaps Yep, you have to specify the range for colours. I usually

1. You pass in half the samples as the 'bits' arg. Speex looks at 1 frame worth of those bits and decodes them, decoded result in 'pcm'. 2. You pass in exactly 1 frame of data as the 'bits' arg. Speex looks at 1 frame worth of those bits (which is all there, exactly), decodes them, stores decoded result in 'pcm'. 3. You pass in 2 frames of data as

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

so, having a speex frame, how do i know where is each sample if i don't know how many bits per sample are being used. Isn't there any info besides the data ? On Wed, Jul 15, 2009 at 7:21 PM, Alexander Chemeris < Alexander.Chemeris at sipez.com> wrote: > Hi, > > Speex RTP payload does not have any header (except RTP header), > as per speex-rtp RFC. > > On Wed, Jul

Here's a summary of changes from README.md: libX11 version 1.7.0 includes a new API, hence the change from the 1.6 series to 1.7: * XSetIOErrorExitHandler which provides a mechanism for applications to recover from I/O error conditions instead of being forced to exit. Thanks to Carlos Garnacho for this. This release includes a bunch of bug fixes, some which have been pending for over