On Wed, 14 Jun 2006, IOhannes m zmoelnig wrote:
i just checked and noticed that "which pd" (which is used to determine where the pd-executable lives if no "--with-pd" is used) on osx returns something like the following (on stdout instead of stderr) on failure: "no pd in /bin /sbin /usr/bin /usr/sbin" and a positive error code!
A positive error code means that it failed, only 0 stands for success. Or maybe I just misunderstand what you want to say.
Günter
therefore there is no easy way to detect, whether the "which pd" failed and instead the pd executable is assumed to be "no pd in /bin/ ..." which of course is non-sense. then the linker checks whether it can build a bundle with "no pd in.." and fails.
however i should succeed if you give the full path like "--with-pd=/path/to/pd/bin/pd.exe" (the .exe suffix is just here to illustrate what i mean)
The SIMD check finds that the compiler accepts -msse2 on PPC. The check should check for the actual CPU or at least do a uname -s and uname -p like I suggested for the Pd endian checks.
i have no checked in a configure version that uses "uname -m" for this task and which won't test for e.g. "sse2" on ppc unless explicitely asked for with "--enable-sse2". "uname -p" is problematic, since it doesn't return anything useful ("unknown", or an error about an invalid flag) on my linux machines.
My configure skills are pretty weak so I need some help fixing this.
hopefully we can fix it together.
fgma.sdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev