Re: [alpine-devel] Issue with abuild on aports github build
I do my builds from /home/tim
the built-in abuild results in the same error message on my system
however running the abuild from my local git clone for like
Now that I think of it I should do a diff between my git version of abuild
and the local system abuild.
On Thu, Mar 28, 2019, 8:01 AM Natanael Copa, <ncopa_at_alpinelinux.org> wrote:
> On Wed, 27 Mar 2019 20:05:01 -0300
> Timothy Legge <timlegge_at_gmail.com> wrote:
> > Hi
> > I pushed a pull request https://github.com/alpinelinux/aports/pull/6851
> > perlmagic. The build works on my development box if I use abuild from
> > current https://github.com/alpinelinux/abuild master.
> > If I use the version of abuild included on 3.8.4 I it fails with
> > >>> ERROR: perlmagick*: Has /home/... in rpath
> This is a check that there should be no references to /home in the
> binaries. Binaries should not be told to look for shared libs in any
> place under /home.
> What probably happened here is that build script will set RPATH to look
> for shared libs in the build tree, most likely to be able to run test
> suite or similar.
> My guess is that this does not happen on your local machine because you
> don't run your build from /home.
> You can find the offending binaries with: scanelf --recursive --rpath
> As a side note, I think we may need extend the test to also look
> for /tmp and /var/tmp or any place that users may have write access too.
> > >>> ERROR: perlmagick*: prepare_package failed
> > >>> ERROR: perlmagick: all failed
> > This is the same error that shows up in github after the pull request
> > continuous-integration/drone/pr * Build is failing
> > continuous-integration/travis-ci/pr * The Travis CI build failed
> > However the current git version of abuild works without any errors. Any
> > thoughts?
> > Tim
Received on Thu Mar 28 2019 - 08:43:06 UTC