(quoting from the build log you linked to)
link -out:blib\arch\auto\xsmode\xsmode.dll -dll -nologo -nodef +aultlib -d ebug -opt:ref,icf -libpath:"C:\Perl\lib\CORE" -machine:x86 xsmode.ob +j C:\Per l\lib\CORE\perl58.lib oldnames.lib kernel32.lib user32.lib gdi32.lib w +inspool.li b comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib netap +i32.lib uu id.lib ws2_32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.l +ib msvcrt. lib -def:xsmode.def link: invalid option -- o Try `link --help' for more information. NMAKE : fatal error U1077: 'link' : return code '0x1'
I can't help getting the impression that it's not the linker belonging to the compiler suite that's being called here, but rather some Windows port of the Unix command 'link' - at least, if I type the respective command on my Debian box, I get a rather similarly looking output:
$ link -out:... link: invalid option -- o Try `link --help' for more information.
I wouldn't be too surprised, if you got
$ link --help Usage: link FILE1 FILE2 or: link OPTION Call the link function to create a link named FILE2 to an existing FIL +E1. --help display this help and exit --version output version information and exit Report bugs to <bug-coreutils@gnu.org>.
if you typed link --help :)
In that case, make sure this command is no longer found along the search path, while trying to build stuff... Just a thought.
In reply to Re^7: inline c
by almut
in thread inline c
by panaman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |