[Slackbuilds-users] gdal SlackBuild fails

[Duncan Roe]

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:
> >> On Fri, Mar 03, 2017 at 12:19:09PM +0000, David Spencer wrote:
> >> > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything
> >> > > other than -j1). That's a snap diagnosis, I don't know what gdal even is.
> >> >
> >> > gdal already has 'make -j1' hard-coded, because it definitely fails
> >> > with multiple parallel make jobs.
> >> >
> >> > For some reason that I don't understand, on Duncan's system gcc is
> >> > being invoked through libtool.
> >> > The compilation explicitly has '-o
> >> > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that
> >> > file does not exist at the time the next command 'g++ -pthread -shared
> >> > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked.
> >> >
> >> > So this really does look like a multiple parallel make jobs failure.
> >> > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it somehow?
> >> > Are you on -current?
> >> > Do you have CC and/or CXX defined in the environment?
> >> > could you put your config.log on pastebin or somewhere similar?
> >> >
> >> Hi David,
> >>
> >> On 14.2 unpatched
> >>
> >> env has CC=gcc
> >>
> >> 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).
>
> Matteo

Hi Matteo,

I ran the build from a logged-in-as-root environment, as evidenced by:

> 22:00:11# echo $0
> -bash

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?

Cheers ... Duncan.