[Slackbuilds-users] SOLVED: gdal SlackBuild fails

Duncan Roe duncan_roe at acslink.net.au
Sat Mar 4 11:13:14 UTC 2017


On Sat, Mar 04, 2017 at 10:06:09PM +1100, Duncan Roe wrote:
> 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.
>
I removed CC=gcc from the environment and the SB ran to completion.

It's been in my .bashrc for years, will take it out.

Cheers ... Duncan.


More information about the SlackBuilds-users mailing list