common: rename _src_ to _source_ everywhere

This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-01-22 00:00:00 +00:00
parent a1ae3fbd26
commit eccefa4c57
12 changed files with 76 additions and 70 deletions

View File

@@ -535,7 +535,7 @@ You have to checkout to the latest tag to ensure that the scripts match the rele
Be saner and use our custom built QEMU instead:
....
git submodule update --init --recursive "$(./getvar qemu_src_dir)"
git submodule update --init --recursive "$(./getvar qemu_source_dir)"
./build-qemu
./run
....
@@ -656,7 +656,7 @@ which is equivalent to:
Or just remove the `.c` extension from the failing files and try again:
....
cd "$(./getvar kernel_modules_src_dir)"
cd "$(./getvar kernel_modules_source_dir)"
mv broken.c broken.c~
....
@@ -9249,7 +9249,7 @@ A few workarounds are:
If you do this, don't forget to do a:
+
....
cd "$(./getvar parsec_src_dir)"
cd "$(./getvar parsec_source_dir)"
git clean -xdf .
....
before going for the cross compile build.
@@ -11521,9 +11521,9 @@ Analogous to the <<linux-kernel-build-variants>> but with the `--qemu-build-id`
....
./build-qemu
git -C "$(./getvar qemu_src_dir)" checkout v2.12.0
git -C "$(./getvar qemu_source_dir)" checkout v2.12.0
./build-qemu --qemu-build-id v2.12.0
git -C "$(./getvar qemu_src_dir)" checkout -
git -C "$(./getvar qemu_source_dir)" checkout -
./run
./run --qemu-build-id v2.12.0
....
@@ -11656,9 +11656,9 @@ Analogous to the <<linux-kernel-build-variants>> but with the `--build-id` optio
....
./build-buildroot
git -C "$(./getvar buildroot_src_dir)" checkout 2018.05
git -C "$(./getvar buildroot_source_dir)" checkout 2018.05
./build-buildroot --buildroot-build-id 2018.05
git -C "$(./getvar buildroot_src_dir)" checkout -
git -C "$(./getvar buildroot_source_dir)" checkout -
./run
./run --buildroot-build-id 2018.05
....
@@ -11956,7 +11956,7 @@ We then bisected it as explained at: https://stackoverflow.com/questions/4713088
....
root_dir="$(pwd)"
cd "$(./getvar qemu_src_dir)"
cd "$(./getvar qemu_source_dir)"
git bisect start
# Check that our test script fails on v3.0.0-rc3 as expected, and mark it as bad.