SOLVED [gelöst] Windows10, Neuinstallation iobroker, fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h", unix_dgram

[greyhound]

Mich nervt auf meinem Dev-System schon länger der ein build-Fehler bezüglich unix_dgram und habe daher node und ioBroker frisch auf einem "unbelasteten" System installiert (kein node, iobroker, ...)

C:\iobroker>node -v
v8.16.0
C:\iobroker>npm -v
6.4.1

BuildTools installiert
python-2.7.15
windows-build-tools@5.1.0

und dann ioBroker ...

Microsoft Windows [Version 10.0.17763.529]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

C:\WINDOWS\system32> npm install --global windows-build-tools

> windows-build-tools@5.1.0 postinstall C:\Users\Frank\AppData\Roaming\npm\node_modules\windows-build-tools
> node ./dist/index.js

Downloading python-2.7.15.amd64.msi
[>                                            ] 0.0% (0 B/s)
Downloaded python-2.7.15.amd64.msi. Saved to C:\Users\Frank\.windows-build-tools\python-2.7.15.amd64.msi.
Downloading vs_BuildTools.exe
[>                                            ] 0.0% (0 B/s)
Downloaded vs_BuildTools.exe. Saved to C:\Users\Frank\.windows-build-tools\vs_BuildTools.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
Successfully installed Visual Studio Build Tools.
------------------- Python --------------------
Action start 18:13:35: MsiPublishAssemblies.
Action ended 18:13:35: MsiPublishAssemblies. Return value 1.
Action start 18:13:35: PublishFeatures.
Action ended 18:13:35: PublishFeatures. Return value 1.
Action start 18:13:35: PublishProduct.

Now configuring the Visual Studio Build Tools and Python...

All done!

+ windows-build-tools@5.1.0
updated 1 package in 14.432s

C:\WINDOWS\system32>
C:\WINDOWS\system32>
C:\WINDOWS\system32>cd \iobroker

C:\iobroker>npm install iobroker

> iobroker@2.0.3 install C:\iobroker\node_modules\iobroker
> node lib/checkVersions.js

NPM version: 6.4.1

> iobroker@2.0.3 postinstall C:\iobroker\node_modules\iobroker
> node lib/install.js


╭───────────────────────────────────────────────────────╮
│ The iobroker files have been downloaded successfully. │
│ To complete the installation, you need to run         │
│                                                       │
│           npm i --production --unsafe-perm            │
│                                                       │
╰───────────────────────────────────────────────────────╯

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\iobroker\package.json'
npm WARN iobroker No description
npm WARN iobroker No repository field.
npm WARN iobroker No README data
npm WARN iobroker No license field.

+ iobroker@2.0.3
added 51 packages from 32 contributors and audited 83 packages in 4.579s
found 0 vulnerabilities


C:\iobroker>npm i --production --unsafe-perm
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.

> iobroker.js-controller@1.4.2 preinstall C:\iobroker\node_modules\iobroker.js-controller
> node lib/preinstall_check.js

NPM version: 6.4.1
npm version >= 5: disabling package-lock

> unix-dgram@0.2.3 install C:\iobroker\node_modules\unix-dgram
> node-gyp rebuild


C:\iobroker\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
  unix_dgram.cc
  win_delay_load_hook.cc
c:\iobroker\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": No such file or directory [C:\iobroker\node_modules\unix-dgram\build\un
ix_dgram.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\iobroker\node_modules\unix-dgram
gyp ERR! node -v v8.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

> serialport@6.2.2 install C:\iobroker\node_modules\serialport
> prebuild-install || node-gyp rebuild


> iobroker.js-controller@1.4.2 install C:\iobroker\node_modules\iobroker.js-controller
> node iobroker.js setup first

creating conf/iobroker.json
object system.certificates created
object system.repositories created
object system.config created
object enum.functions created
object enum.rooms created
object system.group.user created
object system.group.administrator created
object _design/system created
object system.meta.uuid created: 60f73a44-b6af-8137-6eec-9038d9d2afe9
object system.user.admin created
host.NB04 install adapter admin
npm install --production (System call) in "C:/iobroker/node_modules/iobroker.admin"
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm notice created a lockfile as package-lock.json. You should commit this file.
got C:/iobroker/node_modules/iobroker.admin/admin
upload [3] admin.admin C:/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript
upload [2] admin.admin C:/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html
upload [1] admin.admin C:/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html
upload [0] admin.admin C:/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png
host.NB04 object system.adapter.admin created
host.NB04 create instance admin
host.NB04 object admin.0 created
host.NB04 object admin.0.info created
host.NB04 object system.adapter.admin.upload created
host.NB04 object system.adapter.admin.0.outputCount created
host.NB04 object system.adapter.admin.0.inputCount created
host.NB04 object system.adapter.admin.0.uptime created
host.NB04 object system.adapter.admin.0.memRss created
host.NB04 object system.adapter.admin.0.memHeapTotal created
host.NB04 object system.adapter.admin.0.memHeapUsed created
host.NB04 object system.adapter.admin.0.connected created
host.NB04 object system.adapter.admin.0.alive created
host.NB04 object system.adapter.admin.0 created
host.NB04 install adapter discovery
npm install --production (System call) in "C:/iobroker/node_modules/iobroker.discovery"
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm notice created a lockfile as package-lock.json. You should commit this file.
got C:/iobroker/node_modules/iobroker.discovery/admin
upload [5] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript
upload [4] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html
upload [3] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html
upload [2] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html
upload [1] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html
upload [0] discovery.admin C:/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png
host.NB04 object system.adapter.discovery created
host.NB04 create instance discovery
host.NB04 object discovery.0.scanRunning created
host.NB04 object discovery.0.devicesFound created
host.NB04 object discovery.0.instancesFound created
host.NB04 object discovery.0.servicesProgress created
host.NB04 object discovery.0.devicesProgress created
host.NB04 object system.adapter.discovery.0.outputCount created
host.NB04 object system.adapter.discovery.0.inputCount created
host.NB04 object system.adapter.discovery.0.uptime created
host.NB04 object system.adapter.discovery.0.memRss created
host.NB04 object system.adapter.discovery.0.memHeapTotal created
host.NB04 object system.adapter.discovery.0.memHeapUsed created
host.NB04 object system.adapter.discovery.0.connected created
host.NB04 object system.adapter.discovery.0.alive created
host.NB04 object system.adapter.discovery.0 created

> iobroker.inst@2.0.3 install C:\iobroker
> node lib/checkVersions.js

NPM version: 6.4.1

> iobroker.inst@2.0.3 postinstall C:\iobroker
> node lib/install.js

Write "iobroker start" to start the ioBroker
npm install node-windows@0.1.14 --production --save --prefix "C:/iobroker"
C:\iobroker\semver -> C:\iobroker\node_modules\semver\bin\semver

> iobroker@2.0.3 install C:\iobroker\node_modules\iobroker
> node lib/checkVersions.js

NPM version: 6.4.1

> iobroker@2.0.3 postinstall C:\iobroker\node_modules\iobroker
> node lib/install.js


╭───────────────────────────────────────────────────────╮
│ The iobroker files have been downloaded successfully. │
│ To complete the installation, you need to run         │
│                                                       │
│           npm i --production --unsafe-perm            │
│                                                       │
╰───────────────────────────────────────────────────────╯

+ node-windows@0.1.14
added 56 packages from 39 contributors in 3.344s
ioBroker started!
Visit http://127.0.0.1:8080 to configure it.
ioBroker service installed. Write "serviceIoBroker start" to start the service and go to http://localhost:8081 to open the admin UI.
To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules\osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

added 523 packages from 330 contributors and audited 1835 packages in 67.434s
found 23 vulnerabilities (17 low, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for details

C:\iobroker>

ioBroker selbst startet nach der Installation, auch ein Update vom Discovery-Adapter geht ohne Probleme.

Kann mir bitte jemand erklären, warum der Bau von unix-dgram fehl schlägt und wie ich das lösen kann.

[AlCalzone]

@greyhound sagte in Windows10, Neuinstallation iobroker, fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h", unix_dgram:

unix-dgram

Indem du auf Unix wechselst

Nein, Spaß beiseite... Das ist ein Paket für Unix, deswegen steht im Log auch SKIPPING OPTIONAL DEPENDENCY. Es wird für Windows nicht benötigt, d.h. du kannst die Warnung ignorieren.

[sigi234]

@greyhound

Kennst du das ?

Link Text

[greyhound]

Danke nein, kannte ich nicht, habe mein Windows-ioBroker schon vor längerem aufgesetzt und bin dann beim Adapter-Programmieren über diesen build-Fehler gestolpert.

Ist die Installationsvariante auch zum Debuggen mit VSC geeignet?

[sigi234]

@greyhound sagte in Windows10, Neuinstallation iobroker, fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h", unix_dgram:

Ist die Installationsvariante auch zum Debuggen mit VSC geeignet?

Da musst du @Stabilostick fragen......

[AlCalzone]

@greyhound sagte in Windows10, Neuinstallation iobroker, fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h", unix_dgram:

unix-dgram

Indem du auf Unix wechselst

Nein, Spaß beiseite... Das ist ein Paket für Unix, deswegen steht im Log auch SKIPPING OPTIONAL DEPENDENCY. Es wird für Windows nicht benötigt, d.h. du kannst die Warnung ignorieren.

[greyhound]

@AlCalzone Danke, das hatte ich mir eigentlich auch so gedacht, hatte aber angenommen, dass bei den vielen OS- und Arch-Prüfungen solche Sachen dann übergangen werden. Hintergrund ist eigentlich die Frage in https://forum.iobroker.net/post/263787 und da wollte ich eine fehlerfreie Installation haben, wo dann auch VSC nicht dauernd über Exceptions stolpert.

Hoffe, ich komme die Tage zum Testen des neuen Installers und zum Testen mit VSC.