You are not logged in.
hi
I am trying to create a PKGBUILD for this cross-gcc (the first time I try to create a PKGBUILD):
http://tho-otto.de/crossmint.php
the procedure without makepkg would be:
$ tar -C ./ -xf "gcc-7.2.0-mint-20171006.tar.xz"
$ tar -C ./ -xf "gcc-7.2.0.tar.xz"
$ ./build-gcc-7.2.0-20171006.sh
and it works
but inside a PKGBUILD:
bpaste.net
it doesn't work:
makepkg fails:
....
config.status: executing gccdepdir commands
mkdir -p -- build/.deps
mkdir -p -- ada/.deps
mkdir -p -- brig/.deps
mkdir -p -- c/.deps
mkdir -p -- cp/.deps
mkdir -p -- fortran/.deps
mkdir -p -- go/.deps
mkdir -p -- jit/.deps
mkdir -p -- lto/.deps
mkdir -p -- objc/.deps
mkdir -p -- objcp/.deps
mkdir -p -- c-family/.deps
mkdir -p -- common/.deps
config.status: executing default commands
==> ERROR: A failure occurred in build().
I don't understand this.
What is the difference between manually calling ./build-gcc-7.2.0-20171006.sh and let makepkg do this?
aligator
Offline
seems that script sends fail signal instead of sucess. what is the output when type:
echo $?
inmediate after the finish script execution?
usually means 0 = sucess, 1 or more = error
Last edited by sl1pkn07 (2017-10-17 20:24:38)
Offline