From the auto-builds:
g++ -c -g -O2 -fPIC -freg-struct-return -O3 -falign-loops=16 -funroll- loops -ffast-math -faltivec -I/sw/include/libquicktime -I/sw/include/ libquicktime/quicktime -I.. -I/Users/pd/auto-build/pd-extended/pd/ src GemPathBase.cpp -o GemPathBase.o GemMan.cpp: In static member function 'static void GemMan::createContext(char*)': GemMan.cpp:336: error: '::EnterMovies' has not been declared make[3]: *** [GemMan.o] Error 1 make[3]: *** Waiting for unfinished jobs.... GemPBuffer.cpp:510:1: warning: unknown escape sequence '\p' make[2]: *** [Base] Error 2 make[1]: *** [/Users/pd/auto-build/pd-extended/Gem/src/Gem.pd_darwin] Error 2 make: *** [extended_install] Error 2
.hc
------------------------------------------------------------------------
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
Wrong Quicktime. libquicktime is not the real one.
On 10/3/06, Hans-Christoph Steiner hans@eds.org wrote:
From the auto-builds:
g++ -c -g -O2 -fPIC -freg-struct-return -O3 -falign-loops=16 -funroll- loops -ffast-math -faltivec -I/sw/include/libquicktime -I/sw/include/ libquicktime/quicktime -I.. -I/Users/pd/auto-build/pd-extended/pd/ src GemPathBase.cpp -o GemPathBase.o GemMan.cpp: In static member function 'static void GemMan::createContext(char*)': GemMan.cpp:336: error: '::EnterMovies' has not been declared make[3]: *** [GemMan.o] Error 1 make[3]: *** Waiting for unfinished jobs.... GemPBuffer.cpp:510:1: warning: unknown escape sequence '\p' make[2]: *** [Base] Error 2 make[1]: *** [/Users/pd/auto-build/pd-extended/Gem/src/Gem.pd_darwin] Error 2 make: *** [extended_install] Error 2
.hc
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Hans-Christoph Steiner wrote:
From the auto-builds:
g++ -c -g -O2 -fPIC -freg-struct-return -O3 -falign-loops=16 -funroll-loops -ffast-math -faltivec -I/sw/include/libquicktime -I/sw/include/libquicktime/quicktime -I.. -I/Users/pd/auto-build/pd-extended/pd/src GemPathBase.cpp -o GemPathBase.o GemMan.cpp: In static member function 'static void GemMan::createContext(char*)': GemMan.cpp:336: error: '::EnterMovies' has not been declared make[3]: *** [GemMan.o] Error 1 make[3]: *** Waiting for unfinished jobs.... GemPBuffer.cpp:510:1: warning: unknown escape sequence '\p' make[2]: *** [Base] Error 2 make[1]: *** [/Users/pd/auto-build/pd-extended/Gem/src/Gem.pd_darwin] Error 2 make: *** [extended_install] Error 2
this has been fixed 6 hours ago ;-)
the problem used to be, that my environment (zmoelnig) on the build-machine was totally different from the one that was used for the auto-builds (pd), which also includes the path to all the fink-stuff (/sw/...).
took me a while to figure that out.
as for the x-dependency mentioned by cyrille: "--without-x" should do this.
mfga.sdr IOhannes
IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
From the auto-builds:
g++ -c -g -O2 -fPIC -freg-struct-return -O3 -falign-loops=16 -funroll-loops -ffast-math -faltivec -I/sw/include/libquicktime -I/sw/include/libquicktime/quicktime -I.. -I/Users/pd/auto-build/pd-extended/pd/src GemPathBase.cpp -o GemPathBase.o GemMan.cpp: In static member function 'static void GemMan::createContext(char*)': GemMan.cpp:336: error: '::EnterMovies' has not been declared make[3]: *** [GemMan.o] Error 1 make[3]: *** Waiting for unfinished jobs.... GemPBuffer.cpp:510:1: warning: unknown escape sequence '\p' make[2]: *** [Base] Error 2 make[1]: *** [/Users/pd/auto-build/pd-extended/Gem/src/Gem.pd_darwin] Error 2 make: *** [extended_install] Error 2
this has been fixed 6 hours ago ;-)
the problem used to be, that my environment (zmoelnig) on the build-machine was totally different from the one that was used for the auto-builds (pd), which also includes the path to all the fink-stuff (/sw/...).
took me a while to figure that out.
as for the x-dependency mentioned by cyrille: "--without-x" should do this.
i confirmed on the osx-10.4 build machine (with hopefully the same settings in the tcsh as the user 'pd'):
./configure --without-x --without-ImageMagick --without-tiff --without-jpeg --without-mpeg --without-mpeg3 --without-ieee1394 --without-aviplay --without-avifile --without-ffmpeg --with-pd=$(pd_src)
this produces a Gem.pd_darwin with following dependencies: otool -L Gem.pd_darwin Gem.pd_darwin: Gem.pd_darwin (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime (compatibility version 1.0.0, current version 6.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0) /System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.6) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0)
this looks ok to me.
so i would _strongly_ recommend such restrictive settings (the problem is, that while disabling X will disable X11 for now, but with the first dependency on X11 it crawls back in)
mfa-dr IOhannes
On Oct 3, 2006, at 11:49 AM, IOhannes m zmoelnig wrote:
IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
From the auto-builds:
g++ -c -g -O2 -fPIC -freg-struct-return -O3 -falign-loops=16 - funroll-loops -ffast-math -faltivec -I/sw/include/libquicktime - I/sw/include/libquicktime/quicktime -I.. -I/Users/pd/auto-build/ pd-extended/pd/src GemPathBase.cpp -o GemPathBase.o GemMan.cpp: In static member function 'static void GemMan::createContext(char*)': GemMan.cpp:336: error: '::EnterMovies' has not been declared make[3]: *** [GemMan.o] Error 1 make[3]: *** Waiting for unfinished jobs.... GemPBuffer.cpp:510:1: warning: unknown escape sequence '\p' make[2]: *** [Base] Error 2 make[1]: *** [/Users/pd/auto-build/pd-extended/Gem/src/ Gem.pd_darwin] Error 2 make: *** [extended_install] Error 2
this has been fixed 6 hours ago ;-) the problem used to be, that my environment (zmoelnig) on the build-machine was totally different from the one that was used for the auto-builds (pd), which also includes the path to all the fink- stuff (/sw/...). took me a while to figure that out. as for the x-dependency mentioned by cyrille: "--without-x" should do this.
i confirmed on the osx-10.4 build machine (with hopefully the same settings in the tcsh as the user 'pd'):
./configure --without-x --without-ImageMagick --without-tiff -- without-jpeg --without-mpeg --without-mpeg3 --without-ieee1394 -- without-aviplay --without-avifile --without-ffmpeg --with-pd=$(pd_src)
this produces a Gem.pd_darwin with following dependencies: otool -L Gem.pd_darwin Gem.pd_darwin: Gem.pd_darwin (compatibility version 0.0.0, current version 0.0.0) /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime (compatibility version 1.0.0, current version 6.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/ Carbon (compatibility version 2.0.0, current version 128.0.0) /System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/OpenGL.framework/Versions/A/ OpenGL (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.6) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 92.0.0)
this looks ok to me.
so i would _strongly_ recommend such restrictive settings (the problem is, that while disabling X will disable X11 for now, but with the first dependency on X11 it crawls back in)
I added that long string of --without-?? flags to packages/Makefile. Ideally, that stuff would all be disabled automatically, so that a ./ configure --with-pd=/path/to/pd would be all that is necessary.
Speaking of ./configure on Mac OS X, anyone tried a Universal Binary of Gem yet?
.hc
------------------------------------------------------------------------
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
Hans-Christoph Steiner wrote:
so i would _strongly_ recommend such restrictive settings (the problem is, that while disabling X will disable X11 for now, but with the first dependency on X11 it crawls back in)
I added that long string of --without-?? flags to packages/Makefile.
thanks. (though i think it compiled fine the last days, after i disabled the default quicktime/lqt check when the QuickTime-framework was found)
Ideally, that stuff would all be disabled automatically, so that a ./configure --with-pd=/path/to/pd would be all that is necessary.
i think we disagree here. ./configure --with-pd=/path/to/pd should be able to build a running version of Gem (here we agree (and this did not work!)), but there is no need to ignore available libraries on the building machine for the sake of packaging (for machines that lack this dylibs). this is what we have the configure-flags for...
Speaking of ./configure on Mac OS X, anyone tried a Universal Binary of Gem yet?
in theory it is just adding 2 flags to the compiler/linker, isn't it?
mfg.adr IOhannes
On 10/6/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Speaking of ./configure on Mac OS X, anyone tried a Universal Binary of Gem yet?
in theory it is just adding 2 flags to the compiler/linker, isn't it?
Plus universal builds of freetype and FTGL and the lipo stages to bind everything together.
On Oct 6, 2006, at 11:26 AM, chris clepper wrote:
On 10/6/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Speaking of ./configure on Mac OS X, anyone tried a Universal
Binary of
Gem yet?
in theory it is just adding 2 flags to the compiler/linker, isn't it?
Plus universal builds of freetype and FTGL and the lipo stages to bind everything together.
I am pretty sure that gcc handles calls to lipo, just like how gcc handles calls to the linker. Doing it manually is possible but probably not recommended.
Miller was able to get Pd building as a Universal with no direct calls to lipo.
.hc
------------------------------------------------------------------------
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
On Oct 6, 2006, at 11:19 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
so i would _strongly_ recommend such restrictive settings (the problem is, that while disabling X will disable X11 for now, but with the first dependency on X11 it crawls back in)
I added that long string of --without-?? flags to packages/Makefile.
thanks. (though i think it compiled fine the last days, after i disabled the default quicktime/lqt check when the QuickTime-framework was found)
Ideally, that stuff would all be disabled automatically, so that a ./configure --with-pd=/path/to/pd would be all that is necessary.
i think we disagree here. ./configure --with-pd=/path/to/pd should be able to build a running version of Gem (here we agree (and this did not work!)), but there is no need to ignore available libraries on the building machine for the sake of packaging (for machines that lack this dylibs). this is what we have the configure-flags for...
I don't think it should ignore anything, instead it should prioritize. If it finds both libquicktime and the Quicktime Framework on Mac OS X, it should choose the QuickTime framework over libquicktime. Right now, it does the opposite.
Speaking of ./configure on Mac OS X, anyone tried a Universal Binary of Gem yet?
in theory it is just adding 2 flags to the compiler/linker, isn't it?
In theory yes. It seems to be decently clean, so that should work. The other thing is to remove is anywhere where __APPLE__ or MACOSX assumes a specific endianness.
.hc
------------------------------------------------------------------------
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
Hans-Christoph Steiner wrote:
i think we disagree here. ./configure --with-pd=/path/to/pd should be able to build a running version of Gem (here we agree (and this did not work!)), but there is no need to ignore available libraries on the building machine for the sake of packaging (for machines that lack this dylibs). this is what we have the configure-flags for...
I don't think it should ignore anything, instead it should prioritize. If it finds both libquicktime and the Quicktime Framework on Mac OS X, it should choose the QuickTime framework over libquicktime. Right now, it does the opposite.
not quite. imo, it should use everything available. if (and only if) things conflict, then it should prioritize, right now, QuickTime framework _is_ prioritized over libquicktime (this was the fix for the buildfarm osx10.4 machine; one (1) week ago this prioritisation (or however this is called) was not done).
my proposal to use the series of --without flags was rather to use the dependencies on dylibs (like libdv, libquicktime (regardless of the conflict) and so on)
so now i think, we do agree here (though we probably misunderstand each other)
mfg.adr. IOhannes
-
chris clepper -
Hans-Christoph Steiner -
IOhannes m zmoelnig