[L2Ork-dev] [PD] Upcoming pd-l2ork release teaser

Ivica Ico Bukvic ico.bukvic at gmail.com
Wed Sep 4 05:00:07 UTC 2013

Small correction, it built ok in my dev folder but when I checked out 
the entire tree into a new folder it failed just like yours did while 
compiling zexy. I just added files I failed to add earlier when I was 
updating zexy and am now testing to see if there are any other 
problems--so far it all looks good. The build tarball is approx. 30MB 
which is about right and the extra folder looks ok as far as I can tell. 
moocow/flite and other stuff never built successfully in the first 
place--this is something I will have to vet down the road as we slowly 
get rid of redundant doubles.


On 09/03/2013 10:40 PM, Ivica Ico Bukvic wrote:
> Also, to follow-up, I just tried building a script-based installer in
> Ubuntu with your patches and Andrew's tkpath fork merged, and a small
> update to moocow automated build script, and it built without a hitch
> over here.
> I will also try another clean pull into a separate folder to see if it
> builds fine as well.
> Best wishes,
> Ico
> On 09/03/2013 08:30 PM, Ivica Ico Bukvic wrote:
>> Many thanks for the feedback, Albert. Are you suggesting that
>> building a deb works but building a script-based installer fails? If
>> so, this may be simply due to a way paths are being interpreted.
>> Otherwise, if both builds fail it is a matter of a missing file. Yet,
>> my build doesn't have configure.ac and it build just fine. Seems to
>> me it may be another discrepancy between arch and Debian/Ubuntu?
>> On 09/03/2013 07:12 PM, Albert Graef wrote:
>>> On Tue, Sep 3, 2013 at 11:11 PM, Albert Graef <aggraef at gmail.com>
>>> wrote:
>>>> So it seems that
>>>> something in the installation process still isn't working quite right
>>>> on Arch. I'll dig into this tomorrow.
>>> Well, I'm getting build errors in moocow/gfsm and zexy, that's why the
>>> build bails out before most of the externals get installed. I
>>> overlooked that at first since it was buried deeply in my 2.8 MB build
>>> log.
>>> Not sure yet what the problem with gfsm is, but the externals/Makefile
>>> target for building zexy is definitely broken; it looks for
>>> configure.ac in externals/zexy which simply doesn't exist. And I get
>>> exactly the same compile errors on Ubuntu 12.04:
>>> make[2]: *** No rule to make target
>>> `/home/ag/tmp/pd-l2ork/externals/zexy/configure.ac', needed by
>>> `/home/ag/tmp/pd-l2ork/externals/zexy/configure'.  Stop.
>>> make[2]: Leaving directory `/home/ag/tmp/pd-l2ork/externals'
>>> make[1]: *** [externals_install] Error 2
>>> make[1]: Leaving directory `/home/ag/tmp/pd-l2ork/packages'
>>> make: *** [install] Error 2
>>> copying l2ork-specific externals...
>>> Could anyone with a pristine git checkout please see whether he can
>>> reproduce this?
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> http://disis.music.vt.edu/listinfo/l2ork-dev
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev

Ivica Ico Bukvic, D.M.A
Composition, Music Technology
Director, DISIS Interactive Sound & Intermedia Studio
Director, L2Ork Linux Laptop Orchestra
Head, ICAT IMPACT Studio
Virginia Tech
Department of Music
Blacksburg, VA 24061-0240
(540) 231-6139
(540) 231-5034 (fax)

More information about the L2Ork-dev mailing list