Re: list_head naming conflict gcc 4.2/perl/solaris

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: list_head naming conflict gcc 4.2/perl/solaris
Date: 2009-06-01 20:09:36
Message-ID: 23415.1243886976@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> My idea is to rename list_head to pg_list_head (and other functions analogously) to avoid name conflict.

There is zero chance of that happening. We have thousands of references
to those functions in the core code, and who knows how many more in
third-party code we don't control.

What is <sys/list.h>, and why is it being imported by the Perl headers?
Can we do something like "#define list_head solaris_list_head" around
the problematic #include? (Which one is that, anyway?)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-06-01 20:17:23 Re: User-facing aspects of serializable transactions
Previous Message Magnus Hagander 2009-06-01 20:08:16 Re: It's June 1; do you know where your release is?