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

Fix build of ZNC with LibreSSL #594

Closed
brad0 opened this issue Jul 16, 2014 · 6 comments · Fixed by jimloco/Csocket#49
Closed

Fix build of ZNC with LibreSSL #594

brad0 opened this issue Jul 16, 2014 · 6 comments · Fixed by jimloco/Csocket#49

Comments

@brad0
Copy link

brad0 commented Jul 16, 2014

Here is a patch from the OpenBSD ports tree to fix the build of ZNC against LibreSSL.

http://openbsd.comstyle.com/cgi/cvsweb/ports/net/znc/patches/patch-src_Csocket_cpp?rev=1.1&content-type=text/x-cvsweb-markup

@DarthGandalf
Copy link
Member

Changes to Csocket need to go at https://github.com/jimloco/Csocket

@jimloco

@Sp1l
Copy link

Sp1l commented Mar 7, 2015

Created jimloco/Csocket#49 to fix build with LibreSSL.

Saw that the tarball does not include Csocket.cpp, imagine that this is included with some build script?

@DarthGandalf
Copy link
Member

Both release tarballs and nightly tarballs include it...

@Mikaela
Copy link
Contributor

Mikaela commented Mar 7, 2015

Saw that the tarball does not include Csocket.cpp, imagine that this is included with some build script?

GitHub tarballs don't include submodules and thus are broken and they shouldn't be used.

@Sp1l
Copy link

Sp1l commented Mar 7, 2015

Sorry, meant to say the GitHub repo does not include Csocket.cpp yet the tarball does

@Mikaela
Copy link
Contributor

Mikaela commented Mar 7, 2015

It's submodule which you should be able to find at https://github.com/znc/znc/tree/master/third_party but all changes to it belong to where you already went.

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

Successfully merging a pull request may close this issue.

4 participants