Damian wrote: > Paul Mossman wrote: > > Paweł wrote: > >> On 2009-05-06, at 17:05, Paul Mossman wrote: > >> > >>> Pawel wrote: ... > >>>> I am trying to compile sipXecs using scripts from EDE. I > know they > >>>> are not FC10 ready yet but I'll ask anyway. Any hints > how to avoid > >>>> the following error? : > >>>> > >>>> make_output.txt: cd - cd /home/sipx/BUILD/sipXproxy/src/cdr/pkg > >>>> zip -r sipxcallresolver-2.0.0.zip sipxcallresolver-2.0.0 [cut] > >>>> adding: > >> sipxcallresolver-2.0.0/system-test/data/callresolver-config > >>>> (deflated 41%) adding: sipxcallresolver-2.0.0/system-test/ > >>>> call_resolver_purge_test.rb (deflated 75%) cd - rake aborted! > >>>> undefined method `empty?' for nil:NilClass > >>>> > >>>> (See full trace by running task with --trace) make[3]: *** > >>>> [package-gem] Error 1 make[3]: Leaving directory > >>>> `/home/sipx/BUILD/sipXproxy/src/cdr' make[2]: *** > >>>> [install-recursive] Error 1 > >>> Hi Pawel. I haven't even got this far with the EDE on Fedora 10. > >>> Though, I will be tacking it in the next week or two. > >>> > >>> However I'm guessing this error is specific to F10, and not > >> the EDE. > >>> I know others are developing sipXecs on F10, so it is certainly > >>> possible to do. > >>> > >>> Have any of you aforementioned others come across this error? > >>> > >> Pls, I'll accept any hint. I am stuck with my new devel > station setup > >> and cannot make any progress on porting my ACD to sipXecs 4.0 :( > > > > I don't even get to this point yet. > > > > > > Firstly there was a failure to install the nsis package from the > > devel_fedora_env.sh script, run as root. It was easy to > fix, and the > > change has now been committed in revision 15446. > > > > Did you encounter this failure? Note that it causes the > > devel_fedora_env.sh script to stop running. So many critical steps > > would not have completed, including ruby gems installs, > which sounds > > like it could be related to your package-gem build error above... > > > > You may want to wget the latest devel_fedora_env.sh, and ensure it > > runs to completion. (It's designed to be safely re-run > after it quits > > due to an error.) > > > > > > Secondly there was a failure to install the sipx-freeswitch > RPM from > > the devel_build_install.sh script, run as sipx. This > happens before > > the build step. The problem is that the sipx-freeswitch > RPM requires > > older versions of the libcrypto.so and libssl.so libraries, > and also a > > library > > (libgnutls.so.13) that isn't present. Understandable, > since this is > > Fedora 10 but that RPM was built on Fedora 8. > > (http://sipxecs.sipfoundry.org/temp/sipXecs/main/FC/8/i386/RPM/) > > > > Paweł, did you encounter this failure? How about others who are > > developing sipXecs on Fedora 10? Did you just break down and build > > the FreeSWITCH RPM from source? > > > > I am pretty sure I built Freeswitch and other dependencies > from source. > It's not just freeswitch: you do need to build 3rd party > dependencies from source until there is an official build > loop on sipfoundry.org. Binaries do not have to work.
OK, I will add building of FreeSWITCH from source to the devel_build_install.sh script. As for the other dependency RPMs, they are installed by the earlier devel_fedora_env.sh script. It is kludged to install the Fedora 8 RPMs, despite being Fedora 10. Taboo I know, but it seems to work for now. The problem is we don't yet have a Fedora 10 official build loop. But hopefully the Fedora 10 EDE will make it easier to get one set up. My hope is to avoid building these dependencies from scratch in the EDE. Building the FreeSWITCH RPM on the other hand seems like it will be a useful feature to have in the EDE. Paweł, regarding your package-gem build error... My build succeeded without issue. So I'm pretty sure your error is indeed related to the devel_fedora_env.sh script not completing. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
