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 future versions of the flac source distribution. The patch is against flac-1.0.2. If the source distribution is built with 'make dist' the end user should be able to build his own rpm files with the 'rpm -tb flac-VERSION-src.tar.gz' command. The build and functionality is tested on redhat-7.2 on i686. The build requires the libogg-devel and xmms-devel packages to be installed. The build produces three packages: flac, flac-devel and flac-xmms. nasm support is not built. Questions --------- I saw that there are some asm code for preformance critcal things. Does binaries built on for example i686 contain instructions that are incompatible with the i386? Cheers Daniel Resare PS. Please reply CC any replies to this message to noa@metamatrix.se as I'm not on the flac-dev list -- 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 -------------- A non-text attachment was scrubbed... Name: flac-spec-2.patch Type: text/x-patch Size: 2322 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20011218/6fe9b894/flac-spec-2.bin
--- Daniel Resare <noa@metamatrix.se> wrote:> For my own needs I have created the .spec file needed for rpm > packaging > of the flac package.thanks, I'll put this in the queue. I won't be able to do much with flac until january.> I saw that there are some asm code for preformance critcal things. > Does > binaries built on for example i686 contain instructions that are > incompatible with the i386?if asm optimization is not disabled, and nasm is available, for any i386 build, then several versions of some functions are always assembled. some use mmx, some use sse, some use 3dnow extensions. at runtime the library determines which cpu is being used and chooses the right assembly or C routine to use. the only exception is with sse. sse instructions require processor AND operating system support, and there is no run-time check for OS support anymore. so to get sse at all you have to use the --enable-sse flag with configure. this is the only way you can get an i386 binary that won't run on all i386 machines. that binary would crash if run on a cpu that supported sse instructions under an OS that did not. Josh __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com