On 6-3-2018 18:07, Ricardo Dias wrote:
>
>
> On 06-03-2018 16:59, Willem Jan Withagen wrote:
>> On 6-3-2018 17:12, Ricardo Dias wrote:
>>> Hi Willem,
>>>
>>> This only means that you cannot currently build the dashboard_v2
>>> frontend in freebsd.
>>>
>>> I'm not familiar with freebsd, but we can investigate if it's possible
>>> to make it work.
>>
>> Yup, that much I found out. :)
>> Disabling with `-D WITH_MGR_DASHBOARD_V2_FRONTEND=OFF` will restore
>> successful building and testing.
>> Probably not all modules (fsevents??) are compatible with FreeBSD, given
>> the more detailed error output.
>>
>> So probably it'll need a version that matches:
>> 26225 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform
>> for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current:
>> {"os":"freebsd",
>> "arch":"x64"})
>>
>>
>> But then still building this way of creating the DASHBOARD_V2 module
>> into the FreeBSD package is going to be even more of a problem, since it
>> is not expected (allowed) that neither during the building of the
>> package the make file fetches extra online "code", nor during
>> installation of the package is it expected to fetch more code.
>
> If you are running the build from the tarball, we already include the
> frontend build files in the tarball to avoid the need to access the
> internet during the creation of packages.
I'm building the package from the github-repo...
Which is also nicer in the packaged freeBSD environment.
If only to prevent downloading this huge tarball over and over.
> But to generate the tarball you need an environment that is capable of
> building the frontend.
catch-22...
So for the time being it'll be switched off, also because I expect
fsevents to contain eventing trickery more compatible to Linux. And
getting that working on a BSD is not always trivial.
And that needs to be fixed first, before we even get to the distribution
challenge.
--WjW
>>
>> If so, then that code needs to be installed as another (set of) packages.
>>
>> Perhaps a trick around it would be to fetch the data before the actual
>> building starts, but I know that that method is frowned upon.
>>
>>
>> --WjW
>>
>>
>>>
>>> Thanks,
>>> Ricardo
>>>
>>> On 06-03-2018 15:48, Willem Jan Withagen wrote:
>>>>
>>>> This is not going to work on FreeBSD atm...
>>>> So I guess no dashboard_v2 for the time being.
>>>>
>>>> --WjW
>>>>
>>>>
>>>> cd
>>>> /home/jenkins/workspace/ceph-master/src/pybind/mgr/dashboard_v2/frontend
>>>>
>>>> && npm install
>>>>
>>>> npm ERR! code E404
>>>> npm ERR! 404 Not Found: node-freebsd-x64@8.9.4
>>>>
>>>> npm ERR! A complete log of this run can be found in:
>>>> npm ERR!
>>>> /home/jenkins/.npm/_logs/2018-03-06T15_43_35_298Z-debug.log
>>>> module.js:559
>>>> throw err;
>>>> ^
>>>>
>>>> Error: Cannot find module 'node-freebsd-x64/package.json'
>>>> at Function.Module._resolveFilename (module.js:557:15)
>>>> at Function.resolve (internal/module.js:18:19)
>>>> at ChildProcess.<anonymous>
>>>> (/home/jenkins/workspace/ceph-master/src/pybind/mgr/dashboard_v2/frontend/node_modules/node-bin-setup/index.js:18:27)
>>>>
>>>>
>>>> at ChildProcess.emit (events.js:127:13)
>>>> at maybeClose (internal/child_process.js:936:16)
>>>> at Process.ChildProcess._handle.onexit
>>>> (internal/child_process.js:220:5)
>>>> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3
>>>> (node_modules/fsevents):
>>>> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
>>>> fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current:
>>>> {"os":"freebsd","arch":"x64"})
>>>>
>>>> npm ERR! code ELIFECYCLE
>>>> npm ERR! errno 1
>>>> npm ERR! node@8.9.4 preinstall: `node installArchSpecificPackage`
>>>> npm ERR! Exit status 1
>>>> npm ERR!
>>>> npm ERR! Failed at the node@8.9.4 preinstall script.
>>>> npm ERR! This is probably not a problem with npm. There is likely
>>>> additional logging output above.
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> ceph-devel" in
>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
