public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Howard Chu <hyc@highlandsun.com>
To: cygwin@cygwin.com
Subject: Bash fails on BerkeleyDB configure
Date: Mon, 26 Nov 2007 15:15:00 -0000	[thread overview]
Message-ID: <474AB3A1.2050608@highlandsun.com> (raw)

I ran into this problem while trying to run the BerkeleyDB 4.6.21 configure 
script with current Cygwin installed on a Windows64 machine. (Windows 2003 
Server SP2 x86_64, using the Cygwin build of the x86_64-pc-mingw32 compiler 
from the mingw-64 project).

The script fails on a case statement. Pasting the case statement into a 
separate script by itself doesn't fail, so I can't send you a simple test 
case. But you can easily download the BerkeleyDB source code to reproduce the 
problem. The first failure starts at line 28024:

if test $ac_cv_type_u_int8_t = yes; then
   :
else

     case "1" in
     "$ac_cv_sizeof_unsigned_int")
         u_int8_decl="typedef unsigned int u_int8_t;";;
     "$ac_cv_sizeof_unsigned_char")
         u_int8_decl="typedef unsigned char u_int8_t;";;
     "$ac_cv_sizeof_unsigned_short")
         u_int8_decl="typedef unsigned short u_int8_t;";;
     "$ac_cv_sizeof_unsigned_long")
         u_int8_decl="typedef unsigned long u_int8_t;";;
     "$ac_cv_sizeof_unsigned_long_long")
         u_int8_decl="typedef unsigned long long u_int8_t;";;
     *)
         if test "" != "notfatal"; then
             { { echo "$as_me:$LINENO: error: No unsigned 1-byte integral 
type" >&5
echo "$as_me: error: No unsigned 1-byte integral type" >&2;}
    { (exit 1); exit 1; }; }
         fi;;
     esac
fi

ac_cv_sizeof_unsigned_int is defined to 4 by prior tests. Likewise,
ac_cv_sizeof_unsigned_char is 1
ac_cv_sizeof_unsigned_short is 2
ac_cv_sizeof_unsigned_long is 4
ac_cv_sizeof_unsigned_long_long is 8

The test fails with "No unsigned 1-byte integral type". The script exits at 
that point. Getting past this (by explicitly setting variables to bypass the 
test) just runs into another failure as the script uses the same construct to 
set a bunch of other type defs.

Let me know if you need any more info.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2007-11-26 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 15:15 Howard Chu [this message]
2007-11-26 15:56 ` Dave Korn
2007-12-06  1:22   ` Howard Chu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=474AB3A1.2050608@highlandsun.com \
    --to=hyc@highlandsun.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).