[Slackbuilds-users] gdal SlackBuild fails
matteo.bernardini at gmail.com
Sat Mar 4 14:11:36 UTC 2017
2017-03-04 15:02 GMT+01:00 Duncan Roe <duncan_roe at acslink.net.au>:
> On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote:
>> 2017-03-04 12:06 GMT+01:00 Duncan Roe <duncan_roe at acslink.net.au>:
>> > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote:
>> >> Paste is http://pastebin.com/v4gXJbDr
>> > And, I did not override -j1. This pocessor does have 2 cores though.
>> Duncan, sorry, before anyone else asks: the paste above looks done
>> from your unprivilege used environment.
>> it could be there are no differences but maybe it's better if you post
>> the one you got from running the SlackBuild (you can take it directly
>> from the /tm/SBo/gdal-* directory) from the root environment (in which
>> you get by running "su -l" from your user shell).
> Hi Matteo,
> I ran the build from a logged-in-as-root environment, as evidenced by:
>> 22:00:11# echo $0
> I just do su but then immediately start a fresh xterm (with a pink background,
> so I know it's root); then exit from the su.
> What looks unprivileged in the paste?
in the paste you have these lines
these mean that you have executed just "su" and not "su -" (or "su
-l") so your root environment, not having being launched as a true
login shell, was polluted by user variables (see point 3 of the howto
you shouldn't run SBo's build scripts executing just "su".
More information about the SlackBuilds-users