summaryrefslogtreecommitdiff
path: root/t/t3506-cherry-pick-ff.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2019-02-13 02:19:49 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-02-13 13:46:58 -0800
commitbb02e7a560de818eac48344717bc52ca51b01908 (patch)
tree278a996e656180fe584f7b29a19ab74647bc8fb3 /t/t3506-cherry-pick-ff.sh
parentmingw: fix CPU reporting in `git version --build-options` (diff)
downloadtgif-bb02e7a560de818eac48344717bc52ca51b01908.tar.xz
mingw: use a more canonical method to fix the CPU reporting
In `git version --build-options`, we report also the CPU, but in Git for Windows we actually cross-compile the 32-bit version in a 64-bit Git for Windows, so we cannot rely on the auto-detected value. In 3815f64b0dd9 (mingw: fix CPU reporting in `git version --build-options`, 2019-02-07), we fixed this by a Windows-only workaround, making use of magic pre-processor constants, which works in GCC, but most likely not all C compilers. As pointed out by Eric Sunshine, there is a better way, anyway: to set the Makefile variable HOST_CPU explicitly for cross-compiled Git. So let's do that! This reverts commit 3815f64b0dd983bdbf9242a0547706d5d81cb3e6 partially. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3506-cherry-pick-ff.sh')
0 files changed, 0 insertions, 0 deletions