[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Custom make rules yield ambiguous result
From: |
NightStrike |
Subject: |
Custom make rules yield ambiguous result |
Date: |
Fri, 9 Apr 2010 18:32:37 -0400 |
This is regarding the following file:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/trunk/mingw-w64-crt/Makefile.am?revision=2163&view=markup
Down at lines 937 to 941, there are two sets of rules, one for 3
specific files and one for the rest of the libs we generate:
lib64/libcrtdll.a lib64/libmsvcrt.a lib64/libmsvcr80.a: lib64/lib%.a:
lib64/%.def
$(DTDEF) $< --dllname $*.dll -m i386:x86-64 --as-flags=--64
lib64/lib%.a: lib64/%.def
$(DTDEF) $< -m i386:x86-64 --as-flags=--64
What I noticed is happening is that those three files, libcrtdll.a,
libmsvcrt.a, and libmsvcr80.a, are being built using the second rule
instead of the first, and so they don't contain the rather crucial
--dllname option.
What can I do about this?
- Custom make rules yield ambiguous result,
NightStrike <=