Opened 2 years ago
Closed 2 years ago
#12740 closed Bug report (rejected)
FileZilla 3.60.1 fails to build on Mageia Cauldron
Reported by: | kekePower | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | ||
Component version: | 3.60.1 | Operating system type: | Linux |
Operating system version: |
Description (last modified by )
Hi.
There is a long list of compilation errors when I try to build FileZilla on Mageia Cauldron.
gcc -DHAVE_CONFIG_H -I. -I../../config -DNO_GSSAPI -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -Wall -c -o libfzputtycommon_a-sshsha.o `test -f 'sshsha.c' || echo './'`sshsha.c In file included from /usr/lib/gcc/i586-mageia-linux/12/include/immintrin.h:98, from sshsha.c:345: /usr/lib/gcc/i586-mageia-linux/12/include/avx512fp16intrin.h:38:9: error: '_Float16' is not supported on this target 38 | typedef _Float16 __v8hf __attribute__ ((__vector_size__ (16))); | ^~~~~~~~
Here is the full log file: https://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20220624173422.papoteur.duvel.689132/log/filezilla-3.60.1-3.mga9/build.i586.0.20220624173643.log
Please let me know if you need more information.
Thanks in advance.
Attachments (2)
Change History (8)
by , 2 years ago
Attachment: | FileZilla-build.i586.0.20220624173643.log added |
---|
comment:1 by , 2 years ago
Description: | modified (diff) |
---|
comment:2 by , 2 years ago
Status: | new → moreinfo |
---|
comment:3 by , 2 years ago
Status: | moreinfo → new |
---|
Hi Tim.
The patch is only for pugixml and isn't related to the issue afaics.
% more filezilla-3.51.0-mga-system-pugixml.patch diff --git a/FileZilla/src/engine/Makefile.am b/FileZilla/src/engine/Makefile.am index 2de4f6c..838bb4a 100644 --- a/FileZilla/src/engine/Makefile.am +++ b/FileZilla/src/engine/Makefile.am @@ -143,6 +143,10 @@ libfzclient_private_la_LDFLAGS = -no-undefined -release $(PACKAGE_VERSION_MAJOR) libfzclient_private_la_LDFLAGS += $(LIBFILEZILLA_LIBS) libfzclient_private_la_LDFLAGS += $(IDN_LIB) +if HAVE_LIBPUGIXML +libfzclient_private_la_LDFLAGS += $(PUGIXML_LIBS) +endif + dist_noinst_DATA = engine.vcxproj CLEANFILES = filezilla.h.gch
When this patch is omitted, it fails to build due to pugixml.
After the latest round of updates to Mageia Cauldron I was able to compile it on x86_64, however it still fails on i586 with the same error on our build system.
I'm not a programmer and am unable to "fix" this.
Hints or pointers would be much appreciated.
by , 2 years ago
Attachment: | FileZilla-build.i586.0.20220627070203.log added |
---|
comment:5 by , 2 years ago
Status: | moreinfo → new |
---|
The other patch in the log file attached was just a test on my side that has since been removed.
Here is the latest build log with only 1 patch.
https://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20220627070105.kekepower.duvel.2043284/log/filezilla-3.60.1-3.mga9/build.i586.0.20220627070203.log
comment:6 by , 2 years ago
Resolution: | → rejected |
---|---|
Status: | new → closed |
In file included from /usr/lib/gcc/i586-mageia-linux/12/include/immintrin.h:98, from sshsha.c:347: /usr/lib/gcc/i586-mageia-linux/12/include/avx512fp16intrin.h:38:9: error: '_Float16' is not supported on this target 38 | typedef _Float16 __v8hf __attribute__ ((__vector_size__ (16))); | ^~~~~~~~
It comes from a system header. It looks like your compiler cannot handle one of its own header files.
Closing as this does not appear to be an issue with FileZilla.
Consider this test program and compile it with gcc -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables
#include <immintrin.h> int main() { return 0; }
Please contact your compiler package maintainer for further assistance.
You are applying custom patches to FileZilla. We cannot support modified versions of FileZilla.
Do you still experience this issue with an unmodified FileZilla?