[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] Building Tutorial Noop on OpenBSD
Thanks for getting back about this. opam2 is still in beta so isn't part of the tree yet, but I'll make a port available next week. It builds from the master branch on OpenBSD out of the box, with a built-in solver, so you may want to try it now. Success/failure reports on opam2 are very useful right now :) best Anil On 25 Oct 2017, at 03:54, Adam Steen <adam@xxxxxxxxxxxxxxxx> wrote: > > Hi Anil > > Just to report back, we are not going to be able to have aspcud on > OpenBSD just yet, it requires gringo (>= v4.2.1) > (https://github.com/potassco/clingo/), but his fails with a "undefined > reference to `__cxa_thread_atexit'" and OpenBSD does not implement > this symbol as yet. > > Is opam2 built as part of the standard ocaml/opam build? > > Cheers > Adam > > On Thu, Oct 12, 2017 at 7:09 PM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote: >> Adam, >> >> It would be worth trying to see if you can get aspcud working, since things >> have been >> updated somewhat with clang on OpenBSD. I'm going to be taking a look at the >> opam2 beta this week to see how usable it is with Mirage, so I'll post an >> update >> here when I do that. Opam2 already has mccs builtin so it's not worth a >> separate >> port, but aspcud will still be useful with both opam1 and 2, and hence is >> worth >> a port. >> >> Anil >> >>> On 12 Oct 2017, at 01:20, Adam Steen <adam@xxxxxxxxxxxxxxxx> wrote: >>> >>> Hi Anil and Hannes >>> >>> Thank you for the reply. >>> >>> I can confirm i don't have aspcud and OpenBSD does not have a aspcud port. >>> >>> i ended up setting OPAMUSEINTERNALSOLVER=1 and this seem to get noop >>> compiling and running (well i got an exist code of 0). >>> >>> What would be the best way forward? Should i look into creating a >>> aspcud port or is mccs the better way to go? >>> >>> Cheers >>> Adam >>> >>> >>> On Wed, Oct 11, 2017 at 9:22 PM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote: >>>> I suspect the problem is that OpenBSD doesn't have an aspcud port, and so >>>> the online solver is failing. I'm just about ready to give up on that >>>> online >>>> solver staying up, and so the solution is probably to make an opam2-beta5 >>>> port for OpenBSD and go with that instead. That includes a statically >>>> linked solver (mccs) that just works without any more dependencies. >>>> >>>> Adam, could you confirm that you don't have aspcud installed? I don't >>>> remember >>>> porting it to OpenBSD but someone else may have since. >>>> >>>> thanks >>>> Anil >>>> >>>>> On 11 Oct 2017, at 14:06, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote: >>>>> >>>>> first question is do you have math/aspcud installed? >>>>> >>>>> another workaround I commonly use is to disable depext (which is >>>>> supposed to interact with your operating system packaging system) in the >>>>> Makefile, and install external dependencies manually if the build fails. >>>>> >>>>> >>>>> hannes >>>>> >>>>> On 11/10/2017 04:02, Adam Steen wrote: >>>>>> opam depext --yes --update mirage-unikernel-noop-unix >>>>>> OPAM plugin depext is not installed. Install it on the current switch? >>>>>> [Y/n] y >>>>>> [WARNING] External solver failed with inconsistent return value. Request >>>>>> saved >>>>>> to "/home/asteen/.opam/log/solver-error-73931-1.cudf" >>>>>> [ERROR] External solver failure, please fix your installation and check >>>>>> /home/asteen/.opam/config and variable $OPAMEXTERNALSOLVER. >>>>>> You may also retry with option --use-internal-solver >>>>> >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx >>>>> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>> >>>> >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx >>>> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx >>> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |