It works. Great! I have a question. where is JACK option? It runs only with ALSA.
Jonghyun akntk On Mon, Sep 21, 2015 at 6:39 PM, Jonghyun Kim <agitato...@gmail.com> wrote: > now it seems works. thanks! > > jonghyun > > ===== > $ sudo dpkg -i pd-l2ork-x86_64-20150920.deb > (Reading database ... 474214 files and directories currently installed.) > Preparing to unpack pd-l2ork-x86_64-20150920.deb ... > Unpacking pd-l2ork (20150920) over (20150920) ... > Setting up pd-l2ork (20150920) ... > Processing triggers for mime-support (3.55ubuntu1.1) ... > Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... > Processing triggers for desktop-file-utils (0.22-1ubuntu2) ... > Processing triggers for bamfdaemon (0.5.1+14.10.20140925-0ubuntu1) ... > Rebuilding /usr/share/applications/bamf-2.index... > Processing triggers for man-db (2.7.0.2-2) ... > Processing triggers for hicolor-icon-theme (0.13-1) ... > Processing triggers for shared-mime-info (1.2-0ubuntu3) ... > Unknown media type in type 'all/all' > Unknown media type in type 'all/allfiles' > Unknown media type in type 'uri/mms' > Unknown media type in type 'uri/mmst' > Unknown media type in type 'uri/mmsu' > Unknown media type in type 'uri/pnm' > Unknown media type in type 'uri/rtspt' > Unknown media type in type 'uri/rtspu' > Processing triggers for ureadahead (0.100.0-16) ... > $ > ======= > > On Mon, Sep 21, 2015 at 4:18 PM, IOhannes m zmoelnig <zmoel...@iem.at> > wrote: > >> On 2015-09-21 03:42, Ivica Ico Bukvic wrote: >> > I think that was because it was built with libMagick++4 whereas 14.04 >> > and newer Ubuntu versions have libMagick++5. I am not sure why this >> > matters (sounds to me like something may be improperly symlinked >> > system-wise). >> >> i would say that Debian has a pretty well established system to avoid >> breakage of applications due to library incompatibilities. >> >> part of this scheme is to rename library packages (e.g. "libMagick++4" >> vs "libMagick++5") if and only if the two libraries are binary >> incompatible. >> usually this means that some previously exported symbols have vanished >> in the newer version. >> >> a specific application might not use those symbols at all and would thus >> not be affected by the incompatibility. >> but using symlinks (system-wide!) is certainly the right approach to >> break your system, and thus should be avoided. >> >> there are two solutions for this problem: >> - ship all dependencies (the w32 and OSX way) >> - link against the proper libraries (the linux distro way) >> >> fgmadrt >> IOhannes >> >> _______________________________________________ >> Pd-list@lists.iem.at mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >> > >
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list