similar to: vorbis-tools spec fixes

While I'm at it here is an update to the libogg .spec-file fixing two small things. /noa <p> -- begin:vcard fn:Daniel Resare tel;cell:+46739442044 tel;work:+468332040 adr;work:Scheelegatan 36; 112 28; Stockholm; Sweden end:vcard pgp fingerprint: 8D97 F297 CA0D 8751 D8EB 12B6 6EA6 727F 9B8D EC2A -------------- next part -------------- Index: libogg.spec

I had to change the following to get the 'make distcheck' to work and to be able to build the rpms with 'rpm-build -tb *.tar.gz' I also added a test in libvorbis configure.in to detect older ogg versions (check for oggpack_writealign) and print a meaningful error. I also updated the .spec-file with dependencies on libogg-1.0 Thanks for great work everyone! /noa -- begin:vcard

For my own needs I have created the .spec file needed for rpm packaging of the flac package. End users --------- If anyone is interested in the resulting rpm-files i have made them available on http://noa.tm/flac-rpms/ FLAC maintainers ---------------- I have attached the specfile along with hooks in Makefile.am and configure.in in unified diff format so that they are ready for inclusion in

I have now listened to some rc3-encoded ogg-files, and overall it sounds great! I have, howerver encountered an annoying artifact in rc3 that could be described as a pumping or vibrating distortion. In the beginning of the provided sample the artifact is easily noticed in the left channel, but later in the sample i belive it is somewhat to the right in the stereo image. The artifact dissapears

I really don't know if this is the same problem that was reported by Ingo Saitz (I really couldn't say which one was 128kbit and which was the original wav when blind-testing. The original had some distortion that perhaps does somehting with my cheapo soundcard) but here's a description of what i've found: When doing some sample encoding with rc2 (rebuilt rpm with latest redhat

I had lunch with an interesting guy who had gotten .com-money to record the whole bible professionally with good actors (in swedish and english, kjv). The idea was to sell custom made compilations of biblical texts on cd over internet. The company is now out of money (surprise!), but all the material is recorded (about 350 hours) and if anyone gets a good idea on what to use the material to, it

... that this is a bug. :) btw, the argument to the -R option should be documented better (err, at all ;). it took me a while to guess it, especially considering the circumstances ... :} and are you sure, that the http://www.xiph.org/ogg/vorbis/doc/vorbisenc/reference.html contents match the url? the developer docs are generally a bit ... useless. they tell me hardly more than the headers by

The new 3.2.6.1 codecs work great with QuickTime 6 (thank you!), but there's no way for an application to identify them. And since the older 3.2.1.x and 3.2.2.x installers will actually *downgrade* the installed version of VP3, it would be nice if an application could warn the user. The attached patch increments kdxlqt_CodecVersion (and documents all the Component Manager arcana involved).

Here is a patch that implements a check so that libvorbis complains when a comment string that is not UTF-8 is added. This patch will break oggenc without my UTF-8 patch. (http://noa.tm/oggenc-utf8.2.diff.gz) I've tested the verification algorithm on ~150k strings in various charsets (from the gnome translations) and about 0.02% of the strings that has chars with 8th bit set is valid UTF-8

The attached typo results in error on uninstall of vorbis-tools: error: execution of %postun scriptlet from vorbis-tools-1.0beta4-1 failed, exit status 2 cheers/d -- nuclear cia fbi spy password code president bomb 8D97 F297 CA0D 8751 D8EB 12B6 6EA6 727F 9B8D EC2A <HR NOSHADE> <UL> <LI>text/plain attachment: vorbis-tools.spec.diff </UL> -------------- next part

Some days ago i noticed in the ogg vorbis documentation that the comment-field contents should be encoded in UTF-8. A brilliant idea I think, sadly it seems like no one is using it. oggenc and vorbiscomment included in vorbis-tools writes strings to the comments fields blindly without any encoding conversion in violation of the spec. I intend to try to solve these problems to the best of my

building rpm for mandrake 8.1 gives me this error what should i try? checking for two-argument statfs with struct fs_data (Ultrix)... no checking if large file support can be enabled... yes checking whether to support ACLs... no checking whether to build winbind... yes checking for poptGetContext in -lpopt... no checking whether to use included popt... ./popt checking configure summary configure:

The patch below modifies the spec file for FC4 RPM builds as follows: 1.) Build binaries using the -lmcheck option; various samba commands and smbd process crash badly without; see, for example: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=164353 2.) The Fedora project's samba RPMS install mount.cifs; it would help to have samba.org's RPMS do the same. It would be nice to

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1332851995 -7200 # Node ID 9c6337771520b390ed624fa6b6b2f2edc8042701 # Parent d9e6e8632bb6b9a2144e7e148bc7ea53ea4933fd tools/configure: add options to pass EXTRA_CLFAGS Currently qemu-xen will be compiled with CFLAGS only if CFLAGS was already in the environment during make invocation. If CFLAGS is in environment then make will

On 02.07.2015 23:12, Thomas Schmitt wrote: > Hi, > > hpa wrote: >> On PowerPC (I think) "unsigned char" is the default. > > In any case it seems a good idea to interpret the character > more explicitely. To my experience, one signdness change causes > a little tree of consequential signedness changes or questionable > cast operations. > How about the

Hello, just a few remarks for the SPEC file in icecast 2.1.0 First you might change these prerequest because if you use older release it does not compile anymore. Requires: libxml2 >= 2.4.19 BuildRequires: libxml2-devel >= 2.4.19 Requires: libxslt >= 1.0.15 BuildRequires: libxslt-devel >= 1.0.15 In the section %build you might add one option in the CFLAGS line,

hi there here is part of SPECS file: ------------------------------------------------------------------ CFLAGS="$RPM_OPT_FLAGS" ./configure \ --prefix=%{_prefix} \ --localstatedir=/var \ --sysconfdir=/etc \ --with-privatedir=%{_sysconfdir}/samba \ --with-fhs \ --with-quotas \ --with-smbmount \ --with-pam \

https://bugzilla.mindrot.org/show_bug.cgi?id=1992 Bug #: 1992 Summary: RPM build fails using Red Hat spec file Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Build system

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

Hello all, I used to use fully statically linked PHP, which I build into RPM using own-written spec-file. I need to do this as there are a lot of boxes with old linuxes (RedHat 6.2, 7, 9) which I can't upgrade to CentOS3/4 right now for a several reasons I don't want to explain here. When I've been using CentOS 4.0 and 4.1 - there were no big problems to link PHP as static executable