#3203 closed defect (invalid)
Windows MSVC configure failed.
Reported by: | persanker | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | build system |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
How to reproduce:
open visual studio 2010 command prompt run msys.bat to open msys command prompt run ./configure --toolchain=msvc
Result:
cl is unable to create an executable file. If cl is a cross-compiler, use the --enable-cross-compile option. Only do this if you know what cross compiling means. C compiler test failed.
Lines in config.log:
link -o ./ffconf.ldwHcjto.exe ./ffconf.TGmoNFot.o link: invalid option -- o Try `link --help' for more information. C compiler test failed.
Change History (2)
comment:1 by , 11 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 11 years ago
Fixed, thanks. I think the config tool made the link parameters by the link.exe edition. It found /bin/link.exe so make a -o option, but the toolchain used MSVC's link.exe to execute.
I renamed /bin/link.exe to link1.exe, the error disappeared.
Note:
See TracTickets
for help on using tickets.
You did not read the documentation (http://ffmpeg.org/platform.html#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows)
Specifically:
It is possible that coreutils' link.exe conflicts with MSVC’s linker. You can find out by running 'which link' to see which link.exe you are using. If it is located at /bin/link.exe, then you have the wrong one in your PATH. Either move or remove that copy, or make sure MSVC’s link.exe takes precedence in your PATH over coreutils'.