Arch Linux User Repository

PSA: I've started hosting this and all its dependencies as prebuilt packages (x86_86 only) in my repository for those that want to install them using pacman without messing around with building from the AUR.

@brackenhill-mob Upon further investigation it seems like archlinux c-client does not include imap/linkage.c. You can manually build a package that includes it like this (maybe the paths might not be right, but you should be able to follow along):

mkdir -p ~/builds
cd ~/builds
git clone --single-branch -b packages/imap https://github.com/archlinux/svntogit-packages.git ~/builds/c-client
cd ~/builds/c-client/trunk
# Add the following line to PKGBUILD at the end of the `package_c-client` function:
# install -D -m644 c-client/c-client.a $pkgdir/usr/lib/c-client.a
makepkg
sudo pacman -U c-client-2007f-*.tar.xz

The last line installs the newly build package including the linkage.c file.

I had to change the PKGBUILD of the asterisk package, too:

Replace

./menuselect/menuselect --disable BUILD_NATIVE

with

./menuselect/menuselect --disable BUILD_NATIVE --enable app_voicemail_imap

I guess as long as getting imap/linkage.c is a manual process it won't be possible for the asterisk package to officially enable the IMAP support.

This has been added as a bug report: https://bugs.archlinux.org/task/69016

@brackenhill-mob You might want to try the c-client package. It includes imap/linkage.h.

@nkukard I "borrowed" linkage.c from my Ubuntu server - I now have a working build. I can't find which package contains this file on Ubuntu - many moons ago it was in the uw-imap source code from Uni of Washington but I could find their repository to download it.

@brackenhill-mob You have a very good point there, I wrongly assumed just enabling imap support with --with-imap=system sorted it out :(

I get the same build error as you, missing imap/linkage.c

@nkukard OK I've just looked at my scripts for Ubuntu. --with-imap=system is required.

But my build fails with a missing /usr/lib/imap/linkage.c which is not in the c-client nor imap packages (it exists in Ubuntu).

Please can you set app_voicemail_imap in menuselect and try your build to see if it completes.

@nkukard I downloaded the snapshot for 18.1.0-2 as it hadn't hit the repositories at the time, and app_voicemail_imap is not checked in menuselect so the .so is still not being built

HTH

@nkukard I'm new to running Asterisk under Arch (coming from Ubuntu Server) so I may not understand how the Arch system works in this case. So at the risk of telling you stuff you already know... ;)

The 3 voice mail options if you run make menuselect manually create 3 different .so files. With your 18.1.0 package, only app_voicemail.so was created but the /etc/asterisk/modules.conf file told the server to load app_voicemail_imap.so which didn't exist. I've always built Asterisk from source and used make menuselect to setup the system for my needs, so in this case I would check all 3 options to generate the 3 .so files and let the user decide what to load in modules.conf. If you check those settings do you need a build dependency?

HTH

@Astroturf, thanks for the link. Updated to use bundled version.

@brackenhill-mob, please see https://www.asterisk.org/announcing-a-new-compile-option-for-app_voicemail-storage/. As far as I can see "imap" was never a build dependency, nor could of of worked due to the imap linking issue. Nonetheless, I've added imap as a build dep and fixed the linker options. Not sure I like it though. Willing to take improvement suggestions.

Agree with @Astroturf re pjproject (especially as it would not compile for me!).

So I downloaded v18.1 from your repository and you appear to have compiled the wrong app_voicemail - I've got app_voicemail.so when it should be app_voicemail_imap.so.

If you've renamed the .so file for some reason, then /etc/modules.conf is wrong.

TIA

What is the reason the bundled version of pjproject is not used? It is the recommended default since Asterisk 15. Asterisk crashes for me when using the pjproject dependency. It works just fine when removing --with-pjproject-bundled=no from PKGBUILD. The bundled version of pjproject also has a very specific config_site.h & a few extra patches (https://github.com/asterisk/asterisk/tree/master/third-party/pjproject/patches).