Signed-off-by: Ting Liu <b28...@freescale.com> Signed-off-by: Chunrong Guo <b40...@freescale.com> --- Makefile | 22 +++++++++++----------- 1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/Makefile b/Makefile index 05ad9b4..987fcc3 100644 --- a/Makefile +++ b/Makefile @@ -146,17 +146,17 @@ endif # If TMPLIB64 is set, then sure we are not resolving LIB32 and LIB64 to the # same place -ifdef TMPLIB64 - -REALLIB32 = $(realpath $(PREFIX)/$(LIB32)) -REALLIB64 = $(realpath $(PREFIX)/$(LIB64)) -ifneq ($(realpath $(PREFIX)),) -ifeq ($(REALLIB32),$(REALLIB64)) -$(error LIB32 ($(PREFIX)/$(LIB32) to $(REALLIB32)) and LIB64 ($(PREFIX)/$(LIB64) to $(REALLIB64)) are resolving to the same place. Manually specify LIB32 and LIB64. e.g. make PREFIX=$(PREFIX) LIB32=lib32 LIB64=lib64) -endif -endif - -endif +#ifdef TMPLIB64 +# +#REALLIB32 = $(realpath $(PREFIX)/$(LIB32)) +#REALLIB64 = $(realpath $(PREFIX)/$(LIB64)) +#ifneq ($(realpath $(PREFIX)),) +#ifeq ($(REALLIB32),$(REALLIB64)) +#$(error LIB32 ($(PREFIX)/$(LIB32) to $(REALLIB32)) and LIB64 ($(PREFIX)/$(LIB64) to $(REALLIB64)) are resolving to the same place. Manually specify LIB32 and LIB64. e.g. make PREFIX=$(PREFIX) LIB32=lib32 LIB64=lib64) +#endif +#endif +# +#endif HEADERDIR = $(PREFIX)/include LIBDIR32 = $(PREFIX)/$(LIB32) -- 1.7.5.4 ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Libhugetlbfs-devel mailing list Libhugetlbfs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
