Re: link: invalid option -- n.....make[2]: *** [install.windows-x64] Error 2

[Max Power <sixsvalka@gmail.com>]

Thank you Mark,

After trying again and again using mingw, make 4.1 for windows, and the last version of MVC2015 (free version) both windows 8.1 and windows 10, I have to say that I had always the following error: http://www.aps.anl.gov/epics/tech-talk/2015/msg01742.php, about:

...

make[3]: *** No rule to make target 'epicsTempFile.obj', needed by 'antelope.exe'.  Stop.
make[3]: Leaving directory 'c:/base-3.15.2/src/libCom/O.win32-x86'
../../configure/RULES_ARCHS:61: recipe for target 'install.win32-x86' failed
make[2]: *** [install.win32-x86] Error 2
make[2]: Leaving directory 'c:/base-3.15.2/src/libCom'
...

I followed all the indications about the recommendations written in this forwarding, including the modification of the bat file (you mention Mark), but as says Mark at this point, I think the problem is the express edition of MVC2015: 

For building base 3.15.2 with Visual Studio 2015 you need to look at the Known Problems page here.

http://www.aps.anl.gov/epics/base/R3-15/2-docs/KnownProblems.html

It says that you cannot use the Express Edition, you must use the Community Edition (or presumably the licensed version).  You also must apply a patch to base as documented on that page.

Finally I had to do waht I didn't want to, and is use cygwing... It compiled at first time.

anyway Thank you very much

Max

2016-09-07 23:48 GMT+02:00 Mark S. Engbretson <Engbretson@anl.gov>:

Normally, a reasonable system to get good builds with Microsoft compilers uses any modern version of pearl,

Mingw, or gnuwin32.

 

You then modify or use the win32.bat file found in base\startup to point to all your tools.

 

You run *that* and it sets up all the Microsoft paths for all of its stuff.

 

Base should then build without a hitch.

 

Enclosed is how I have my build system set up.for a MSVC2015 system. I renamed the gnu link to be something else since the standard batch file does the directories in the wrong order.   You might try doing a

 

make clean uninstall

 

and starting fresh.

 

Or . . . . if you have a full version of mingw, you could build EPICS with that just to see if it will build or not.

 

 

 

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Max Power
Sent: Wednesday, September 07, 2016 3:51 PM
To: Mark Rivers <rivers@cars.uchicago.edu>
Cc: tech-talk@aps.anl.gov
Subject: Re: link: invalid option -- n.....make[2]: *** [install.windows-x64] Error 2

 

Dear Mark, 

 

Thank you very much for your support. Yes you are totally right, I put first in the PATH, the path to the Microsoft LINK command, but It didn't work. Anyway, I have tried to do what Enbregtson said, and Another compiling/linking problems have appeared. I am going to try to understand what is the new problem, and in both cases: I fix the problem or not I will write the solution or the problem :D.

 

Thank you very much to all

 

Regards

 

2016-09-07 21:39 GMT+02:00 Mark Rivers <rivers@cars.uchicago.edu>:

I think you are confusing 2 things:

 

-          Using gnumake from MinGW, but using the Microsoft Visual Studio compiler and linker.  EPICS_HOST_ARCH=windows-x64 uses the Microsoft compiler and linker.

-          Using the mingw (GNU) compiler and linker.  EPICS_HOST_ARCH=windows-x64-mingw uses the GNU compiler and linker.

 

If you want to use the Microsoft compiler then you need to make sure that the minGW linker does not come first in your PATH, which seems like what is happening.  You can probably change your PATH definition so the Microsoft compiler tools come before the minGW tools.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Max Power
Sent: Wednesday, September 07, 2016 2:26 PM
To: tech-talk@aps.anl.gov
Subject: link: invalid option -- n.....make[2]: *** [install.windows-x64] Error 2

 

Dear guys,

 

I have tried to install EPICS base 3.15.4 in windows 8.1 64 bits using MinGW tools, following instructions in EPICS.org: http://www.aps.anl.gov/epics/base/win32.php and Mark River explanation. 

 

I have used the last version of Visual studio 2015 and all the building tools required.

 

After "make" command execution, everything looked going on perfect until the point the installation has used the "link" command (see below). It says that "link" command does not understand -n option. I have checked that the link.exe command installed with VC2015 has the possibility of using that argument, but the link command from MinGW GNU tools cannot. Any idea or someone with the same problem?

 

Thank you very much in advance!, console outputs coming below

 

....

link -nologo  -LTCG -incremental:no -opt:ref -release -version:3.15 /MACHINE:X64

              -out:antelope.exe       epicsTempFile.obj closure.obj error.obj la

lr.obj lr0.obj antelope.obj mkpar.obj output.obj reader.obj skeleton.obj symtab.

obj verbose.obj warshall.obj

link: invalid option -- n

Try `link --help' for more information.

make[3]: Leaving directory `/c/Users/Max/AppData/Roaming/SPB_Data/epics/base/s

rc/libCom/O.windows-x64'

make[2]: *** [install.windows-x64] Error 2

make[2]: Leaving directory `/c/Users/Max/AppData/Roaming/SPB_Data/epics/base/src/libCom'

make[1]: *** [libCom.install] Error 2

make[1]: Leaving directory `/c/Users/Max/AppData/Roaming/SPB_Data/epics/base/s

rc'

make: *** [src.install] Error 2

 

 

link version that the make uses:

 

$ link

link: missing operand

Try `link --help' for more information.

 

$ link --version

link (GNU coreutils) 5.97

Copyright (C) 2006 Free Software Foundation, Inc.

This is free software.  You may redistribute copies of it under the terms of

the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.

There is NO WARRANTY, to the extent permitted by law.

 

Written by Michael Stone.

 

$ link --help

Usage: link FILE1 FILE2

  or:  link OPTION

Call the link function to create a link named FILE2 to an existing FILE1.

 

      --help     display this help and exit

      --version  output version information and exit

 

Report bugs to <bug-coreutils@gnu.org>.