And this fails with cc1: error: /alt/root/path//usr/include: Permission denied. Also, obviously the package build should not be aware of the alternative root it will be installed into. dev-lang/perl-5.24.0-r1 works okay, so my workaround is to use that. example output: i486-pc-linux-gnu-gcc -c -I/root/makelive/chatserver/chatserver//usr/include -fwrapv -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings -O2 -march=pentium3 -pipe -fno-stack-protector -fomit-frame-pointer -DVERSION=\"2.069\" -DXS_VERSION=\"2.069\" -fPIC "-I../.." -DNO_VIZ -DZ_SOLO -DGZIP_OS_CODE=3 Zlib.c cc1: error: /root/makelive/chatserver/chatserver//usr/include: Permission denied Makefile:350: recipe for target 'Zlib.o' failed make[1]: *** [Zlib.o] Error 1
Please attach the failing build log and emerge --info.
Created attachment 462040 [details] build log for perl-5.24.1_rc4
Created attachment 462042 [details] emerge --info output Ha ha, how relevant.
This is just silly, but playing along. And yes, still fails with 5.24.1_rc4.
OK so I can't find any occurrence of ROOT in the perl-5.24.1-r1 source, and I can't find any smoking gun in the diff from 5.24.0 to 5.24.1 ...
(In reply to Urja Rannikko from comment #0) > And this fails with cc1: error: /alt/root/path//usr/include: Permission > denied. > > Also, obviously the package build should not be aware of the alternative > root it will be installed into. > > dev-lang/perl-5.24.0-r1 works okay, so my workaround is to use that. > > example output: > i486-pc-linux-gnu-gcc -c > -I/root/makelive/chatserver/chatserver//usr/include -fwrapv > -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall > -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings -O2 > -march=pentium3 -pipe -fno-stack-protector -fomit-frame-pointer > -DVERSION=\"2.069\" -DXS_VERSION=\"2.069\" -fPIC "-I../.." -DNO_VIZ > -DZ_SOLO -DGZIP_OS_CODE=3 Zlib.c > cc1: error: /root/makelive/chatserver/chatserver//usr/include: Permission > denied > Makefile:350: recipe for target 'Zlib.o' failed > make[1]: *** [Zlib.o] Error 1 Well, runtime dependencies (which include libraries that you want to link to) must be present inside ROOT/ ... so not being able to read it is kinda counterproductive. Doesn't work like this. And please stop the sarcasm, it's not really helping.
All of the buildtime deps (that are what you need to have when building...) need to be installed in / anyways, and you shouldnt be involving the target root from the build at all (i guess being in roots home directory makes this one unreadable from the jailed build phase...), since my workaround is to buildpkgonly it without the root and then install the binary package to the alternative root, and it could be installed in any number of different roots, since those are just a temporary installation location, in runtime the root will obviously be /. Sorry about the snark (but it didnt feel welcome that you didnt even just try to see if it was real ...)
