Page 5 of 5 FirstFirst ... 345
Results 101 to 106 of 106

Thread: ProSocks

  1. #101
    Join Date
    Feb 2011
    Location
    The Future.
    Posts
    5,600
    Mentioned
    396 Post(s)
    Quoted
    1598 Post(s)

    Default

    Quote Originally Posted by riwu View Post
    ...
    Looks like the newest version of OpenSSL officially supports 64-bit but has problems with its make-file (make-file also changed and so did the configuration).. Anyway, to get around it, use the following to build the libraries:


    bash Code:
    #For Building Zlib:

    export "INCLUDE_PATH=/usr/local/include"
    export "LIBRARY_PATH=/usr/local/lib"
    export "BINARY_PATH=/usr/local/bin"
    export "CFLAGS=-m32"
    export "CXXFLAGS=-m32"
    export "LDFLAGS=-m32"
    make -f win32/Makefile.gcc install



    #For Building OpenSSL (if you are missing any dependencies, run "make depend" before "make install"):

    ./configure no-shared threads --prefix=/usr/local mingw
    make install



    #For Building OpenSSL (with specific CPU/Architecture):

    ./configure no-shared threads --prefix=/usr/local -m32 -march=i686 mingw
    make install



    #For Building OpenSSL (without Assembly):

    ./configure no-shared threads --prefix=/usr/local no-asm mingw
    make install


    #For Listing OpenSSL CPU/OS/Architecture configurations:

    ./configure no-shared thread --prefix=/usr/local -m32



    #For Building CurlLib:

    ./configure —-enable-static —-enable-shared —-enable-ipv6 —-with-ssl=/usr/local --build=i686-pc-windows "CFLAGS=-m32" "CXXFLAGS=-m32" "LDFLAGS=-m32"
    make install


    OpenSSL is installed in your prefix directory. You can specify --prefix=/c/OpenSSL or --prefix=/c/OpenSSL64 but in the above I just leave it as /usr/local.

    If you decide to change the prefix then when building Curl, you have to specify --with-ssl=WhateverPrefixYouSpecified
    Last edited by Brandon; 12-18-2015 at 04:30 AM.
    I am Ggzz..
    Hackintosher

  2. #102
    Join Date
    Feb 2013
    Posts
    65
    Mentioned
    0 Post(s)
    Quoted
    25 Post(s)

    Default

    Doesn't seem like I can get the library to load correctly. I mean, it obviously loads because I don't get an error when I try to load it, but when I try to use any of the functions I get a "Unknown Declaration" error.

    Simba Code:
    Error: Unknown declaration "Pro_InitSocket"

  3. #103
    Join Date
    Jun 2012
    Posts
    586
    Mentioned
    112 Post(s)
    Quoted
    296 Post(s)

    Default

    ProSocks is no longer structured like that.




    Skype: obscuritySRL@outlook.com

  4. #104
    Join Date
    Feb 2013
    Posts
    65
    Mentioned
    0 Post(s)
    Quoted
    25 Post(s)

    Default

    Quote Originally Posted by Obscurity View Post
    ProSocks is no longer structured like that.
    Oh, now I see. Does that mean there's no longer any way to connect to a socket server with the library? Since the address constant in SSLSocket and the connect, read and write functions are not there in the lape part.

    Should I use the built in socket library instead?

  5. #105
    Join Date
    Jan 2012
    Posts
    468
    Mentioned
    3 Post(s)
    Quoted
    200 Post(s)

    Default

    After Updating Prosocks I keep running into this error!!

    Error: Unknown declaration "Pro_InitSocket" at line 624
    Compiling failed.


    Can anyone help?

  6. #106
    Join Date
    May 2016
    Posts
    2
    Mentioned
    0 Post(s)
    Quoted
    0 Post(s)

    Default

    Error: Unknown declaration "SSLSocket" at line 83
    Compiling failed.

    i downloaded prosocks and put it in plugins.
    still gives this error can some1 pls help?

Page 5 of 5 FirstFirst ... 345

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •