This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: make 3.81 bug - error: multiple target patterns. Stop.
On Wed, Apr 01, 2009 at 10:25:08AM -0400, Allan Schrum wrote:
>> Hello all
>>
>> Since the make 3.81 release in Cygwin, I constantly have issues with
>> this released version:
>> When using Mentor ModelSim to compile and simulate VHDL, the released
>> make 3.81 fails by executing generated Makefiles from ModelSim (using
>> 'vmake > Makefile').
>>
>> It does not occur with make 3.79.1 or the patched 3.81 version
>> available at https://software.sandia.gov/trac/acro/ticket/2835 and
>> using the binary at http://www.cmake.org/files/cygwin/make.exe
>>
>> Command line log:
>> -----------------
>> admin@Blueshark /cygdrive/d/Xilinx/example_design/sim
>> $ make
>> Makefile:128: *** multiple target patterns. Stop.
>>
>> admin@Blueshark /cygdrive/d/Xilinx/example_design/sim
>> $ make_3.79.1.exe
>> make_3.79.1: Nothing to be done for `whole_library'.
>>
>> admin@Blueshark /cygdrive/d/Xilinx/example_design/sim
>> $ make_3.81_fixed.exe
>> make_3.81_fixed: Nothing to be done for `whole_library'.
>>
>>
>> If you could fix this when time comes by, I think many hardware
>> engineers will be very happy...
>> The last discussion about this issue was in 2006 at
>> http://sourceware.org/ml/cygwin/2006-07/msg00667.html
>>
>> Attached as well the (generated) Makefile, where the released Cygwin
>> make 3.81 complains about line 128
>
>Lines 4 and 5 of the Makefile define LIB_UNISIM and LIB_IEEE using
>paths that are Windows path (meaning that they contain a colon as in
>"C:\Tools"). This confuses "make" it seems. If you change them to a
>reasonable filename structure (reasonable for "make") then it seems to
>progress.
>
>I tested with "make -n -f Makefile" to reproduce the problem. By
>removing the colons, the "make" stopped complaining and progressed.
>
>Can you use the Unix-style of paths for these two symbols rather than
>the Windows-style names? I would also suggest replacing the
>reverse-slash characters "\" with forward-slash characters "/" in the
>path.
There is no mystery here. Not using MS-DOS-style paths is exactly what
the referenced message talks about.
As I've said on many occasions, I'll produce a new version of make when
there is a new version upstream. I'm not going to hack a version to
accommodate MS-DOS paths.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/