1 |
Hi, |
2 |
|
3 |
I am trying to create an ebuild file for |
4 |
https://github.com/NVIDIA/libnvidia-container. It has a few other |
5 |
dependencies which will be built by itself. |
6 |
|
7 |
My ebuild can download and compile those dependencies. But one of the |
8 |
dependency "libtirpc-1.3.2" needs to install itself in the temporary |
9 |
portage environment. Its Makefile allows me to pass in the "DESTDIR" |
10 |
variable which I passed in |
11 |
"/var/tmp/portage/sys-libs/libnvidia-container-1.10.0/work/libnvidia-container-1.10.0/deps", |
12 |
but when it installs, the package is installed to |
13 |
"/var/tmp/portage/sys-libs/libnvidia-container-1.10.0/work/libnvidia-container-1.10.0/deps/var/tmp/portage/sys-libs/libnvidia-container-1.10.0/work/libnvidia-container-1.10.0/deps/usr/local", |
14 |
the working director got repeated after the "deps" directory. |
15 |
|
16 |
I checked the makefile, but could not figure out where that path got |
17 |
replicated. I guess when running inside the portage build environment, |
18 |
there's some "chroot" trick that prevents packages from writing the root |
19 |
file system. |
20 |
|
21 |
So I want to ask if I need to do a "make install" during compilation, how |
22 |
should I pass the destination directory? |
23 |
|
24 |
|
25 |
Thanks |