FileZilla @3.5.1 fails to build wxWidgets @2.8.12 on 10.8 Mountain Lion

[roberthuston@…]

After upgrading to Mountain Lion, I installed a fresh version of MacPorts 2.1.2 and proceeded to reinstall all of my previous ports. Upon attempting to install FileZilla, I get an error when it tries to build wxWidgets @2.8.12. I found the "wxWidgets" thread that indicated people should use wxWidgets-devel on Mountain Lion, and I was able to get that to work. I then updated FileZilla's portfile to use wxWidgets-devel. However, when FileZilla runs its configuration phase, it fails to locate the wxWidgets static library and states "You need to use wxWidgets 2.8.x to compile this program." How can I get FileZilla to be happy with wxWidgets-devel? The "wxWidgets" ticket for the build failure under Mountain Lion was marked as "won't fix" so I'm assuming I need to patch FileZilla instead.

[valorisa]

Hello,

I have the same problem. I wish to install FileZilla on Mountain Lion but wxWidgets is needed. Unfortunatelly the command "sudo port -v install FileZilla" or "sudo port -v install wxWidgets" fails. I obtain the following message :

../include/wx/mac/carbon/​private.h:1459: error: ‘Cursor’ does not name a type
../include/wx/mac/carbon/​private.h:1488: error: ‘ClassicCursor’ does not name a type..

Otherwise "sudo port -v install wxWidgets-devel" works fine and also the method for compiling the libraries here : ​http://www.wxwidgets.org/docs/faqmac.htm#buildx

[roberthuston@…]

Unfortunately, when I try building wxWidgets-devel with the stdlib option (sudo port install wxWidgets-devel +sdl +stdlib +universal) I get more errors. I think I'll abandon getting FileZilla back up and running on MacPorts under Mountain Lion for now. Too much stuff is broken.

[brian@…]

Similar problem here. New install of Mountain Lion. New install of MacPorts. Unable to install the current FileZilla port. It's version 3.5.1.

Here's the error I get:

xxxxx$ sudo port install filezilla
Password:
--->  Computing dependencies for FileZilla
--->  Dependencies to be installed: wxWidgets
--->  Fetching distfiles for wxWidgets
Error: org.macports.fetch for port wxWidgets returned: wxWidgets does not build on 10.8 due to missing Carbon support, please use port wxWidgets30 instead
Error: Failed to install wxWidgets
Please see the log file for port wxWidgets for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_wxWidgets/wxWidgets/main.log
Error: The following dependencies were not installed: wxWidgets
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port filezilla failed

Would a new port of the current FileZilla 3.6.0.2 using wxWidgets30 work?

Thanks for any help!

--Brian

P.S. - I suppose I could use the native Aqua binary at ​http://filezilla-project.org, but I'd rather use the MacPorts version, if possible.

[whcordis@…]

Cc Me!

[mojca (Mojca Miklavec)]

Just quoting/repeating what I wrote in comment 12 in #38375 already:

I just checked FileZilla and otrproxy. Neither of them compiles with wxWidgets 2.9.

With FileZilla it's relatively explicit. 4 years ago a ticket (​http://trac.filezilla-project.org/ticket/4973) has been closed with wontfix and the following comment:

FileZilla requires wxWidgets 2.8

Note that wxWidgets 2.9 is an unstable development version, it shouldn't be used in a production environment.

even though they have a wx3 branch (​http://svn.filezilla-project.org/filezilla/FileZilla3/branches/), but they haven't touched it for three years and I didn't try to compile that one yet.

Someone submitted a bunch of patches in October 2012 (​http://trac.filezilla-project.org/ticket/8272). I'm not sure against which version exactly, but it's somewhere close to version 3.5.3 and I managed to apply the patches. They needed additional fixing (the patches have been tested on Windows & Linux, but some additional Mac code needed changes) and still didn't compile. They do nightly builds on a Leopard PowerPC machine.

Anyway: FileZilla requires some effort that goes beyond the scope of MacPorts. Someone really needs to collaborate with the upstream developers to get it working, otherwise it would be a lot of effort for very little benefit.

[mojca (Mojca Miklavec)]

provisionary patch for compiling FileZilla 3.7.3 against wxWidgets 2.9

[mojca (Mojca Miklavec)]

Here's a patch for compiling FileZilla 3.7.3 against wxWidgets 2.9 based on ​http://trac.filezilla-project.org/ticket/8272. It compiles fine, but I still experience a bunch of warnings during execution. If anyone is interested in playing around ...

[mojca (Mojca Miklavec)]

Cc Me!

[mojca (Mojca Miklavec)]

This should be "fixed" in r110262 and a couple of later "bugfix" commits. This means that FileZilla should be usable compiled against wxgtk-2.8 and conditionally (highly experimental, with problems) also against Cocoa-based wxWidgets 2.9.

For more extensive support please report to the above ticket and try to convince the upstream to do something about this.

If there are problems with building FileZilla (which is certainly possible), please open a new ticket with the exact error (complete main.log).