package() function doesn't recognise shell script

LukeLabrie · 2022-02-20 18:27:53

In the PKGBUILD file for an AUR I am working on, I get the following error in my package() function:

./install.sh: No such file or directory

here is the function:

package() {
    cd /opt/"$pkgname"/pymoab
    ./install.sh
    python setup.py install
}

The file is in the directory, and it is called 'install.sh.cmake'.

I have tried changing the command in the package() function multiple ways, including:

bash install.sh
bash install.sh.cmake
bash ./install.sh
bash ./install.sh.cmake
./install.sh
./install.sh.cmake
. ./install.sh
. ./install.sh.cmake

All give the same error.

I originally wrote this as a set of shells scripts, which work well. In the shell script the command is:

bash install.sh

So I'm not sure why it doesn't work in the package() function.

All input appreciated. Let me know if I can provide more detail.

loqs · 2022-02-20 18:30:41

If /opt/"$pkgname"/pymoab is created by the PKGBUILD you can not use it in the PKGBUILD as it will not exist until the package is installed.

LukeLabrie · 2022-02-20 18:32:29

Ohh that would explain it. Thanks.

Slithery · 2022-02-20 18:34:14

So are you actually using Arch now or have you just reposted this hiding the fact that your using a different distro?

LukeLabrie · 2022-02-20 18:34:38

But when I look at other AURs, I see that package() is entering directories created in the build function.

LukeLabrie · 2022-02-20 18:35:13

@Slithery, using Arch and seeing the same issue

ayekat · 2022-02-20 18:52:55

LukeLabrie wrote:

But when I look at other AURs, I see that package() is entering directories created in the build function.

Yes, but /opt (or anything underneath) is certainly not created by the build() function. Your PKGBUILD code should ideally only operate within $srcdir and $pkgdir.

LukeLabrie · 2022-02-23 16:52:36

I updated my package() function to only include $srcdir and $pkgdir but I am still seeing the same error:

package() {
	cd $srcdir/$pkgname/build
	make DESTDIR="${pkgdir}" install
	cd $srcdir/$pkgname/pymoab
	bash install.sh
	python setup.py install
}

bash: install.sh: No such file or directory

Any ideas?

Scimmia · 2022-02-23 16:53:48

What are you trying to package, exactly?

LukeLabrie · 2022-02-23 16:57:38

this PKGBUILD is for moab (https://bitbucket.org/fathomteam/moab)

Slithery · 2022-02-23 17:00:17

Post the complete PKGBUILD you are having issues with, we need to see it in it's entirety.

Scimmia · 2022-02-23 17:01:28

So the CMakeLists.txt file includes this ( https://bitbucket.org/fathomteam/moab/s … t#lines-89 ), and it has to be processed by cmake to make the install.sh script. Have you done this?

Or better yet, skip install.sh all together, all it does is call setup.py. https://bitbucket.org/fathomteam/moab/s … e#lines-12

Last edited by Scimmia (2022-02-23 17:03:40)

LukeLabrie · 2022-02-23 17:02:56

Sure, see below:

pkgname=moab
pkgver=git
pkgrel=1
pkgdesc="The Mesh-Oriented datABase MOAB is a component for representing and evaluating mesh data"
arch=(x86_64)
url="https://bitbucket.org/fathomteam/moab"
license=(GPL3)
makedepends=(
	git
	python
	cmake
	gcc-fortran
	eigen
	netcdf
	hdf5
	cython
	blas
	lapack
	python-numpy
	python-setuptools
	"glibc>=2.34"
)
provides=("${pkgname%}")
source=("${pkgname}::git+${url}.git")

build() {
	cd $srcdir/$pkgname
	mkdir build && cd build
	# test later if it's necessary to have double compilation
	cmake .. -DENABLE_HDF5=ON \
		       -DENABLE_PYMOAB=ON \
		       -DENABLE_NETCDF=ON \
		       -DENABLE_FORTRAN=OFF \
		       -DENABLE_BLASLAPACK=OFF \
		       -DBUILD_SHARED_LIBS=ON
	make
}

package() {
	cd $srcdir/$pkgname/build
	make DESTDIR="${pkgdir}" install
	cd $srcdir/$pkgname/pymoab
	bash install.sh
	python setup.py install
}

LukeLabrie · 2022-02-23 17:06:57

@Scimmia I don't think I've done that and I'm not really clear on what it means, but when I wrote this as a set of shell scripts it worked fine, so I'm not convinced that that's the issue.

Scimmia · 2022-02-23 17:07:59

If you had to run 'python setup.py' separately, it DIDN'T work fine.

LukeLabrie · 2022-02-23 17:10:41

I see. Well that comes after the bash install.sh command so I don't think it would be the reason that that didn't run no?

LukeLabrie · 2022-02-23 17:12:08

ah I just saw your edit. I've tried that and then I get the same error on the python script. Will try again now.

LukeLabrie · 2022-02-23 17:25:19

Similar error on the python script:

[$srcdir]/moab/pymoab/setup.py': [Errno 2] No such file or directory

I can see the file in the directory as "setup.py.in"

Scimmia · 2022-02-23 17:30:07

Found it. You're building in $srcdir/$pkgname/build, but you're trying to install pymoab from the raw, unbuilt source in $srcdir/$pkgname/pymoab.

Before you upload the PKGBUILD, though, you have a LOT of things to fix. Even the pkgname is wrong.

Last edited by Scimmia (2022-02-23 17:30:33)

LukeLabrie · 2022-02-24 15:50:38

Ok. I'm not sure how that resolves the issue I'm seeing though. Shouldn't it still be able to run a bash script or a python script even if that were the case? Regardless of where I am building/installing, those files exist in the directories when the commands are run.

What do you mean that the pkgname is wrong?

Scimmia · 2022-02-24 16:06:15

That's my entire point, those files do not exist where you're trying to run them. Look for yourself. They only exist in build/pymoab.

As for cleaning up the PKGBUILD, including the pkgname, start here: https://wiki.archlinux.org/title/VCS_package_guidelines

Trilby · 2022-02-24 16:12:13

For cleaning up the PKGBUILD, follow the link above and review the pkgname, pkgver, depends, and makedepends variables (and some checksum variable), then add a pkgver and prepare function to create the build directory as the current use of mkdir (at least without "-p") in the build function will make rebuilds fail.

Last edited by Trilby (2022-02-24 16:13:50)

LukeLabrie · 2022-02-24 16:22:37

When I look I see the files there. If I go to .../src/moab/pymoab I see both the the python script and the shell script (not sure if this forum allows for screenshots). Just to demonstrate, I added an ls command just before it tries to run the python script.

package() {
	cd $srcdir/$pkgname/build
	make DESTDIR="${pkgdir}" install
	cd $srcdir/$pkgname/pymoab
	ls
	python setup.py install
}

Here is the output

CMakeLists.txt	cmake		  interface_notes.txt  pyproject.toml	 setup.py.cmake.in  tests
Makefile.am	install.sh.cmake  pymoab	       requirements.txt  setup.py.in


python: can't open file '[$srcdir/$pkgname]/pymoab/setup.py': [Errno 2] No such file or directory

So unless I'm misunderstanding something about the way this package() function works, it is certainly in the correct directory when it attempts to run the files.

Scimmia · 2022-02-24 16:28:27

install.sh.cmake and setup.py.cmake.in/setup.py.in ARE NOT SCRIPTS. We covered this back in post #12. You cannot run them.

LukeLabrie · 2022-02-24 16:46:48

I see. Seems to be working now. I am past that error at least. Thanks for your help.

Arch Linux

#1 2022-02-20 18:27:53

package() function doesn't recognise shell script

#2 2022-02-20 18:30:41

Re: package() function doesn't recognise shell script

#3 2022-02-20 18:32:29

Re: package() function doesn't recognise shell script

#4 2022-02-20 18:34:14

Re: package() function doesn't recognise shell script

#5 2022-02-20 18:34:38

Re: package() function doesn't recognise shell script

#6 2022-02-20 18:35:13

Re: package() function doesn't recognise shell script

#7 2022-02-20 18:52:55

Re: package() function doesn't recognise shell script

#8 2022-02-23 16:52:36

Re: package() function doesn't recognise shell script

#9 2022-02-23 16:53:48

Re: package() function doesn't recognise shell script

#10 2022-02-23 16:57:38

Re: package() function doesn't recognise shell script

#11 2022-02-23 17:00:17

Re: package() function doesn't recognise shell script

#12 2022-02-23 17:01:28

Re: package() function doesn't recognise shell script

#13 2022-02-23 17:02:56

Re: package() function doesn't recognise shell script

#14 2022-02-23 17:06:57

Re: package() function doesn't recognise shell script

#15 2022-02-23 17:07:59

Re: package() function doesn't recognise shell script

#16 2022-02-23 17:10:41

Re: package() function doesn't recognise shell script

#17 2022-02-23 17:12:08

Re: package() function doesn't recognise shell script

#18 2022-02-23 17:25:19

Re: package() function doesn't recognise shell script

#19 2022-02-23 17:30:07

Re: package() function doesn't recognise shell script

#20 2022-02-24 15:50:38

Re: package() function doesn't recognise shell script

#21 2022-02-24 16:06:15

Re: package() function doesn't recognise shell script

#22 2022-02-24 16:12:13

Re: package() function doesn't recognise shell script

#23 2022-02-24 16:22:37

Re: package() function doesn't recognise shell script

#24 2022-02-24 16:28:27

Re: package() function doesn't recognise shell script

#25 2022-02-24 16:46:48

Re: package() function doesn't recognise shell script

Board footer