Hi everyone,

I've been trying for a solid few days to get iem_dp working on my Mac (for double precision lookup of long arrays), but I seem to have reached the limits of my abilities.

I downloaded the library from https://git.iem.at/pd/iem_dp/tree/master which contains the helpfiles, .c files for each object, and four makefiles for different architectures (including makefile_darwin, which I assume is the one I want for MacOS 10.12. I have no experience with compiling files, so I tried downloading Command Line Tools, and ran "make -f makefile_darwin" in Terminal, but I only get errors (see below).

Does anyone know what the problem might be? Or, does anyone happen to have iem_dp compiled for pd_darwin?

touch symtodp.c
cc -DPD -DUNIX -g -Wall -W -Werror -Wno-unused -Wno-parentheses -Wno-switch -O2 -fno-strict-aliasing -I. -I"/Applications/Pd-0.47-1.app/Contents/Resources"/src    -DPD -I. -I"/Applications/Pd-0.47-1.app/Contents/Resources"/src -c -o symtodp.o symtodp.c
symtodp.c:86:50: error: unused parameter 's' [-Werror,-Wunused-parameter]
static void symtodp_list(t_symtodp *x, t_symbol *s, int ac, t_atom *av)
                                                 ^
symtodp.c:96:61: error: unused parameter 'ac' [-Werror,-Wunused-parameter]
static void symtodp_anything(t_symtodp *x, t_symbol *s, int ac, t_atom *av)
                                                            ^
symtodp.c:96:73: error: unused parameter 'av' [-Werror,-Wunused-parameter]
static void symtodp_anything(t_symtodp *x, t_symbol *s, int ac, t_atom *av)
                                                                        ^
symtodp.c:120:37: error: unused parameter 'x' [-Werror,-Wunused-parameter]
static void symtodp_free(t_symtodp *x)
                                    ^
4 errors generated.
make: *** [symtodp.o] Error 1```

OK, so applying the pvoc~ 64-bit patch was rather easy:

patch pvoc~.c < bsaylor_pvoc~.c.patch

But unfortunately I'm back to my original problem—the makefile that is included with bsaylor throws a bunch of errors when I try to compile the library, and I don't have any expertise (besides a few days ago with iem_dp) to guide my troubleshooting. I spent a good chunk of the day editing everything I could make sense of in the makefile (changing the path from Pd-extended.app to Pd-0.47-1-64bit.app, deleting things that seemed to be causing warnings), but still no luck.

clang: error: unknown argument: '-ftree-vectorizer-verbose=2'

...

fatal error: 'm_pd.h' file not found

...

/usr/include/sys/cdefs.h:761:2: error: Unsupported architecture

...

In file included from /usr/include/stdint.h:52:
/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_blkcnt_t;      /* total blocks */

In file included from /usr/include/stdint.h:52:
/usr/include/sys/_types.h:68:9: error: unknown type name '__darwin_natural_t'
typedef __darwin_natural_t __darwin_mach_port_name_t; /* Used by mach */

Does anybody know of a very simple step-by-step beginner's guide to compiling objects/libraries from source? I see the words "just recompile for your system" quite a bit, but even with several days of unguided googling, I can't say I feel like I understand even the basics. (other than running a makefile & hoping for the best...) I'm not averse to rolling up my sleeves & learning how to do it, rather than bug everyone for help every time I run into an error.

the unsupported architecture probably points to trying to compile for ppc if I had to guess.
You also need to point to the correct location of pd. Try taking out all -arch ppc and -ftree-vectorizer-verbose=2 from the makefile & run
make PD_PATH=/Applications/Pd-0.47-1/Contents/Resources PD_INCLUDE=/Applications/Pd-0.47-1.app/Contents/Resources/include

as for learning this stuff, unfortunately I have no concrete advice besides learning common compiler args, the make program and the gnu build tools in general. I also usually do a lot of googling of errors & such (modern luxuries)

http://autotoolset.sourceforge.net/tutorial.html
http://clang.llvm.org/docs/UsersManual.html

Thanks for those links to compiling info, much appreciated!

I think I'm getting closer... I realized that the makefile is pointing to /include because that's where m_pd.h is located in Pd-Extended, but that file is in /src in the vanilla versions I'm using. I tried changing that path, and also tried pointing to a version of Pd-Extended that I have, but now I get this:

fatal error: 'fftw3.h' file not found

The bsaylor library comes with a /libs folder containing libfftw3.3.dylib and libfftw3f.3.dylib (required for partconv~ and pvoc~). Perhaps the makefile is looking for these libraries when compiling? I don't see a fftw3.h file anywhere in the source code of pd (including extended).

install fftw3, I recommend using Homebrew http://brew.sh. In order to store a dynamic library in a location other than the place it was linked from requires some otooling and install_name_tooling (which I wouldn't mess with), (e.g. packages/darwin_app/embed-McOSX-dependencies.sh)

I'm not sure which version of bsaylor you have but mine doesn't have a libs folder

Success! My internet has been down for a week, so had to wait until today before I could try installing fftw via Homebrew. I was able to do so without much trouble, and after re-editing the bsaylor makefile & recompiling, the patched version of pvoc~.pd_darwin is up & running properly in 64-bit!

I really appreciate your help! I wouldn't have known where to begin without your helpful advice.

Cheers,
-Jon

@beep.beep Hi, I have the exact same problem with pvoc~ on macOS sierra and pd vanilla 0.47.1-64bit. I have installed fftw via homebrew and applied the bsaylor_pvoc~.c patch, but I'm having troubles understanding what to do next. I have never compiled an external from the source code and I have no idea how to go about it.
What kind of changes did you end up making to the makefile, and what do I do with it next?

Sorry if this is too basic but it's all a bit alien to me. Thanks so much for your help.

@weightless

Hi there,

Indeed, if you’ve read the long thread above you know that this was my first time compiling as well, so I can definitely relate to the feeling of flying blind!

5 months later I can’t quite remember which edits I made to the bsaylor makefile, but I’m pretty sure this one is the final version that ended up working for me:

Makefile

If memory serves, I removed all objects other than pvoc~.c and partconv~.c from “SOURCES” (I think because the others were already working in 64 bit?), and also made sure the path pointed to “PD_PATH = /Applications/Pd-0.47-1-64bit.app/Contents/Resources”. Then I ran “make” (with the patched pvoc~.c in the same directory as the makefile, and fftw installed as noted), and got my new pvoc~.pd_darwin file to replace the old (non-64 bit) version in my bsaylor folder.

It was rather satisfying to successfully compile, but I still can’t say that I understand most of the errors that pop up during the process. It’s also entirely possible I’m forgetting other key steps that I took, as I was beating my head against this for days at the time. If it helps, here’s the darwin file that I got working on 64 bit:

pvoc~.pd_darwin

@beep.beep

Thank you so much!

I have just copied the pvoc~.pd_darwin to "Contents/Resources/extras/bsaylor" inside the Pd0.47-1-64bit package and deleted the old "pvoc~.d_fat", and it works! I had to rename your file and add the ~, but it works with no errors this time.

One thing I'm not so sure about is that originally in the bsaylor folder there were no pd_darwin files for any of the objects, which have .d_fat extensions instead, I wonder why that is? I installed the library from the Help/Find externals menu.

Anyway, it's just out of curiosity.
Thank so much for your help, it made my day!

@weightless

Happy to help! Glad to hear it worked for you. I suppose the forum automatically removes special characters like ~ from filenames when they're uploaded... good to know for future reference.

As alexandros noted (much) earlier in this thread, d_fat is another valid Mac OS format. I see 2 versions of bsaylor available for Mac via "Find externals", perhaps the one you downloaded was a d_fat version? In any case, if it works, it works!