12-08-2004 Perşembe günü saat 22:27 sularında, Tom Lane dedi ki:
> ntufar <[EMAIL PROTECTED]> writes:
> > I attached a diff of fix that adds LANG=C; before call to $(FLEX).
> > Fixes the problem here but I don't know if adding environment variable
> > assignment like this is appropriate. I am not too fluent in PostgreSQL
> > build environment and do not know where one can put a global deffinition
> > you are talking below.
> 
> Um, the attachment was unreadable :-( but I get the idea.

Something to do with my mail provider, sorry.
in file src/pl/plpgsql/src/Makefile:
        LANG=C;$(FLEX) $(FLEXFLAGS) -Pplpgsql_base_yy -o'$@' $<
instead of
        $(FLEX) $(FLEXFLAGS) -Pplpgsql_base_yy -o'$@' $<

> 
> As for the global solution, I was wondering if it would work to put
> "LANG=C" right inside the definition of $(FLEX).  That would ensure
> the right behavior from all our flex builds without unnecessarily
> messing up people's build environments otherwise.  I don't know however
> whether this would parse properly.

The only thing that comest in mind is that it may break Win32 port. 
Can someone comment on this?

> 
>                       regards, tom lane

Regards,
Nicolai Tufar


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to