Request for porting "SoftEther VPN"

[Big Lebowski]

Interestingly, I used their makefiles to just do the build and then created
proper do-install separately. When it comes to compilation, I didnt had any
issues using CLANG, beside some noisy warnings, but it compiles and runs
fine. What I did changed tho, was pthreads and iconv. Perhaps we should
join the forces?


On Fri, Jan 17, 2014 at 11:57 AM, Tommy Scheunemann <net at arrishq.net> wrote:

> Hello,
>
> seems we both "went" into the same problem. What I did:
>
> patching both makefiles (freebsd_32bit and freebsd_64bit) to add ${PREFIX}
> and use this instead of the hardcoded /usr/bin one.
> Though that doesn't seem to be required because the final "cp" process can
> be triggered manually without calling "make install" at all.
>
> Then adding "-I${PREFIX}/include -I/usr/include" and "-L${PREFIX}/lib
> -L/usr/lib" - under 9.1 and 9.2 the compile run fails (when using gcc)
> without this and complains about missing header files / libraries.
> Additionally adding a dependency for openssl from the ports because the
> final linking complains about a too old openssl version.
>
> So for the datafiles - maybe doing it like:
>
> ${PREFIX}/lib/softether
>
> placing all binary files and the datafiles there. Then creating small
> scripts in
>
> ${PREFIX}/bin
>
> that act as wrapper.
>
> Finally - a small "rc" script to enable starting / stopping the entire
> thing.
>
> Kind regards
>
>
> On Fri, 17 Jan 2014, Big Lebowski wrote:
>
>  Hi,
>> I've almost the port ready, but I am just struggling with decision wether
>> I want to write patches for it, or not. The software is quite badly
>> written, and it expects a
>> certain data file to exist... in the same directory as the binaries.
>> Normally, I'd install binaries to /usr/local/bin, but in this case that'd
>> require the file living
>> in there, what's a mess I dont want to create. The solution is to either
>> install it in /usr/local/softether or to patch it so that the data file
>> could go to lib - I am
>> undecided yet, as the first solution is so linux'y and second requires
>> rewriting piece of their code.
>>
>>
>>
>>
>> On Fri, Jan 17, 2014 at 9:43 AM, Tommy Scheunemann <net at arrishq.net>
>> wrote:
>>       Hello @list,
>>
>>       I'm about to work on getting it ported, just in case so nothing
>> gets done twice.
>>
>>       On Mon, 13 Jan 2014, Гуляев Гоша wrote:
>>
>>             Hi friends!
>>             It is a very interesting VPN solution, and some days ago it
>> going opensource!
>>             So maybe someone will port it to FreeBSD?
>>             Official site: http://www.softether.org/
>>             Instructions for build on UNIX-like systems:
>> http://www.softether.org/5-download/src/2.unix
>>             _______________________________________________
>>             freebsd-ports at freebsd.org mailing list
>>             http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>             To unsubscribe, send any mail to "freebsd-ports-unsubscribe@
>> freebsd.org"
>>
>>       _______________________________________________
>>       freebsd-ports at freebsd.org mailing list
>>       http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>       To unsubscribe, send any mail to "freebsd-ports-unsubscribe@
>> freebsd.org"
>>
>>
>>
>>
>>