Build started at 2021-11-02T12:06:01.968378
meson.build:1:0: ERROR: Unable to detect linker for compiler “link /logo --version”
gcc -v
gcc version 6.3.0 (MinGW.org GCC-6.3.0-1)
make -v
GNU Make 3.81
nazar-pc
November 2, 2021, 4:43am
2
It doesn’t seem like you have followed all of the instructions top to bottom.
Also please search forum for similar questions, you will find a few topic right on the front page.
this is the MinGW packages
i read the doc for windows , and exec like this.
the complete log is next:
PS E:\mediasoup-demo\server\node_modules\mediasoup> npm install@typescript-eslint /experimental-utils@5.3.0’,@typescript-eslint /scope-manager@5.3.0’,@typescript-eslint /types@5.3.0’,@typescript-eslint /typescript-estree@5.3.0’,@typescript-eslint /visitor-keys@5.3.0’,
mediasoup@3.9.0 postinstall
npm-scripts.js [INFO] running task “postinstall”
meson.build:1:0: ERROR: Unable to detect linker for compiler “link /logo --version”
A full log can be found at e:\mediasoup-demo\server\node_modules\mediasoup\worker\out\Release\meson-logs\meson-log.txt
npm ERR! A complete log of this run can be found in:
nazar-pc
November 2, 2021, 5:03am
4
Did you install and configure MSVS? What version of Make do you have (please attach make -v output as it is printed)?
yes,i install the msvs 2017 and setted.
path contained:
C:\MinGW\msys\1.0\bin
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.14.26428\bin\Hostx64\x64
and the make -v installed by MinGW is next:
nazar-pc
November 2, 2021, 5:15am
6
It might be caused by extra packages installed. Make sure there is no link.exe in C:\MinGW\msys\1.0\bin or else it might be selected over MSVC’s linker and fail like that.
1 Like
Yes ,you are right!
while i delete it ,and exec npm install ,and i had a new error ……
Build started at 2021-11-02T13:27:22.910235
Sanity check compile stderr:
meson.build:1:0: ERROR: Compiler cl can not compile programs.
nazar-pc
November 2, 2021, 5:36am
8
Yep, now it seems like MSVS environment wasn’t configured, this is likely also a reason why you had linker errors in the first place. Adding paths that are not mentioned in the installation guide is not a replacement for those instructions.
so sorry,
i tried again followed all of the instructions top to bottom.
1. node -v ----------v12.20.0 2.python -v ----------python 3.6.8 with PIP 3.MinGW (GNU make)
4.installed MSVS,and setted path like instructions
5.while i exec ‘npm install’ ,then error is this:
Build started at 2021-11-02T16:52:35.926418
meson.build:1:0: ERROR: Unknown compiler(s): [[‘cl’]]6. i added a var to path like this:
now ,i try exec ‘npm install’ ,i had the error :
> Build started at 2021-11-02T16:55:53.394534
> Main binary: c:\Users\Administrator\AppData\Local\Programs\Python\Python36\python.exe
> Build Options: -Db_ndebug=true -Db_pie=true -Db_staticpic=true -Dbuildtype=release
> Python system: Windows
> The Meson build system
> Version: 0.60.0
> Source dir: e:\mediasoup-demo\server\node_modules\mediasoup\worker
> Build dir: e:\mediasoup-demo\server\node_modules\mediasoup\worker\out\Release
> Build type: native build
> Project name: mediasoup-worker
> Project version: undefined
> Sanity testing C compiler: cl
> Is cross compiler: False.
> Sanity check compiler command line: cl sanitycheckc.c /Fesanitycheckc.exe /MD /nologo /showIncludes /utf-8 /link
> Sanity check compile stdout:
> sanitycheckc.c
> LINK : fatal error LNK1104: �����ļ���MSVCRT.lib��
>
> -----
> Sanity check compile stderr:
>
> -----
>
> meson.build:1:0: ERROR: Compiler cl can not compile programs.
so,What do I need to do?
lilala
February 18, 2022, 7:25am
10
I have encountered the same problem as you. Have you solved it now? Can you share the solution? thank you
nazar-pc
February 18, 2022, 12:18pm
11
The solution is to follow installation instructions and not adding to PATH something that isn’t described in installation guide. There were a few fixes for some of the setups as well since this thread was created.
snnz
February 18, 2022, 1:04pm
12
Until the install succeeds without any interactions (it should eventually), try setting VC environment manually: form the Start menu, launch Visual Studio {version} folder → … → x64 Native Tools Command Prompt for VS {version}, then run the install in this command prompt.
snnz
February 18, 2022, 1:17pm
13
I doubt that removing the last additions to the PATH will solve the problem, because there is another occurance of the substring “Visual Studio”, that was probably added for some other purpose (and even for another version of VS). And the check for this substring is still present in the release branch of the Meson sources.
nazar-pc
February 18, 2022, 1:25pm
14
Hm, I thought they included it in 0.61.2, unfortunately they didn’t, but it should be a part of the next release.
snnz
February 18, 2022, 1:53pm
15
It may or it may not. They have the separate branches for every version, from which the maintainance releases are done, and which are quite different from the master branch, i.e. they do not merge the master into the other ones. So either they’ll start a new version, or similar change should be somehow committed to the active release branch (0.61).
