[GEM-dev] build errors on 10.3

[IOhannes m zmoelnig]

Hans-Christoph Steiner wrote:
> 
> The Mac OS X 10.3 build is still dying here.  There hasn't been a 10.3
> fix for many weeks.  Could this be fixed?  It could be done with an
> #ifdef for Mac OS X 10.3 alone, at the very least.  Then we'd have
> Pd-extended builds on 10.3 again.

i was already wondering....
every day i see the build log and think to myself "this oughta be fixed".

fixes and workarounds include:
+ real fixes, which use the correct types when calling the intrinsic
functions (needs to be tested by someone who does not work via ssh...)
+ add tests to configure whether the compiler accepts unsigned vs signed
vectors in the intrinsics and conditionally disable the problematic code.
+ #ifdef the code for given compilers (gcc-versions)
+ #ifdef the code for given platforms (osx-10.3)
+ disable the use of altivec in the osx-10.3 builds via configure-args
+ disable the use of altivec on osX via configure-args

imo, the simplest solution would be to disable altivec via configure,
but i doubt that you would like this (and i understand this). most
likely it is not really possible to have different configure-flags for
10.3 and 10.4 builds in the build-system (read: it would mean much work
for little gain).

i don't like the idea of disabling the code via an "#ifdef OSX10.3" at
all, since it is not osx-10.3 that prevents Gem from building but the
compiler.

adding a test to configure needs more time than i currently have.

this basically gives us 3 possible solutions:
+ fix the code
+ #ifdef the compiler-version
+ disable altivec in the pd-extended versions

unless somebody does a real fix, i will try the 2nd solution (at the
risk of disabling more than would be needed)


mfg.,adsr
IOhannes

PS: damned, i forgot to send this earlier...