search

jambonz / jambonz-infrastructure

packer and cloudformation templates for creating EC2-based jambonz deployments
23 stars 29 forks source link

Packer still fails to build freeswitch on GCP after recent spandsp change #55

Closed rjp44 closed 1 year ago

rjp44 commented 1 year ago

Following https://blog.jambonz.org/deploying-jambonz-on-google-cloud, the jambonz-mini disk image gets produced, but on running it, Jambonz fails opaquely because there is no freeswitch binary in the disk image.

I think this is because configure.ac in /usr/src/freeswitch/libs/spandsp sets a PREREQ of autoconf2.71, but the requested GCP image is running Debian 5.10.179-1 which has autoconf2.69.

Will confirm and try to find a fix.

rjp44 commented 1 year ago

Looks like the current state of the master branch of spandsp is pretty broken, which in turn breaks freeswitch builds here:

  1. https://github.com/freeswitch/spandsp/commit/d9681c3747ff4f56b1876557b9f6d894b7e6c18d changed spandsp to hard require (but doesn't seem to need) autoconf 2.71, Debian Bullseye ships 2.69 so won't build.
  2. A breaking API change made it into spandsp at some point adding two more parameters to v18_init() which Freeswitch v1.10.5 doesn't know to provide.

I have a patch to make packer builds work for me again by patching around both the above, can submit a PR if it will help anyone, or maybe the solution is to specify a specific more ancient spandsp commit until the above get sorted there.

rjp44 commented 1 year ago

Turns out the actual solution is much simpler, there is a one liner to check out a pre-breakage commit of spandsp that is in the AWS build build script but hasn't been copied to the GCP version.