[PATCH] Fix build on DragonFly BSD

Jov amutu at amutu.com
Mon Jul 17 04:59:29 PDT 2017


Hi Nikos,
  I have setup a FreeBSD CI runner successfully but the ocserv master
build failed,see:
https://gitlab.com/amutu/ocserv/-/jobs/22831558

FreeBSD port of ocserv has several patches, should they must upstream
first?  patches are here :
https://github.com/freebsd/freebsd-ports/tree/8bddb8fb8a8d5049a9339582b014874c998c47b7/net/ocserv/files

Regards,
Jov


2017-07-09 23:00 GMT+08:00 Nikos Mavrogiannopoulos
<n.mavrogiannopoulos at gmail.com>:
> On Sat, Jul 8, 2017 at 5:24 PM, Jov <amutu at amutu.com> wrote:
>> For freebsd, maybe I can setup a CI as I have several freebsd vps boxes. Is
>> there some doc about this?
>>
>
> Hi Jov and Aaron,
>  Thanks, that would be great. You would need a freebsd VM which has
> gitlab-ci runner installed and setup, plus all the development
> dependencies to build ocserv (see README.md) + bash. To setup
> gitlab-ci-runner see:
> https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/install/freebsd.md
>
> That would be for the setup. Now to make the ocserv repo to use it, we
> need to make sure it works so:
> 1. Fork ocserv on gitlab and go to your ocserv settings -> CI/CD
> pipelines and using the information there to register the runner. Use
> the tag "freebsd" for the runner.
> 2. On your forked report change .gitlab-ci.yml to contain only the
> commented out freebsd lines (at the end). Commit and push.
>
> You can see whether the build was successful by going to your
> project's pipelines page.
>
> If that works let me know and I'll send you the info to register the
> runner for the ocserv project.
>
> regards,
> Nikos



More information about the openconnect-devel mailing list