PKGBUILD: untuck the way generic subarch is set
Previously a really convoluted two stage 'yes' invocation was used with that required weird formatting. Switch to using the good old configs enabling.
This commit is contained in:
parent
6258f9892c
commit
d70024da20
1 changed files with 3 additions and 2 deletions
5
PKGBUILD
5
PKGBUILD
|
@ -345,8 +345,9 @@ update_defconfig() {
|
||||||
# check if subarch is a number
|
# check if subarch is a number
|
||||||
if [[ ${_subarch} =~ ^[0-9]+$ ]] && ((_subarch>=1)); then
|
if [[ ${_subarch} =~ ^[0-9]+$ ]] && ((_subarch>=1)); then
|
||||||
if [ "${_subarch}" == "41" ]; then
|
if [ "${_subarch}" == "41" ]; then
|
||||||
yes "${_subarch}
|
scripts/config -e GENERIC_CPU
|
||||||
${_subarch_microarch}" | make ${BUILD_FLAGS[*]} oldconfig
|
scripts/config --set-val X86_64_VERSION "${_subarch_microarch}"
|
||||||
|
make ${BUILD_FLAGS[*]} oldconfig
|
||||||
else
|
else
|
||||||
yes "${_subarch}" | make ${BUILD_FLAGS[*]} oldconfig
|
yes "${_subarch}" | make ${BUILD_FLAGS[*]} oldconfig
|
||||||
fi
|
fi
|
||||||
|
|
Loading…
Reference in a new issue