[MacPorts] #41832: Can't build FileZilla
#41832: Can't build FileZilla -------------------------------+-------------------------------- Reporter: michael_hodgins@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: filezilla -------------------------------+-------------------------------- sudo port install filezilla gives this error: Error: org.macports.build for port FileZilla returned: command execution failed -- Ticket URL: <https://trac.macports.org/ticket/41832> MacPorts <http://www.macports.org/> Ports system for OS X
#41832: Can't build FileZilla --------------------------------+----------------------- Reporter: michael_hodgins@… | Owner: rudloff@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: filezilla | --------------------------------+----------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => rudloff@… Old description:
sudo port install filezilla gives this error:
Error: org.macports.build for port FileZilla returned: command execution failed
New description: sudo port install filezilla gives this error: {{{ Error: org.macports.build for port FileZilla returned: command execution failed }}} -- Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers filezilla}}}). -- Ticket URL: <https://trac.macports.org/ticket/41832#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#41832: Can't build FileZilla --------------------------------+----------------------- Reporter: michael_hodgins@… | Owner: rudloff@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: filezilla | --------------------------------+----------------------- Comment (by mojca@…): The error is {{{ wxdbusconnection.cpp:69:69: error: use of undeclared identifier 'pthread_self' bool CalledFromThread() const { return !pthread_equal(m_parent_id, pthread_self()); } ^ wxdbusconnection.cpp:123:16: error: use of undeclared identifier 'pthread_self' m_parent_id = pthread_self(); ^ 2 errors generated. }}} Man page is here and I don't see any reference mentioning the command being removed in 10.9: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPa... Does it help if you try {{{ sudo port clean filezilla sudo port patch filezilla cd $(port work filezilla) # then edit filezilla-3.7.3/src/dbus/wxdbusconnection.cpp # add: #include <pthread.h> sudo port -v build filezilla }}} -- Ticket URL: <https://trac.macports.org/ticket/41832#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
Ran into the same error on OS-X Mavericks and is seemed to be caused by not having XCode command line tools installed. After installing the command line tools, installing FileZilla succeded. Nevertheless: the FileZilla GUI looks plain *ugly* when running the macports package. Better download a compiled version from the FileZilla project homepage, to receive something you can look at without too mnuch pain. (No retina support on either package yet...) -- View this message in context: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-41832-Can-t-build-FileZil... Sent from the MacPorts - Tickets mailing list archive at Nabble.com.
On Jan 6, 2014, at 11:47 AM, lhaeger <lothar.haeger@gmx.net> wrote:
Ran into the same error on OS-X Mavericks and is seemed to be caused by not having XCode command line tools installed. After installing the command line tools, installing FileZilla succeded.
Nevertheless: the FileZilla GUI looks plain *ugly* when running the macports package. Better download a compiled version from the FileZilla project homepage, to receive something you can look at without too mnuch pain. (No retina support on either package yet...)
Please leave comments on tickets via Trac and not by replying to the macports-tickets mailing list. Relatively few people subscribe to the mailing list, and Trac search will not find comments you make via email. vq
Well, then make it more obvious how to best reply. I only subscribed to the mailing list because the webpage I found about this bug via google asked me to and explicitly stated, I could not reply successfully without subscribing. This was my entry point: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-41832-Can-t-build-FileZil... and I just hit reply and took it from there. This is what I get in bright yellow then: „This message will be sent from lothar.haeger@gmx.net to the macports-tickets@lists.macosforge.org mailing list. You may need to subscribe to this mailing list for your message to be accepted." When I first tried, there was an even more alarming message about making sure to have subscribed and not proceed without. Why don’t you dump the whole mailing list stuff if it’s rarely used and only triggering behaviour you do not want to see? Cheers, Lothar An 6. Januar 2014 at 20:43:17, Lawrence Velázquez-2 [via Mac OS Forge] (ml-node+s2317878n240738h90@n4.nabble.com) schrieb: On Jan 6, 2014, at 11:47 AM, lhaeger <[hidden email]> wrote:
Ran into the same error on OS-X Mavericks and is seemed to be caused by not having XCode command line tools installed. After installing the command line tools, installing FileZilla succeded.
Nevertheless: the FileZilla GUI looks plain *ugly* when running the macports package. Better download a compiled version from the FileZilla project homepage, to receive something you can look at without too mnuch pain. (No retina support on either package yet...)
Please leave comments on tickets via Trac and not by replying to the macports-tickets mailing list. Relatively few people subscribe to the mailing list, and Trac search will not find comments you make via email. vq _______________________________________________ macports-tickets mailing list [hidden email] https://lists.macosforge.org/mailman/listinfo/macports-tickets If you reply to this email, your message will be added to the discussion below: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-41832-Can-t-build-FileZil... To unsubscribe from [MacPorts] #41832: Can't build FileZilla, click here. NAML -- View this message in context: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-41832-Can-t-build-FileZil... Sent from the MacPorts - Tickets mailing list archive at Nabble.com.
On Jan 6, 2014, at 3:21 PM, lhaeger <lothar.haeger@gmx.net> wrote:
Well, then make it more obvious how to best reply.
All emails generated by our bug tracker have the Trac ticket URL near the bottom. Here's more information on it: http://guide.macports.org/chunked/project.html
I only subscribed to the mailing list because the webpage I found about this bug via google asked me to and explicitly stated, I could not reply successfully without subscribing. This was my entry point: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-41832-Can-t-build-FileZil... and I just hit reply and took it from there.
We're not responsible for the Nabble interface.
This is what I get in bright yellow then:
„This message will be sent from [hidden email] to the [hidden email] mailing list. You may need to subscribe to this mailing list for your message to be accepted."
When I first tried, there was an even more alarming message about making sure to have subscribed and not proceed without.
All MacPorts mailing lists require subscription, as an anti-spam measure.
Why don’t you dump the whole mailing list stuff if it’s rarely used and only triggering behaviour you do not want to see?
Some people (like myself) subscribe to it as a way of keeping up with tickets. All tickets, changes to tickets, and comments on tickets are automatically posted to the list. vq
#41832: Can't build FileZilla --------------------------------+----------------------- Reporter: michael_hodgins@… | Owner: rudloff@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: filezilla | --------------------------------+----------------------- Changes (by mojca@…): * status: new => closed * version: 2.2.1 => * resolution: => fixed Comment: I committed a blind fix in r116918. I have no 10.9, but the buildbot seems to be happy with the patch: * https://build.macports.org/builders/buildports-mavericks- x86_64/builds/1546 * https://build.macports.org/builders/buildports-mavericks- x86_64/builds/1547 so I'm closing this issue as fixed. -- Ticket URL: <https://trac.macports.org/ticket/41832#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#41832: Can't build FileZilla --------------------------------+----------------------- Reporter: michael_hodgins@… | Owner: rudloff@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: filezilla | --------------------------------+----------------------- Comment (by mojca@…): The patch has been applied upstream in http://svn.filezilla- project.org/filezilla?view=revision&revision=5399 -- Ticket URL: <https://trac.macports.org/ticket/41832#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (3)
-
Lawrence Velázquez
-
lhaeger
-
MacPorts