diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2018-09-18 23:40:55 -0400 |
---|---|---|
committer | Simon Marchi <simon.marchi@polymtl.ca> | 2018-09-18 23:40:55 -0400 |
commit | b567ca638c274e27969975403b885973af9ccae6 (patch) | |
tree | 86bf6c86b2929f9471747d95457f391ea7f8204c /gdb/ada-lang.c | |
parent | 48219c6a06091b873f39c64c5df12ba7ec37a2e0 (diff) | |
download | fsf-binutils-gdb-b567ca638c274e27969975403b885973af9ccae6.zip fsf-binutils-gdb-b567ca638c274e27969975403b885973af9ccae6.tar.gz fsf-binutils-gdb-b567ca638c274e27969975403b885973af9ccae6.tar.bz2 |
Carry the gnulib getcwd backport as a patch
Commit
e2fc52e7457 ("Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB")
backported some changes from a future gnulib version to our import.
However, this means that every time someone wants to change our gnulib
import (e.g. add a module), they must make sure not to include that
backported change. It also means that someone running the
update-gnulib.sh script without changes will get some diffs and wonder
why.
Instead, I suggest we carry that backport as a patch applied by the
update-gnulib.sh script after running the import tool. It will make it
clear what backport or local modification we have and should make
running update-gnulib.sh give a reproducible result.
There is a hunk in the configure file in this patch, this is because the
commit that backported the getcwd bits didn't include the re-generated
configure.
Note: you'll need this patch as well to get deterministic results:
Generate aclocal-m4-deps.mk more deterministically and portably.
https://sourceware.org/ml/gdb-patches/2018-09/msg00643.html
gdb/ChangeLog:
* patches/0001-Fix-PR-gdb-23558-Use-system-s-getcwd-when-cross-comp.patch:
New file.
* update-gnulib.sh: Apply patch.
* configure: Re-generate.
Diffstat (limited to 'gdb/ada-lang.c')
0 files changed, 0 insertions, 0 deletions