fastrlock unable to makepkg -sri
Jim-Holmstroem opened this issue · 4 comments
Jim-Holmstroem commented
gcc: error: fastrlock/rlock.c: No such file or directory
gcc: fatal error: no input files
compilation terminated.
error: command 'gcc' failed with exit status 1
==> ERROR: A failure occurred in build().
Aborting...
it worked after
touch src/fastrlock/fastrlock/rlock.c
mratsim commented
Curious, I'm in the process of rebuilding my whole setup and the PKGBUILD worked out of the box:
Jim-Holmstroem commented
tried it again on another computer (I'm 90% sure)
reproduced by:
setup
git clone git@github.com:mratsim/Arch-Data-Science
cd Arch-Data-Science
cd python-fastrlock
build
$ makepkg -sri
==> Making package: python-fastrlock-git r32.17a4b77-1 (Wed 24 Oct 2018 07:05:20 AM UTC)
==> Checking runtime dependencies... [840/912]
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Cloning fastrlock git repo...
Cloning into bare repository '/home/jim/Programming/Arch-Data-Science/python-fastrlock/fastrlock'...
remote: Enumerating objects: 33, done.
remote: Counting objects: 100% (33/33), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 118 (delta 13), reused 24 (delta 12), pack-reused 85
Receiving objects: 100% (118/118), 27.25 KiB | 17.00 KiB/s, done.
Resolving deltas: 100% (50/50), done.
==> Validating source files with md5sums...
fastrlock ... Skipped
==> Extracting sources...
-> Creating working copy of fastrlock git repo...
Cloning into 'fastrlock'...
done.
==> Starting pkgver()...
==> Starting build()...
NOTE: generated sources not available, need Cython to build
WARNING: trying to build with Cython, but it is not installed
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/fastrlock
copying fastrlock/__init__.py -> build/lib.linux-x86_64-3.7/fastrlock
copying fastrlock/__init__.pxd -> build/lib.linux-x86_64-3.7/fastrlock
copying fastrlock/rlock.pxd -> build/lib.linux-x86_64-3.7/fastrlock
copying fastrlock/_lock.pxi -> build/lib.linux-x86_64-3.7/fastrlock
running build_ext
building 'fastrlock.rlock' extension
creating build/temp.linux-x86_64-3.7
creating build/temp.linux-x86_64-3.7/fastrlock
gcc -pthread -DNDEBUG -g -fwrapv -O3 -Wall -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -I/us
r/include/python3.7m -c fastrlock/rlock.c -o build/temp.linux-x86_64-3.7/fastrlock/rlock.o
gcc: error: fastrlock/rlock.c: No such file or directory
gcc: fatal error: no input files
compilation terminated.
error: command 'gcc' failed with exit status 1
==> ERROR: A failure occurred in build().
Aborting...
files after crash
$ ls -R
.:
fastrlock
pkg
PKGBUILD
src
./fastrlock:
branches
config
description
HEAD
hooks
info
objects
packed-refs
refs
./fastrlock/branches:
./fastrlock/hooks:
applypatch-msg.sample
commit-msg.sample
fsmonitor-watchman.sample
post-update.sample
pre-applypatch.sample
pre-commit.sample
prepare-commit-msg.sample
pre-push.sample
pre-rebase.sample
pre-receive.sample
update.sample
./fastrlock/info:
exclude
./fastrlock/objects:
info
pack
./fastrlock/objects/info:
./fastrlock/objects/pack:
pack-9099231abe522c383efbb9795703d3ffdfff2f06.idx
pack-9099231abe522c383efbb9795703d3ffdfff2f06.pack
./fastrlock/refs:
heads
tags
./fastrlock/refs/heads:
./fastrlock/refs/tags:
./src:
fastrlock
./src/fastrlock:
build
CHANGES.rst
fastrlock
LICENSE
lockbench.py
Makefile
MANIFEST.in
README.rst
setup.py
./src/fastrlock/build:
lib.linux-x86_64-3.7
temp.linux-x86_64-3.7
./src/fastrlock/build/lib.linux-x86_64-3.7:
fastrlock
./src/fastrlock/build/lib.linux-x86_64-3.7/fastrlock:
__init__.pxd
__init__.py
_lock.pxi
rlock.pxd
./src/fastrlock/build/temp.linux-x86_64-3.7:
fastrlock
./src/fastrlock/build/temp.linux-x86_64-3.7/fastrlock:
./src/fastrlock/fastrlock:
fastrlock_helpers.h
__init__.pxd
__init__.py
_lock.pxi
rlock.pxd
rlock.pyx
tests
./src/fastrlock/fastrlock/tests:
__init__.py
test_rlock.py
mratsim commented
I checked the repo: https://github.com/scoder/fastrlock/tree/master/fastrlock, the cython should probably be a makedepends.
I'm away from my Arch box until next week but I'm pretty sure this is the issue.