From: Nicholas Wourms <nwourms@yahoo.com>
To: "Harig, Mark A." <maharig@idirect.net>, cygwin@cygwin.com
Subject: RE: autoconf issues [often when upgrading from 2.13->2.53a]
Date: Tue, 23 Jul 2002 13:43:00 -0000 [thread overview]
Message-ID: <20020723185036.62012.qmail@web21010.mail.yahoo.com> (raw)
In-Reply-To: <BADF3C947A1BD54FBA75C70C241B0B9E10AA6A@ex02.idirect.net>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
--- "Harig, Mark A." <maharig@idirect.net> wrote:
> Yes, autoconf uses sed many, many times. What is often possible is
> to
> narrow down which one by searching in 'configure' for the text
> message
> that 'configure' generates at the time that the script hangs, e.g.,
> "Checking for GNU c compiler..." Sometimes you may need to do this
> several times. The better approach is to have a firm understanding
> of
> the layers of abstraction that autoconf builds on top of m4 and
> automake
> builds on top of autoconf, etc. but we're trying the
> "brute-force-examine-the-assembly-language" approach. 'config.log'
> is
> sometimes helpful in providing clues about what might be causing
> the
> problem.
Mark,
I have attached a log of the configure session with set -xv. Don't
worry, it bombs out early, so it isn't that big. I'll do the same
procedure on win2k, if you want. The offending checkpoint is:
-enable-* | --enable-*)
ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
{ echo "$as_me: error: invalid feature name: $ac_feature" >&2
{ (exit 1); exit 1; }; }
ac_feature=`echo $ac_feature | sed 's/-/_/g'`
case $ac_option in
*=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
*) ac_optarg=yes ;;
esac
eval "enable_$ac_feature='$ac_optarg'" ;;
The options I'm passing are:
CFLAGS=-O2 \
LDFLAGS= \
CC=gcc-2 \
CXX=g++-2 \
../dist/configure --target=i686-pc-cygwin --prefix=/usr
--exec-prefix=/usr --sysconfdir=/etc --bindir=/usr/bin
--libdir=/usr/lib --includedir=/usr/include/db3.1
--datadir=/usr/share '--libexecdir=${sbindir}' --localstatedir=/var
'--program-transform-name=s,^db_,db3.1_,' --enable-posixmutexes
--enable-dynamic --enable-cxx --enable-compat185 --disable-test
If you (or anyone else) are interested in seeing what it does on your
system, you can grab the self-contained build system at:
http://today.clemson.edu/temp/db-3.1.17-1-src.tar.bz2
Untar to a temporary dir and run the buildscript like so:
./db-3.1.17-1.sh prep
Then edit the configure script [db-3.1.17/dist/configure] adding your
-xv flags to line 1 and line 155 [exec "$CONFIG_SHELL" "-xv"]:
Then run:
./db-3.1.17-1.sh conf
It should run fine on win2k, but winme/9x it doesn't. I'm going to
try and examine it some more, but I thought I'd bring you in on it.
Cheers,
Nicholas
__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com
[-- Attachment #2: configure.log.bz2 --]
[-- Type: application/octet-stream, Size: 9718 bytes --]
[-- Attachment #3: Type: text/plain, Size: 214 bytes --]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-07-23 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 11:50 Harig, Mark A.
2002-07-23 13:43 ` Nicholas Wourms [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 13:56 Harig, Mark A.
2002-07-23 21:14 Harig, Mark A.
2002-07-23 19:59 Harig, Mark A.
2002-07-23 21:15 ` Nicholas Wourms
2002-07-22 17:46 Harig, Mark A.
2002-07-22 23:01 ` Nicholas Wourms
2002-07-22 16:41 Harig, Mark A.
2002-07-22 17:00 ` Nicholas Wourms
2002-07-20 15:21 Nicholas Wourms
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=20020723185036.62012.qmail@web21010.mail.yahoo.com \
--to=nwourms@yahoo.com \
--cc=cygwin@cygwin.com \
--cc=maharig@idirect.net \
/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).