Re: [HACKERS] problem compiling 6.5 cvs (Linux, gcc 2.7.2, egcs 1.12)

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] problem compiling 6.5 cvs (Linux, gcc 2.7.2, egcs 1.12)
Date: 1999-05-11 15:31:19
Message-ID: Pine.GSO.3.96.SK.990511192004.3568E-100000@ra
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 11 May 1999, Tom Lane wrote:

> Date: Tue, 11 May 1999 10:35:55 -0400
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: gjerde(at)icebox(dot)org
> Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgreSQL(dot)org
> Subject: Re: [HACKERS] problem compiling 6.5 cvs (Linux, gcc 2.7.2, egcs 1.12)
>
> gjerde(at)icebox(dot)org writes:
> > But with redhat 6.0(egcs 1.1.2, glibc 2.1) I'm having one problem.
> > psql doesn't compile :)
> > psql.c:152: initializer element is not constant
> > which is
> > static FILE * cur_cmd_source = stdin;
>
> > I don't believe I have ever seen that error, and I don't know why it has
> > problems with that line.
>
> You have a broken compiler IMHO --- on any reasonable system, stdin
> should be a load-time constant address, and load-time constants are
> required by the standard to be acceptable initializers for statics.
> Either stdin is defined in a very peculiar way, or the compiler is
> incapable of handling non-compile-time-constant initializers. In
> either case it's gonna fail on a lot more things than just Postgres.
>
> However, it's easy enough to work around it (as you noted in your
> followup). I'll commit the change.
>

I have no problem with that specific case, but I had a problem
with compiling latest cvs which arises from wrong configure suggestion -
I had to make change in config.h
#define HAVE_GETTIMEOFDAY_2_ARGS 1
to compile cvs sources. This happens only recently because
I've never seen this problem.

>
> Re Oleg's original complaint: I'm not seeing any problem with a
> CVS fileset that I pulled afresh on Saturday morning. I think
> he somehow got a corrupted copy...

I too, at home :-) At work I still have sporadical errors in compiling
on one of my machine (Linux 2.0.36, libc5 5.0.46, egcs 1.12 -release).
On another machine (Linux 2.0.36, gcc 2.7.2.3, ibc5 5.0.46) after
trivial change in config.h (see above) I got fully workable postgres :-)
All sources were identical. I did resync of cvs. So, actually
I have weird problem only on one machine and I'll see what were changed
in my setup.

>
> regards, tom lane
>

_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 1999-05-11 15:40:38 Re: [HACKERS] SERIAL + PRIMARY KEY = redundant indexes
Previous Message Bruce Momjian 1999-05-11 15:21:48 Re: [HACKERS] Re: [SQL] plpgsql error