Skip site navigation (1) Skip section navigation (2)

Re: BUG #6166: configure from source fails with 'This platform is not thread-safe.' but was actually /tmp perms

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alex Soto <apsoto(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6166: configure from source fails with 'This platform is not thread-safe.' but was actually /tmp perms
Date: 2011-08-20 15:20:55
Message-ID: 201108201520.p7KFKtA11188@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Alex Soto <apsoto(at)gmail(dot)com> writes:
> > Here's the section in the config.log in case it makes a difference
> 
> > configure:28808: ./conftest
> > Could not create file in /tmp or
> > Could not generate failure for create file in /tmp **
> > exiting
> > configure:28812: $? = 1
> > configure: program exited with status 1
> 
> [ greps... ]  Oh, that error is coming from src/test/thread/thread_test.c.
> 
> I wonder why we have that trying to write to /tmp at all, when all the
> other transient junk generated by configure is in the current directory.
> Bruce, do you have a good reason for doing it that way?

No idea --- using the current directory is probably best.

> (The error message seems to be suffering from a bad case of copy-and-
> paste-itis, too.)

OK, let me see if I can fix this.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

pgsql-bugs by date

Next:From: Robert HopekDate: 2011-08-20 15:31:15
Subject: BUG #6171: Sockets Issue
Previous:From: Daniel FarinaDate: 2011-08-20 00:39:58
Subject: BUG #6170: hot standby wedging on full-WAL disk

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group