Launchpad itself

Executables required to build package not found

Asked by Louis Duchemin

Hi

I'm trying to build a package with opam (Ocaml package manager) on launchpad. Dependencies and some binary tools for building the package are vendored in my package sources, in a directory .opam.
Binary tools for building the package are in .opam/default/bin.
In my debian/rules, I add this directory to PATH as follow :
PATH:="$(PATH):$(CURDIR)/.opam/default/bin"

$PATH evaluates to : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/<<PKGBUILDDIR>>/.opam/default/bin"

However, running `dune build` gives :
make: dune: No such file or directory

I don't understand why dune executable is not found, even though it is present in .opam/default/bin from the build directory.

Any help would be appreciated

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Louis Duchemin
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said : 		#1

Can you provide a link to the failing build so that we can look into it?

Revision history for this message
Louis Duchemin (lsdch) said : 		#2

Sure, here is one :
https://launchpad.net/~phoogle/+archive/ubuntu/pelican-tmp/+build/25501012
Thanks for helping !

Revision history for this message
Jürgen Gmach (jugmac00) said : 		#3

I am not a packaging expert, so hopefully Colin finds time to have another look.

In the past I had similar error messages when the file actually was present, but it had the wrong architecture. Maybe double check that.

Also, maybe there is a way to print the path and the directory structure somehow, so we could compare whether they match?

Revision history for this message
Louis Duchemin (lsdch) said : 		#4

I ended up using another approach, as I found out the executables I need could be installed as ubuntu package dependencies.
I'm marking this problem as solved, but would still be interested in understanding this strange behavior with $PATH.
Thanks for your answers !