-- pica * Buck Evan <buck_at_yelp.com> [20151014 02:51]: > The packaging system I'm targeting (pypi wheels =X) are built binaries that > are relocated arbitrarily, so the "run-time installation path" is entirely > unknown at compile time. > > I know that's weird. > > Making everything fully static makes everything but this one bit work > though. > As a nasty hack, --enable-tai-clock seems like it will disable the use of > leapsecs.dat. > > On Tue, Oct 13, 2015 at 5:39 PM, Laurent Bercot <ska-skaware_at_skarnet.org> > wrote: > > > On 14/10/2015 01:58, Buck Evan wrote: > > > >> > >> open("/tmp/pip-build-qcZXTx/s6/build/temp.linux-x86_64-2.7/etc/leapsecs.dat", > >> O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such file or directory) > >> > >> That is indeed where the leapsecs.dat file lived when the binary was > >> compiled, but no longer. > >> > >> I don't know whether this is meant to be a supported use case or not. > >> Regardless, can any of you all think of a workaround I can use, short of > >> knowing the installation path at compile time? > >> > > > > You should always give ./configure (for skalibs and other packages) the > > *run-time* installation paths. If you want to install the packages into > > a staging directory, use the DESTDIR make variable. In your case, for > > instance: > > > > ./configure # without --prefix: leapsecs.dat will be searched in /etc > > make > > make DESTDIR=/tmp/pip-build-qcZXTx/s6/build/temp.linux-x86_64-2.7/ install > > > > Your automated build system should give you an environment variable > > you can use to define your DESTDIR. > > > > -- > > Laurent > > > > -- picaReceived on Wed Oct 14 2015 - 09:37:04 UTC
This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:38:49 UTC