Forgot to copy the list....
On Feb 6, 2013 3:07 PM, "Charles Goyard" <cg@fsck.fr> wrote:
>
> Hi,
>
> IOhannes m zmoelnig wrote:
> > On 2013-02-06 14:20, Charles Goyard wrote:
> > > I guess it's more a bug of Gem install script rather than pd-l2ork,
> > > but I just wanted to point that out.
> > Gem's "install script" (aka Makefile) installs everything, including
> > all compiled backends.
> > what makes you say that there is a bug here?
>
> You're right. I tried from crash with Gem alone and everything is ok:
> make clean
> git pull
> aclocal
> ./autogen.sh
> # ^-- btw this two commands are missing from the readme.txt
> ./configure --with-pd=/opt/pd-vanilla-0.43/ --prefix=/opt/gem
2 questions:
1. Why are you compiling gem separately when pd-l2ork compiles it for you and includes it with its binary package?
2. Why are you trying to use pd-vanilla includes with pd-l2ork (unless you are using pd instead of pd-l2ork)? The two are not compatible and as I indicated on the site with a huge warning box mixing the two will cause crashes and unexpected behavior.
> make
> sudo make install
>
> When all goes smooth on first time, everything is ok.
> However, it seems that if something fails during compilation and you
> rerun make, then the .so files are not copied if they were produced by
> the former run of make. It already occured to me when building
> pd-extended a few months back. It can be a dependency problem in the
> various targets, a bug in make, something wrong with my system, a
> personal problem with my cat... Whatever the cause, I get a source
> directory with everything: sources, gem.pd_linux and *.so, and an install
> directory with everything but the *.so files (yes, the gem.pd_linux gets
> copied).
>
> I'm not sure if it's a bug or a feature, so apologizes for using the
> wrong word. Maybe it's worth writing in the README.txt what a make clean
> can be necessary on some cases.
>
>
> Ivica Bukvic wrote:
> > How did you install pd-l2ork?
>
> From source with archlinux's PKGBUILD, with cwiid missing. So I first
> ran a build, which failed, and then fixed the problem, rerun the build
> and got into the problems described above.
>
>
> > Again, I need as much information as possible about how you installed the
> > software.
>
> Well, I'll say the problem comes from make/fix/make. Obviously it's not
> that important at all. There is/was the same kind of problem in
> pd-extended with ln -s other existing symlimks that forces you to clean
> and rebuild everything (I reported that on sf) after hours of
> compilation just because a symlink exists. Annoying ain't it ?
>
> Thank you all for your being patient :), and of course for your great
> software !
>
> --
> Charles
>
> _______________________________________________
> Pd-list@iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list