On Tue, 7 Jan 2003, Tom Lane wrote:
> Apparently, our configure script thinks you have getopt_long(), but you
> really don't. Can you look into the situation and figure out why
> configure is confused?
>
> It surprises me that this would happen when 7.2 worked okay --- I don't
> think we changed that configure test since 7.2. Are you sure nothing
> changed on your machine since you last built 7.2?
Yes, I'm sure. This is what happens when I run configure with the 7.2.3 source:
root@dev# ./configure --with-perl --enable-syslog --with-maxbackends=256
--with-libraries=/usr/lib:/usr/local/lib/:/usr/local/lib/lpe | grep -i getopt
checking for getopt.h... no
checking for getopt_long... no
And this is with 7.3.1 (run several minutes later on the same machine):
root@dev# !./conf
./configure --with-perl --enable-syslog --with-maxbackends=256
--with-libraries=/usr/lib:/usr/local/lib/:/usr/local/lib/lpe | grep -i getopt
checking for library containing getopt_long... -lgnugetopt
checking getopt.h usability... no
checking getopt.h presence... no
checking for getopt.h... no
checking for getopt_long... yes
This is from config.log (in the 7.3.1 source):
configure:9866: gcc -o conftest -pipe -L/usr/lib -L/usr/local/lib/
-L/usr/local/lib/lpe conftest.c -lz -lreadline -lcrypt -lgnugetopt -lcompat -lm
-lutil >&5
configure:9869: $? = 0
configure:9872: test -s conftest
configure:9875: $? = 0
configure:9885: result: yes
I have confirmed the conftest.c which tests getopt_long in that section of the
code does indeed complie without errors.
I'm a bit stumped as to what to check next.
-Dan