pd-cvs-request@iem.at wrote:
Message: 4 Date: Wed, 30 May 2007 04:32:12 -0400 (EDT) From: pd@macosx104-powerpc.idmi.poly.edu (Pd User) Subject: [PD-cvs] autobuild: pd-extended macosx104-powerpc 2007-05-30 03.15.04 To: pd-cvs@iem.at Message-ID: 20070530083212.B78ABA8D909@macosx104-powerpc.idmi.poly.edu
/Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:213: note: LOOP VECTORIZED. /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:204: note: vectorized 1 loops in function.
/Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:75: note: LOOP VECTORIZED. /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:75: note: vectorized 1 loops in function.
/Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:148: note: not vectorized: stmt not supported: D.3479_62 = (short int) D.3478_61 /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.c:148: note: vectorized 0 loops in function. cc -bundle -bundle_loader /Users/pd/auto-build/pd-extended/pd/bin/pd -L/sw/lib -o /Users/pd/auto-build/pd-extended/externals/iem16/src/tab16read.pd_darwin /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_array.o /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.o -lm -lc /usr/bin/ld: multiple definitions of symbol _table16_class /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_array.o definition of _table16_class in section (__DATA,__common) /Users/pd/auto-build/pd-extended/externals/iem16/src/iem16_table.o definition of _table16_class in section (__DATA,__common) collect2: ld returned 1 exit status
just to reiterate myself: i can compile and run iem16 on linux and os-x as a _library_.
splitting it up into single externals (for pd-extended) and declaring the table16_class as "static" (to avoid the above compile error), produces a binary that is useless.
therefore, if iem16 is to be included in pd-extended, i suggest building it as a library.
mfga.sdr IOhannes
Hallo!
just to reiterate myself: i can compile and run iem16 on linux and os-x as a _library_.
yes, but also only if you NOT declare table16_class as static, which leads to the compile error on osx ...
therefore, if iem16 is to be included in pd-extended, i suggest building it as a library.
This makes no difference to me here (on linux), maybe it is different on osx ...
I think we should figure out why it is forbidden to declare this as non static ... anyone an idea ?
LG Georg
Georg Holzmann wrote:
Hallo!
just to reiterate myself: i can compile and run iem16 on linux and os-x as a _library_.
yes, but also only if you NOT declare table16_class as static, which leads to the compile error on osx ...
yes, sorry if this is unclear: the reason for all this is that "table16_class" must NOT be static in order to make the objects work.
this (that is: NOT declaring table16_class as static) leads to the compile error on osx, if compiled with pd-extend's build-system as single externals (it compiles fine with _my_ buildsystem)
the fix is NOT to make the class "static" (which breaks the object), but to fix the linkeage.
(this is basically what georg is saying)
fmga.sr IOhannes
IOhannes m zmoelnig wrote:
Georg Holzmann wrote:
Hallo!
anyhow, i have split iem16 into 1-C-file-per-object; this compiles fine on linux and os-x, both as library and single-file externals using my build-system. (functional tests only done on linux).
just, for your interest
mfg.asdr IOhannes
-
Georg Holzmann -
IOhannes m zmoelnig -
IOhannes m zmölnig