commit | a174e2f83b9ae3c60968fb200b4b367f4109e8ce | [log] [tgz] |
---|---|---|
author | Josh Conner <joshconner@google.com> | Thu Feb 02 16:53:46 2017 -0800 |
committer | Joshua Conner <joshconner@google.com> | Fri Feb 03 00:55:28 2017 +0000 |
tree | 71c309dcc40c4f2284236f943597f2a14a545e78 | |
parent | 9b0e1d59dd69550c03a41e3461cc22f1fd864fba [diff] |
Inform make which cmds are dash builtins. Change-Id: I1aa9d6bc6578c3ebd4247604cf0004ae0edbaf2d
This is a fork of GNU Make, with support for running on Fuchsia.
To build a native version of GNU Make for fuchsia, configure in a new directory with:
$ <path-to-make>/configure \ --host=<arch>-fuchsia \ CC=<path-to-compiler>/<arch>-fuchsia-gcc
(where <arch>
is one of: x86_64
, aarch64
, or arm
)
And then simply invoke ‘make’:
$ make
When merging upstream changes, there are a number of files that must be regenerated. Here are the steps to follow to regenerate the files from a virgin git repo (all commands shown should be run from within the source directory):
These can mostly be installed into a user-specific directory to avoid updating the default versions of these utilities. However, if pkg-config is installed in a user-specific directory, you will need to set the environment variable ACLOCAL_PATH
to reference the local “share” subdirectory to avoid getting undefined m4 macro errors for PKG_PROG_PKG_CONFIG
. For example, if pkg-config is installed in /my/usr/local
, ACLOCAL_PATH
should be set to /my/usr/local/share
.
$ autoreconf -i
$ ./configure
$ make scm-update
$ make distclean $ rm -fr autom4te.cache
After these steps, the source tree should be in a state where it can be configured/built as needed. Some of these steps are derived from (but differ slightly from) those given in README.git
.