Thanks Benjamin! So a mesos ebuild in the coreos overlay might be ok? but getting it as a stock dependency of coreos-base/coreos sounds like it will be near impossible :-P
To stop the long jump error we enabled c-ares (adns) for curl : https://github.com/coreos/coreos-overlay/compare/f0b0f9a34711dbfeffd6bf45a78add209e3607ae...drcrallen:dc295ffb776d8dae3603cc87400cc0c9dede883e On Wed, Jun 14, 2017 at 11:13 AM Benjamin Gilbert < [email protected]> wrote: > On Wed, Jun 14, 2017 at 7:39 AM, Charles Allen < > [email protected]> wrote: > >> Regarding mesos by default, I couldn't quite unravel the coreos build >> process enough to have a great way to install a custom ebuild. If I did >> emerge-amd64-usr it seemed to un-emerge whenever I ran the final build >> image command. Though admittedly I may have fat fingered a command >> somewhere since I was doing it manually at the time. If I want to have a >> custom ebuild added to the image, is that the intended way to do it? >> > > emerge-amd64-usr only builds the binpkg; it doesn't add it to the image. > To do that, add the package as a dependency of coreos-base/coreos in the > coreos-overlay repo. > > By the by, we've enabled threaded asynchronous DNS > <https://github.com/coreos/coreos-overlay/commit/7adb80d4fc272e6dab20594c5ed23d150e02249e> > in curl, which should fix the longjmp crash you were seeing. > > --Benjamin Gilbert > >
