[SOLVED] libfilezilla-0.17.0

3rensho · 06-18-2019, 01:44 AM

Built the new libfilezilla this morning and then tried to rebuild the current filezilla. That failed stating that I need to build it with C++17. Is that compiler available for Slackware anywhere?

business_kid · 06-18-2019, 04:33 AM

Could you show us the exact error?

3rensho · 06-18-2019, 07:14 AM

Here ya goes -

#
In file included from /usr/include/libfilezilla/libfilezilla.hpp:4,
from ../../src/include/libfilezilla_engine.h:12,
from filezilla.h:1:
/usr/include/libfilezilla/private/defs.hpp:10:4: error: #error You need to use a C++17 compiler. Try passing -std=c++17 as compiler flag.
10 | #error You need to use a C++17 compiler. Try passing -std=c++17 as compiler flag.
| ^~~~~
In file included from /usr/include/libfilezilla/libfilezilla.hpp:7,
from ../../src/include/libfilezilla_engine.h:12,
from filezilla.h:1:
/usr/include/libfilezilla/string.hpp:38:14: error: ‘string_view’ in namespace ‘std’ does not name a type
38 | typedef std::string_view native_string_view;
| ^~~~~~~~~~~
/usr/include/libfilezilla/string.hpp:38:9: note: ‘std::string_view’ is only available from C++17 onwards
38 | typedef std::string_view native_string_view;
| ^~~
/usr/include/libfilezilla/string.hpp:45:47: error: ‘string_view’ is not a member of ‘std’
45 | native_string FZ_PUBLIC_SYMBOL to_native(std::string_view const& in);
| ^~~~~~~~~~~
/usr/include/libfilezilla/string.hpp:45:47: note: ‘std::string_view’ is only available from C++17 onwards
/usr/include/libfilezilla/string.hpp:51:32: error: redefinition of ‘fz::native_string fz::to_native’
51 | native_string FZ_PUBLIC_SYMBOL to_native(std::wstring_view const& in);
| ^~~~~~~~~
/usr/include/libfilezilla/string.hpp:45:32: note: ‘fz::native_string fz::to_native’ previously declared here
45 | native_string FZ_PUBLIC_SYMBOL to_native(std::string_view const& in);
| ^~~~~~~~~
/usr/include/libfilezilla/string.hpp:51:47: error: ‘wstring_view’ is not a member of ‘std’
51 | native_string FZ_PUBLIC_SYMBOL to_native(std::wstring_view const& in);
| ^~~~~~~~~~~~
/usr/include/libfilezilla/string.hpp:54:53: error: ‘is_same_v’ is not a member of ‘std’; did you mean ‘is_same’?
54 | template<typename T, typename std::enable_if_t<std::is_same_v<native_string, typename std::decay_t<T>>, int> = 0>
| ^~~~~~~~~
| is_same
/usr/include/libfilezilla/string.hpp:54:53: error: ‘is_same_v’ is not a member of ‘std’; did you mean ‘is_same’?
54 | template<typename T, typename std::enable_if_t<std::is_same_v<native_string, typename std::decay_t<T>>, int> = 0>

#

ponce · 06-18-2019, 07:41 AM

you need an svn snapshot of filezilla if you want to build it against libfilezilla-0.17.0, there isn't a release tarball that builds against the new 0.17.0 library.

create a tarball with

Code:

svn co https://svn.filezilla-project.org/svn/FileZilla3/trunk FileZilla
svn export FileZilla filezilla-r9335
tar Jcf FileZilla_r9335_src.tar.bz2 filezilla-r9335

then edit the filezilla.SlackBuild on SBo like

Code:

--- ./filezilla.SlackBuild.orig 2019-06-18 14:19:13.449170435 +0200
+++ ./filezilla.SlackBuild      2019-06-18 14:37:56.419170435 +0200
@@ -21,7 +21,7 @@
 # THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=filezilla
-VERSION=${VERSION:-3.42.1}
+VERSION=${VERSION:-r9335}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -76,6 +76,8 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
+autoreconf -vi
+
 ./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \

3rensho · 06-18-2019, 07:46 AM

Thank you Ponce. I'll stick with the older Filezilla. Works fine as is. Whomever put my error output in a scroll box, thank you. I just looked up

Code:

 code in a box

and was about to do that.

Went ahead and built with your recipe. Worked fine building against 0.17.0

kgha · 06-28-2019, 02:05 AM

I didn't bother upgrading libfilezilla until a stable filezilla-3.43 was released, which happened yesterday. On -current, building libfilezilla-0.17.1 and filezilla-3.43.0 using the SBo scripts and simply editing the version number was straightforward. In other words, with the latest filezilla tarball, ponce's workaround is no longer necessary.