Re: Autoconf code

> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey(at)fmonkey(dot)net]
> Sent: 13 May 2003 21:41
> To: Dave Page
> Cc: Andreas Pflug; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Autoconf code
>
>
> It turns out the the real problem here is the "-static" flag to g++
> (well, actually to ld). On my redhat system, at least, this causes a
> list of undefined symbols that I can't even begin to track down.
> Removing the flag causes the program to compile fine. I
> would just say
> to any developer that if their system allows them to build with the
> "-static" flag, then you can use it by changing:
>
> LDFLAGS = @LDFLAGS@ -lpq
>
> in Makefile.in to:
>
> LDFLAGS = -static @LDFLAGS@ -lpq

The latest version from CVS (I don't know if Andreas included your
latest update yet) seems to work, and includes --static and
--static-libgcc. How easy is it to only put those in if --static is
specified to configure? I guess it would also require the -static to be
taken out of the wx_config command line.

> Try it on your system and see what happens. Incidentally,
> the "correct"
> way to compile in a new library is to use -l<lib>, not to
> list the full
> library. So you should use -lcrypt instead of
> /usr/lib/libcrypt.a. Not
> that it matters. At least it *shouldn't*. :)

Yeah, I tried that first but it didn't like it. Must have been a typo or
something.

Regards, Dave.