[Slackbuilds-users] Linphone 3.12.0 not compiling on -current - but latest version does compile

Sebastian Arcus s.arcus at open-t.co.uk
Wed Dec 27 18:49:17 UTC 2023


I hope it's ok to get in touch about this. I am on Slackware -current 
64bits downloaded 25 Dec 2023. Linphone using the scripts from Ponce's 
Github repo fails to compile with the following error:

</snip>
warning: Tag 'DOT_TRANSPARENT' at line 2389 of file 'ortp.doxygen' has 
become obsolete.
          To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
warning: argument 'a4wide' for option PAPER_TYPE is not a valid enum value
Using the default: a4!
/tmp/SBo/linphone-3.12.0/oRTP/include/ortp/b64.h:292: error: unable to 
resolve link to 'b64::b64_encode2' for \link command (warning treated as 
error, aborting now)
make[4]: *** [Makefile:1014: doc/html/index.html] Error 1
make[4]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[3]: *** [Makefile:572: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[2]: *** [Makefile:435: all] Error 2
make[2]: Leaving directory '/tmp/SBo/linphone-3.12.0/oRTP'
make[1]: *** [Makefile:623: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/linphone-3.12.0'
make: *** [Makefile:551: all] Error 2
Failures:
   linphone: linphone.SlackBuild return non-zero


I've done a bit of digging, and according to the link below it might be 
something to do with ortp and a "finicky doxygen configuration" (search 
for this phrase down the page linked below). There is a patch suggested 
on that page. I'm a little bit out of my depth as to the significance of 
all this though.

https://aur.archlinux.org/packages/ortp

On the other hand - in case it helps - I tried downloading the latest 
Linphone (5.2.0) from Git and followed the instructions in the README 
file to compile and build it - and it worked just fine on my -current 
install. Is there a particular reason Linphone is on 3.12.0 in the SBo 
repo? I guess there could be some compatibility issues I'm not aware of.



More information about the SlackBuilds-users mailing list