Nels Frazier <hellkite500@gmail.com> writes:
> So I checked out ~/.ccache, and there was no such file/directory in my home
> folder.
Hm, ccache RPM not installed then?
> I tried configuring/building from both bash and tcsh, neither worked. This
> is really strange, since I was able to build successfully on a RHEL 6.7
> machine using:
> GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
> GNU Make 3.8.1
> gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
> But on the RHEL 6.4 machine using:
> GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
> GNU Make 3.81
> gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
> the build fails. I even tried using a different compiler version (gcc
> (GCC) 4.7.1) to no avail.
Don't know what to tell you. RHEL 6.4 was current during 2013, which is
the same year that 9.2 was our current release, and we would certainly
have noticed if there was any widespread (or even not so widespread)
build failure on that combination. Also, the code in question hasn't
changed in quite some time, so the issue would affect other PG branches
besides 9.2, making it even less likely that we'd have missed a problem.
I have to think that one or another component of your toolchain is
nonstandard or corrupted, but it's hard to say more than that.
> Should it be ok to proceed using the patch to get a build completed?
Well, Postgres isn't going to care. Applications that make use of the
output of pg_config might be unhappy with the lack of quotes, although
most likely it wouldn't matter as long as there's not spaces or quotes
in your path names.
regards, tom lane