similar to: bug reports and missing license headers

Hello. Look at this: [sergey@gleam sergey]$ uname -s -m -r Linux 2.4.17 i586 [sergey@gleam sergey]$ mount | grep /home /dev/hda11 on /home type ext3 (rw) [sergey@gleam sergey]$ pwd /home/sergey [sergey@gleam sergey]$ id uid=502(sergey) gid=100(users) groups=100(users),10(wheel),13(news),512(ftpadmin),513(dos) [sergey@gleam sergey]$ stat . File: "." Size: 8192 Blocks: 16

On Fri, Oct 28, 2011 at 10:25 AM, Daniel Dunbar <daniel at zuster.org> wrote: >  * I don't think CMake is good enough. I agree it solves problems, but > I want to use great tools, not ones that work. In particular: >    (c) This doesn't solve any other nice problems: >          (i) It doesn't make it easier to play with other build > systems (like Ninja, or gyp).

On Fri, Oct 28, 2011 at 10:50 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Fri, Oct 28, 2011 at 10:25 AM, Daniel Dunbar <daniel at zuster.org> wrote: >>  * I don't think CMake is good enough. I agree it solves problems, but >> I want to use great tools, not ones that work. In particular: >>    (c) This doesn't solve any other nice problems:

I'm going to briefly summarize my responses here. On Fri, Oct 28, 2011 at 9:56 AM, Chris Lattner <clattner at apple.com> wrote: > On Oct 28, 2011, at 12:54 AM, Óscar Fuentes wrote: >> Anyways, if you wish to avoid duplicating info on both Makefile and >> CMakeLists.txt there is a simple solution: read and parse the Makefile >> from the corresponding CMakeLists.txt.

On Oct 28, 2011, at 12:54 AM, Óscar Fuentes wrote: > A good measure of how fast a set of Makefile are is to run the build > with all targets up-to-date. Both builds takes a few seconds (3 or so) > on my Linux quad core box. Whatever improvement can be achieved on this > seems pretty insignificant. There are different overheads in different scenarios. The makefiles get really poor

Hi, We are rebasing our audio compression subsystem using OPUS rather than SPEEX. The platform is Android but this piece is written in C code: we need to support armv5/armv7/x86 architectures.... and we use the released opus-1.1beta package from here<http://downloads.xiph.org/releases/opus/opus-1.1-beta.tar.gz>. A lot of our OPUS build system + code to drive the audio compression has been

Daniel Dunbar <daniel at zuster.org> writes: > I'm going to briefly summarize my responses here. > > On Fri, Oct 28, 2011 at 9:56 AM, Chris Lattner <clattner at apple.com> wrote: >> On Oct 28, 2011, at 12:54 AM, Óscar Fuentes wrote: >>> Anyways, if you wish to avoid duplicating info on both Makefile and >>> CMakeLists.txt there is a simple

If opus_compare doesn't exist or isn't executable, tests failed normally which could be misleading. So test for existence and mode to avoid this ambiguity. --- tests/run_vectors.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/run_vectors.sh b/tests/run_vectors.sh index 1cc445d..116a743 100755 --- a/tests/run_vectors.sh +++ b/tests/run_vectors.sh @@ -57,6 +57,11 @@

On Fri, Oct 28, 2011 at 1:31 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Daniel Dunbar <daniel at zuster.org> writes: > >> I'm going to briefly summarize my responses here. >> >> On Fri, Oct 28, 2011 at 9:56 AM, Chris Lattner <clattner at apple.com> wrote: >>> On Oct 28, 2011, at 12:54 AM, Óscar Fuentes wrote: >>>> Anyways, if

If opus_compare doesn't exist or isn't executable, tests failed normally which could be misleading. So test for existence and mode to avoid this ambiguity. -- Aur?lien Zanelli Parrot SA 174, quai de Jemmapes 75010 Paris France -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Check-if-opus_compare-is-executable-in-run_vectors.s.patch Type:

This patch lets you pass paths for opus_demo and opus_compare to the run_vectors.sh script. The motivation for this was for my aarch64 patches (forthcoming), which I've been testing under qemu. I want to run an emulated opus_demo, but a native opus_compare, so the script completes in a reasonable amount of time. --- tests/run_vectors.sh | 4 ++-- 1 file changed, 2 insertions(+), 2

-- Joshua Bowman Silverback Networks (559) 305-3770 silverbacknet at gmail.com www.silverbacknetworks.net -------------- next part -------------- src/analysis.c | 6 +++--- src/mlp.c | 3 +++ src/opus.vcxproj | 5 +++++ src/opus.vcxproj.filters | 15 +++++++++++++++ src/opus_demo.vcxproj | 4 ++++ src/opus_demo.vcxproj.filters |

On 21 November 2014 at 18:06, Timothy B. Terriberry <tterribe at xiph.org> wrote: > > Viswanath Puttagunta wrote: >> >> a. Simplest use case to validate this optimization for correctness. >> b. Simplest use case to validate this optimization for performance. >> >> Would prefer something like opusdec that can be executed on command >> line. > >

On 13-07-18 8:12 AM, Dubois-Rande, Antoine wrote: > C:/android/android-ndk-r8e/toolchains/arm-linux-androideabi-4.6/prebuilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld.exe: ./obj/local/armeabi/lib0.a(analysis.o): in function > run_analysis:jni/src/libopus/src/analysis.c:636: error: undefined reference to > 'optimize_framesize'

This allows the libopus source files to be compiled with a C++ compiler, by ensuring that the "extern const MLP net" declaration is visible at the point of the "const MLP net" in src/mlp_data.c. Otherwise it will default to static linkage in C++, resulting in an undefined symbol. Note that if compiled with a C++ compiler the symbols will be mangled, so don't do that if

>> >> a. Simplest use case to validate this optimization for correctness. >> >> b. Simplest use case to validate this optimization for performance. >> >> >> >> Would prefer something like opusdec that can be executed on command >> >> line. >> > >> > >> > The easiest thing to use is probably opus_demo (opusdec

Viswanath Puttagunta wrote: > a. Simplest use case to validate this optimization for correctness. > b. Simplest use case to validate this optimization for performance. > > Would prefer something like opusdec that can be executed on command > line. The easiest thing to use is probably opus_demo (opusdec does a bunch of extra things, plus for interactive use we care about both the

On 24 November 2014 at 14:53, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > > On 21 November 2014 at 18:06, Timothy B. Terriberry <tterribe at xiph.org> wrote: > > > > Viswanath Puttagunta wrote: > >> > >> a. Simplest use case to validate this optimization for correctness. > >> b. Simplest use case to validate this

Hi, I am trying to built an ISO with nodejs010 packages but when I run the command "repoclosure -a x86_64 -r <local-repository-name>" to check its further dependencies, it is giving unresolved dependencies error. Example: package: nodejs010-node-gyp-3.2.0-2.el7.centos.noarch from Harman (it's a local repo name) unresolved deps: npm(minimatch) < 0:4

Hi Could you perhaps possibly help me. I would like to use the package VIF but cannot get results I attach the .csv file and my R code. What do I have to do ? Any help is greatly appreciated. library(VIF) coal <- read.csv("e:/freekvif/cqa1.csv",header=TRUE) y <- as.numeric(coal$AI) x <- as.matrix(cbind(coal$Gyp, coal$Pyrite, coal$Sid, coal$Calcite, coal$Dol,