Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SWProxy 0.99.1 - Compiled OSX not working #55

Open
stanleykylee opened this issue Mar 26, 2016 · 14 comments
Open

SWProxy 0.99.1 - Compiled OSX not working #55

stanleykylee opened this issue Mar 26, 2016 · 14 comments

Comments

@stanleykylee
Copy link
Contributor

Two issues at hand:

  1. The compiled zip package is missing the plugins folder.
  2. Double clicking the SWProxy file doesn't load the plugin location properly.
@stanleykylee
Copy link
Contributor Author

Created a .command file which will:

  1. Launch a terminal session
  2. Change to the directory in which the script (.command and SWProxy) file is located
  3. Launch SWProxy
RunSWProxy.command
-------------------------------
cd `dirname $0`
`pwd`/SWProxy

Note:
OSX terminal by default will launch the terminal session to the user's home directory. Placing the plugins directory in the user's home directory will also work and not require the .command file.

@Fl3xX
Copy link

Fl3xX commented Mar 27, 2016

Hi,

When i run the command i get this in my terminal, can you give me a hand..?

Error loading Python lib '/var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEI7ueMOb/Python': dlopen(/var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEI7ueMOb/Python, 10): Symbol not found: ___sincos_stret
Referenced from: /var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEI7ueMOb/Python
Expected in: /usr/lib/libSystem.B.dylib
in /var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEI7ueMOb/Python
logout

Thank you

@stanleykylee
Copy link
Contributor Author

Are the files extracted from the zip file before you run the .command file? It looks like you're trying to run it from a temporary folder?

@Fl3xX
Copy link

Fl3xX commented Mar 28, 2016

Yes i Unziped them and they are on my desktop right now. I tried to install the latest version of python but honestly i'm not comfortable on mac at all ... Doesn't have something to do with pythonlib ?

Tell me if you need anything that can help.

@stanleykylee
Copy link
Contributor Author

@Fl3xX I created a new issue for your problem.

@fperegrinvs
Copy link
Collaborator

can we close this ?

@stanleykylee
Copy link
Contributor Author

@lstern, yes I guess? @kakaroto didn't like the solution I provided, so technically the issue is still there.

I could open a new issue that specifically refers to the double-clicking as the binary works fine.

@kakaroto
Copy link
Owner

Let's leave it open for now. I haven't actually tried it on mac or looked at how it runs at all (just what i understood from reading the issue comments), so until I can actually test it and assess what needs to be done (maybe @stanleykylee 's solution is right, I just misunderstood what he did), let's keep it open.

@stanleykylee
Copy link
Contributor Author

@kakaroto no worries. From my understanding, it's more related to how OSX handles a terminal session when launched by double-clicking that is causing the issue (need for .command file). However, from seeing various issues coming up now, I may need to make my .command file more compatible with older versions of OSX.

In the middle of preparing for final paper and exams, so I'll be in and out for the next two weeks.

@aureus1
Copy link

aureus1 commented May 19, 2016

Just pushed a fix for this to my fork (and pull requested).

OSX binary here: https://github.com/aureus1/SWProxy/releases/tag/OSX_Fix

@msteudel
Copy link

@aureus1 - Sorry I'm new to the whole SWProxy thing ... what is your fork do? I went to look on the github page but didn't see any readme ...

@aureus1
Copy link

aureus1 commented May 19, 2016

It's basically just how github works - I can't directly make code changes
to SWParser as I'm not part of the project, but I can fork it (basically
make my own copy), make changes there and request that they get pulled into
the main version.

That's what I did here - I copied the project and fixed this issue. The
"OSX Binary" link in my original post is a zip containing the version of
SWParser that should fix this issue, built for Mac OSX.

On Thu, May 19, 2016 at 12:18 PM, Mark Steudel [email protected]
wrote:

@aureus1 https://github.com/aureus1 - Sorry I'm new to the whole
SWProxy thing ... what is your fork do? I went to look on the github page
but didn't see any readme ...


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#55 (comment)

@Fl3xX
Copy link

Fl3xX commented May 21, 2016

Hi guys and thank you for the update and fix, but i have the exact same issue.. I get this when i try to run the swproxy or the .command.

I'm running on OSX 10.6.8 and i installed Xcode .
I really need some help to translate what the console said me :) Thanks !

Error loading Python lib '/var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEIW9psS2/Python': dlopen(/var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEIW9psS2/Python, 10): Symbol not found: ___sincos_stret
Referenced from: /var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEIW9psS2/Python
Expected in: /usr/lib/libSystem.B.dylib
in /var/folders/g6/g6xWIqVUGuO6CmDUxKu2Rk+++TI/-Tmp-/_MEIW9psS2/Python
logout

@aureus1
Copy link

aureus1 commented May 22, 2016

@Fl3xX You're going to need OSX 10.9 or later; the compiled version is not compatible with earlier versions.

@ghost ghost mentioned this issue Jul 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants