minor problem with detecting int64 in configure

From: t-ishii(at)sra(dot)co(dot)jp
To: hackers(at)postgreSQL(dot)org
Cc: t-ishii(at)srapc451(dot)sra(dot)co(dot)jp
Subject: minor problem with detecting int64 in configure
Date: 1998-08-24 03:51:36
Message-ID: 199808240351.MAA19646@srapc451.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have found a minor problem with current configure.in.

[AC_MSG_RESULT(yes) AC_DEFINE(HAVE_LONG_INT_64)],

this line produces something like:

echo "$ac_t""yes" 1>&6 cat >> confdefs.h <<\EOF

and would append garbage "yes cat" to confdefs.h. Of course the result
confdefs.h is not syntactically correct therefore following tests
using confdefs.h would all fail.
To avoid the problem, we could switch the order of AC_MSG_RESULT and
AC_DEFINE (see attached patch). This happend on my LinuxPPC box.
--
Tatsuo Ishii
t-ishii(at)sra(dot)co(dot)jp
-------------------------------------------------------------------
*** configure.in.orig Mon Aug 24 12:34:26 1998
--- configure.in Mon Aug 24 12:31:50 1998
***************
*** 596,602 ****
main() {
exit(! does_int64_work());
}],
! [AC_MSG_RESULT(yes) AC_DEFINE(HAVE_LONG_LONG_INT_64)],
AC_MSG_RESULT(no),
AC_MSG_RESULT(assuming not on target machine))

--- 596,602 ----
main() {
exit(! does_int64_work());
}],
! [AC_DEFINE(HAVE_LONG_LONG_INT_64) AC_MSG_RESULT(yes)],
AC_MSG_RESULT(no),
AC_MSG_RESULT(assuming not on target machine))

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-08-24 03:52:41 Re: [HACKERS] What I'm working on
Previous Message Bruce Momjian 1998-08-24 03:51:25 Re: [HACKERS] What I'm working on