On Thu, Aug 4, 2011 at 9:52 PM, Orcan Ogetbil wrote: > On Thu, Aug 4, 2011 at 1:38 PM, Pedro Lopez-Cabanillas wrote:
>> Mandriva: >> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/fluidsynth/current/SPECS/fluidsynth.spec?view=markup >> Mageia: >> http://svnweb.mageia.org/packages/cauldron/fluidsynth/current/SPECS/fluidsynth.spec?view=markup >> > > Thanks. Also add to that > Fedora: > http://pkgs.fedoraproject.org/gitweb/?p=fluidsynth.git;a=blob_plain;f=fluidsynth.spec;hb=HEAD > > >> Mandriva and Mageia have also a %cmake RPM macro, not conflicting with >> FluidSynth's buildsystem. >> > > But the problem is, these are all fluidsynth-1.1.3. Things broke > between 1.1.3 and 1.1.4. I guess I am the first one complaining. > More research showed this is indeed the case. For the two RPM distributions above, LIB_INSTALL_DIR variable is defined as %{_libdir} in their own (nonFedora) %cmake macros http://svnweb.mageia.org/packages/cauldron/cmake/releases/1%3A2.8.5/1.mga2/SOURCES/cmake.macros?view=markup http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/cmake/releases/1%3A2.8.4/3/SOURCES/cmake.macros?view=markup and %{_libdir} opens up to /usr/lib64 on 64bit installations of these distributions. Therefore when these two distributions update to 1.1.4, their fluidsynth build will break too. It's really not just us bad Fedora boys. Orcan _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
