i am trying to build the meshery server from scratch locally on git bash running make commands. but when I run make server I get (after make ui-setup and so on as specified in the docs)
cgo-builtin-prolog:1:10: fatal error: stddef.h: No such file or directory
compilation terminated.
any idea on this? seems like it could be about mismatched versions
Hey @Devesh can you please share the complete logs ?
For the command make server and make ui-setup and make build logs are below.
$ make ui-setup
cd ui; npm i; cd ..
npm warn deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm warn deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated @material-ui/styles@4.11.5: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn deprecated @material-ui/pickers@3.3.10: Material UI Pickers v3 doesn't receive active development since January 2020. See the guide https://mui.com/material-ui/guides/pickers-migration/ to upgrade.
npm warn deprecated @material-ui/lab@4.0.0-alpha.61: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn deprecated @material-ui/core@4.12.4: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error A complete log of this run can be found in: C:\Users\dsawa\npm-cache\_logs\2024-08-05T20_45_59_207Z-debug-0.log
cd provider-ui; npm i; cd ..
npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error A complete log of this run can be found in: C:\Users\dsawa\npm-cache\_logs\2024-08-05T20_46_53_649Z-debug-0.log
make ui-build
cd ui; npm i; cd ..
> meshery-ui@1.0.0 postinstall
> patch-package
cd provider-ui; npm i; cd ..
changed 8 packages, and audited 886 packages in 3s
192 packages are looking for funding
run `npm fund` for details
1 high severity vulnerability
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
cd ui; npm run lint:fix && npm run build && npm run export; cd ..
> meshery-ui@1.0.0 lint:fix
> next lint --fix
cd provider-ui; npm run lint:fix && npm run build && npm run export; cd ..
> provider-ui@1.0.0 lint:fix
> next lint --fix
BUILD="v0.7.87" \
PROVIDER_BASE_URLS="https://meshery.layer5.io" \
PORT=9081 \
DEBUG=true \
ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012 localhost:10013" \
APP_PATH="./apps.json" \
KEYS_PATH="../../server/permissions/keys.csv" \
go run main.go error.go
# runtime/cgo
cgo-builtin-prolog:1:10: fatal error: stddef.h: No such file or directory
compilation terminated.
If this is not what you are asking. Could you specify the location of the logs please? is it stored in some specific location.
@Devesh, could you please flush your node_modules and then execute the following commands in your local repository?
npm imake ui-setupmake ui-buildI tried these steps again but it seems I get the same issue.
I am able to run the server on wsl2 at the moment. would continue from there. thanks!
Sure, @Devesh. If you get stuck, here is a resource that might help:Setting up Meshery Development Environment on Windows | Meshery
