Re: PostgreSQL 7.1.3 vs. gcc 2.95.4 and GNU libc 2.2.4

On Wed, Sep 12, 2001 at 01:16:17AM +0200, Peter Eisentraut wrote:
> tomas@fabula.de writes:
>
> > trying to compile PostgreSQL 7.1.3 (my system: Linux Debian-ish,
> > fairly new Gnu libc (where I think the problem resides):
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For once, my gut feeling was right.

> I have installed a fix for this in the development sources; I understand
> that you were able to fix this yourself.

Yes, I'm a happy camper.

> The more interesting question is why it's trying to use on_exit() when it
> should be using atexit().  If you're interested, you can try to look
> through config.log to see what's happening with the atexit test.

Stupid as it may sound, I lost my atexit()  ;-)

Watch this:

|  slon:/home/spu > vim blub.c
|
|  --( blub.c )---------------------------
|  #include <stdio.h>
|  #include <stdlib.h>
|
|  void scream(void)
|  {
|    fprintf(stderr, "AAAARRRGH!\n");
|  }
|
|  int main(int argc, char *argv[])
|  {
|    atexit(scream);
|  }
|  ---------------------------------------
|
|  slon:/home/spu > make blub
|  cc     blub.c   -o blub
|  /tmp/ccmhreih.o: In function `main':
|  /tmp/ccmhreih.o(.text+0x2f): undefined reference to `atexit'
|  collect2: ld returned 1 exit status
|  make: *** [blub] Error 1
|  slon:/home/spu >

So I think PostgreSQL's configure is not to blame for not finding it;
I think it's rather my gcc/libc combination. I guess it's a lesson
to distribution packagers: upgrading a libc is harder than it even
looks.

Do you think I should file a bug with Debian?
They seem to have noticed already (the proposed fix was to upgrade
gcc/cpp, which I did. Before that compile didn't work at all --
I guess I hadn't either atexit() nor on_exit() then).

Thanks a lot
-- tomas