projects
/
ghc-hetmet.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
ded6781
)
Link with hpc even if GhcWithInterpreter is not set
author
Ian Lynagh
<igloo@earth.li>
Thu, 26 Jul 2007 16:42:01 +0000
(16:42 +0000)
committer
Ian Lynagh
<igloo@earth.li>
Thu, 26 Jul 2007 16:42:01 +0000
(16:42 +0000)
compiler/Makefile
patch
|
blob
|
history
diff --git
a/compiler/Makefile
b/compiler/Makefile
index
0b84536
..
252da0d
100644
(file)
--- a/
compiler/Makefile
+++ b/
compiler/Makefile
@@
-410,11
+410,16
@@
endif
# enabled when we are bootstrapping with the same version of GHC, and
# the interpreter is supported on this platform.
# enabled when we are bootstrapping with the same version of GHC, and
# the interpreter is supported on this platform.
+ifeq "$(bootstrapped)" "YES"
+SRC_HC_OPTS += -package hpc
+PKG_DEPENDS += hpc
+endif
+
ifeq "$(GhcWithInterpreter) $(bootstrapped)" "YES YES"
# Yes, include the interepreter, readline, and Template Haskell extensions
ifeq "$(GhcWithInterpreter) $(bootstrapped)" "YES YES"
# Yes, include the interepreter, readline, and Template Haskell extensions
-SRC_HC_OPTS += -DGHCI -package template-haskell -package hpc
-PKG_DEPENDS += template-haskell hpc
+SRC_HC_OPTS += -DGHCI -package template-haskell
+PKG_DEPENDS += template-haskell
# Should GHCI be building info tables in the TABLES_NEXT_TO_CODE style
# or not?
# Should GHCI be building info tables in the TABLES_NEXT_TO_CODE style
# or not?