GEM-dev August 2014

gem-dev@lists.iem.at

14 participants
32 discussions

Problem to get codeclist or dialog window with pix_record on MacOSX
by Jack 09 Aug '14

09 Aug '14

Hello, I have a problem, i try to get codeclist or the dialog window from [pix_record] on MacOSX.6.8 with Pd-ext 0.43.4 and Gem 0.93.3. When i create the gemwin and click on [codeclist( or [dialog(, i don't get anything : no dialog window or nothing from the third outlet. I have to send [record 1( and [record 0( to get the dialog window when i click on [dialog(. I guess [codeclist( doesn't work on MacOSX ? I miss something ? ++ Jack

2 1

Compiling Gem from git on osx mavericks + homebrew
by me.grimm 03 Aug '14

03 Aug '14

Hello, First time I have tried Homebrew on new Dev machine. With fink I didn't get an issue but following instructions here: https://github.com/avilleret/Gem/wiki/How-to-build-Gem-on-MacOSX-Mavericks when I ./autogen.sh I get: PATH: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin AUTORECONF: /usr/local/bin/autoreconf AUTOHEADER: /usr/local/bin/autoheader AUTOMAKE : /usr/local/bin/automake ACLOCAL : /usr/local/bin/aclocal LIBTOOL : /usr/bin/libtool LIBTOOLIZE: AUTOCONF : /usr/local/bin/autoconf running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: configure.ac: adding subdirectory extra to autoreconf autoreconf: Entering directory `extra' autoreconf: running: aclocal --force -I ../m4 autoreconf: configure.ac: adding subdirectory pix_artoolkit to autoreconf autoreconf: Entering directory `pix_artoolkit' autoreconf: running: aclocal --force -I ../../m4 autoreconf: running: glibtoolize --copy --force glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: putting macros in `../../m4'. glibtoolize: copying file `../../m4/libtool.m4' glibtoolize: copying file `../../m4/ltoptions.m4' glibtoolize: copying file `../../m4/ltsugar.m4' glibtoolize: copying file `../../m4/ltversion.m4' glibtoolize: copying file `../../m4/lt~obsolete.m4' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree. autoreconf: running: /usr/local/Cellar/autoconf/2.69/bin/autoconf --force configure:15430: error: possibly undefined macro: AC_LIB_APPENDTOVAR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/local/Cellar/autoconf/2.69/bin/autoconf failed with exit status: 1 HOST-OS : Mac OS X 10.9.4 (13E28) HOST-KERNEL: Darwin megrimms-Mac.local 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64 HOST-#CPU : 1 Ideas? Something with libtoolize/glibtoolize ... I also had a alocal problem earlier (something to the efect of it was not installed?) but it went away after "brew install automake" etc.... m On Mon, Jul 21, 2014 at 11:29 AM, Antoine Villeret < antoine.villeret(a)gmail.com> wrote: > 2014-07-21 16:39 GMT+02:00 IOhannes m zmoelnig via GEM-dev < > gem-dev(a)lists.iem.at>: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 2014-07-21 15:30, Antoine Villeret via GEM-dev wrote: >> > hello, >> > >> > I started a Wiki page with a step-by-step how-to here : >> > >> https://github.com/avilleret/Gem/wiki/How-to-build-Gem-on-MacOSX-Mavericks >> > >> > >> It's a work in progress >> > >> > feel free to merge / fork / improve or just read it :-) >> >> thanks for sharing. >> >> i've forked to umlaeute/Gem.wiki, fixed a couple of spelling errors >> and the like and pushed. >> > > thanks for the review > >> >> unfortunately there seems to be no way to do a pull-request for the wiki. >> >> so probably just do: >> >> $ git clone git@github.com:avilleret/Gem.wiki.git >> $ cd Gem.wiki >> $ git remote add umlaeute git@github.com:umlaeute/Gem.wiki.git >> $ git pull umlaeute master >> $ git push >> > done > >> >> :-) >> >> >> on a side-note: >> Gem should fall-back to a built-in `glew`, so i wonder why you needed >> to install it as well. is this related to >> https://github.com/umlaeute/Gem/issues/26 ?) >> > yes it is, at first I was stuck by this just because I don't try make > despite of the error > do I tried to install many things to see the effects > > I will remove the glew part > > + > a > >> >> fgasdr >> IOhannes >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1 >> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ >> >> iQIcBAEBCAAGBQJTzSYeAAoJELZQGcR/ejb4r/MP/1YrpXCUQ6d7x/48tpK23I3U >> I738TLp8o9FG4OVg9x4SZr5bWHl+0egegstkjxyGK92wwyqFKGAQ2mlNM93INIht >> 8+iFrKXKGsqgZ4xdF8Gm0uthZJl9Y4YvEu5XudJGLfBHR4gLL6+/FmIH08Eg9rv2 >> I0SPwZ2QW8OMkXeEzysq3umADyqGsBzNAwsgqZXr5PNWzfx4r5iDuxmj1TitUnlS >> msfxanUmsO3Lv+G9jzFaDODeMQl2kQZHBVYGUeK3fLVvXqvGu3g4pSJ+GtjlQugW >> Wo2dNffyJRuauBOHEIQAuqmakal7Df6bXSz9YHlRvd6bRe3fj/IznCcDaEe9Aksu >> zF2qmyEYYLvjqkpFmmntp7vA96odl++ywbcPlNuX9vhjmLPCA7CdaI5RHI9rrl8t >> 8m41PRiQTuilgTInU6yvfl3ZhZNwPKcsb1YKogPRTIj741ncdb8NNwd9HbN6MIPi >> MQQSg9787RMGPaayM0gluHrUI9TEJswbYg2NlB9fCXi6TZWpkwUsOE+V8ubiCpei >> A+5MF7/ZOS0sJZzFR44/7pXPlTJME+Jf8d+LnVM7TNl69CpFVO/afkP8DwnnjO89 >> q3d4e112oxJEKaoQ7FbG4oMslVgyOQr2Yqa6X8nNzpUCpN4w1+qqAVyThqJPBn5H >> zlc49R4nAsE/A7At7v0y >> =4mRz >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev(a)lists.iem.at >> http://lists.puredata.info/listinfo/gem-dev >> > > > _______________________________________________ > GEM-dev mailing list > GEM-dev(a)lists.iem.at > http://lists.puredata.info/listinfo/gem-dev > > -- ____________________ m.e.grimm | m.f.a | ed.m. megrimm(a)gmail.com _________________________________

3 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev August 2014