diff options
| author | Wonkyu Kim <wonkyu.kim@intel.com> | 2019-01-18 17:33:55 -0800 |
|---|---|---|
| committer | Patrick Georgi <pgeorgi@google.com> | 2019-01-22 19:45:27 +0000 |
| commit | 31eeda1c44d4055113e6a64e3a2e4d7a22ae4e0a (patch) | |
| tree | cafda8a1cca1499b21f051227d7c549a8128ead9 | |
| parent | 2ea99da49de6d7faa499510b2d747532be776172 (diff) | |
| download | coreboot-31eeda1c44d4055113e6a64e3a2e4d7a22ae4e0a.tar.xz | |
util/crossgcc: use fixed length version string.
After merging util/crossgcc: derive date and version from latest commit
(https://review.coreboot.org/c/coreboot/+/30804),
crossgcc build is broken in internal repository due to long version
name;coreboot.org repository is ok because it uses short tag name.
The patch uses "git describe" which is dependent on git tag name.
If tag name is little bit long, it can cause crossgcc build failed.
To avoid this issue, use only short version of hash string
which is fixed length. And it's enough as version string,
because we also use date(CROSSGCC_DATE) together.
TEST=Build crossgcc in both coreboot.org and internal repository
which uses longer tag name and check version string in build log.
Change-Id: I405b2e4e5c05831c25aebf1c73a281adab8ef452
Signed-off-by: Wonkyu Kim <wonkyu.kim@intel.com>
Reviewed-on: https://review.coreboot.org/c/31001
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
| -rwxr-xr-x | util/crossgcc/buildgcc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/util/crossgcc/buildgcc b/util/crossgcc/buildgcc index 211494d419..4b5a718a8e 100755 --- a/util/crossgcc/buildgcc +++ b/util/crossgcc/buildgcc @@ -31,7 +31,7 @@ cd "$(dirname "$0")" || exit 1 CROSSGCC_DATE="$(git log -n 1 --pretty=%ad --date=short .)" -CROSSGCC_VERSION="$(git describe $(git log -n 1 --pretty=%h .))" +CROSSGCC_VERSION="$(git log -n 1 --pretty=%h .)" CROSSGCC_COMMIT=$( git describe ) # default settings |