| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: If9a0906a76943160cfdbd647b26a801bc4389615
|
| |
|
|
|
|
| |
Change-Id: I37e6706ff244c9cc21b0826e61ef5d7cd72b3566
|
|
|
|
| |
Change-Id: I6e0758e543a89f593a1b0432b28b4c9768993af7
|
|
|
|
| |
Change-Id: I4362106ac5d221241eafdf44705ca5553ac7013c
|
|
|
|
| |
Change-Id: I9dbe77062df3a9b02dab0f5755c0e616829fa125
|
|
The top-level Makefile invokes autogen.sh (and thereby configure) in an
environment which is polluted by config_host.mk; this causes at least
the problem that following a "make clean", the bootstrap script will not
copy dmake to its destination because BUILD_DMAKE=NO is set from
config_host.mk, which is apparently due to the PATH being polluted from
config_host.mk, so configure finds the dmake in the build tree.
So split up top-level Makefile into Makefile, which invokes autogen.sh,
and Makefile.top, which does everything else.
|