On Mon, Apr 19, 2010 at 08:44, Jonas Smedegaard <jo...@jones.dk> wrote:
> On Mon, Apr 19, 2010 at 08:03:01AM -0400, Felipe Sateler wrote:
>> On Mon, Apr 19, 2010 at 01:40, Reinhard Tartler <siret...@tauware.de>
>> wrote:
>>>> === csound:
>>>> = 1 Release Goals bug(s):
>>>> - #414330 <http://bugs.debian.org/414330>
>>>>   csound: FTBFS on GNU/kFreeBSD: missing OS detection
>>>>   Part of release goal: kfreebsd-* as release architectures
>>> has been uploaded on April 14, I guess this is handled
>> No, its not. The csound build system relies extensively on testing for
>> 'linux' for lots of functionality. Porting work is needed, but I don't
>> have time or motivation for that. I don't think many people will use
>> csound from freebsd, there's not much point.
> One point in ensuring support also on alien architectures is to shake out
> weird bugs appearing first on odd system and maybe only through carefully
> crafted evil hacks on more popular ones.

Note that csound happily builds on all architectures. The biggest
problem is that csounds build system, when checking for functionality
does not always test directly for that, but uses the OS as a proxy.
So, for Windows it would enable some flags, others for OSX and yet
others on linux. Most of these are actually dependent on the gcc
version being used (or indeed if it is gcc at all), and whether the
system is a posix one or not. Csound generally sticks to standards, so
bugs of this kind are rare.


Felipe Sateler

pkg-multimedia-maintainers mailing list

Reply via email to