Hi,
I try to build LO 6.1 in release mode as I did for previous versions, 
but it fails with the following error messages:
/home/libo/60/instdir/program/libpyuno.so has suspicious NEEDED: 
libpython3.5m.so.1.0
/home/libo/60/instdir/program/libucpftp1.so has suspicious NEEDED: 
libcurl-gnutls.so.4
/home/libo/60/instdir/program/libucpcmis1lo.so has suspicious NEEDED: 
libcurl-gnutls.so.4
/home/libo/60/instdir/program/libsvllo.so has suspicious NEEDED: 
libcurl-gnutls.so.4
/home/libo/60/instdir/program/libpythonloaderlo.so has suspicious 
NEEDED: libpython3.5m.so.1.0
/home/libo/60/postprocess/CustomTarget_check_dynamic_objects.mk:20 : 
la recette pour la cible 
« /home/libo/60/workdir/CustomTarget/postprocess/check_dynamic_objects/check.done » 
a échouée
make[1]: *** 
[/home/libo/60/workdir/CustomTarget/postprocess/check_dynamic_objects/check.done] 
Erreur 1
I am running Ubuntu 16.04 x86-64 and the version of curl installed by 
the system is 7.47.0, using internal curl did not help.
I tried to build with the option --enable-python=fully-internal without 
success.
Is there something I can do to fix the problem on my PC ?
Best regards
JBF
--
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.
Disclaimer: my Internet Provider being located in France, each of our
exchanges over Internet will be scanned by French spying services.
Context
- Release build fails for LO 6.1.0.1.0+ · Jean-Baptiste Faure
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.