From: "Harig, Mark A." <maharig@idirect.net>
To: "Nicholas Wourms" <nwourms@yahoo.com>, <cygwin@cygwin.com>
Subject: RE: autoconf issues [often when upgrading from 2.13->2.53a]
Date: Mon, 22 Jul 2002 16:41:00 -0000 [thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E40F118@ex02.idirect.net> (raw)
Have you tried downgrading to the stable tools (2.13) to see if the
problem is still occurring, or is that not an option (i.e, the
configure.in requires 2.53)?
I had a problem recently where it appeared that sed was running in an
infinite loop. When I downgraded to the stable tools, the problem
disappeared.
> -----Original Message-----
> From: Nicholas Wourms [mailto:nwourms@yahoo.com]
> Sent: Saturday, July 20, 2002 10:48 AM
> To: cygwin@cygwin.com
> Subject: autoconf issues [often when upgrading from 2.13->2.53a]
>
>
> Hi,
>
> I've been experiencing some strange problems with the autotools as of
> late. First, let me tell you what I have installed. I have
> updated to
> the latest version of all the autotools and wrapper scripts.
> I've been
> working on a few packages which required re-autotoolizing to
> the latest
> versions to support shared dll's. The problem is that
> lately, many of the
> packages get petulant when I try to pass options to them.
>
> For example:
> ./configure --prefix=/usr ... --enable-shared
>
> will return:
> shared: invalid feature name
>
> I've looked on google and I've check the mailing lists, but I
> can't seem
> to get a definitive answer on what might cause this to
> happen. I tried to
> follow the autotools script, but it isn't the easiest thing
> to unravel.
> To get around this, I have to manually edit the configure
> file and remove
> the 3 lines that do the validity test. I don't think this is
> the proper
> solution, in the long run. So, my hope is that someone has
> experienced
> this lately and can clue me in on a good way isolate what is
> causing this.
> I might note that this behaviour started happening after I
> upgraded to
> automake-1.6.2, but I can't say for sure that this is the cause of my
> woes. I wanted to atleast see if anyone else is aware of
> this on cygwin
> before I go posting to the autoconf list. Maybe I'm not thinking too
> clearly and have been working too hard on one of my packages,
> but this is
> driving me crazy. Any helpful pointers or references to some
> documentation I might have missed would be greatly appreciated.
>
> Cheers,
> Nicholas
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
>
> --
> 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/
>
>
--
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 reply other threads:[~2002-07-22 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 16:41 Harig, Mark A. [this message]
2002-07-22 17:00 ` Nicholas Wourms
-- 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-23 11:50 Harig, Mark A.
2002-07-23 13:43 ` Nicholas Wourms
2002-07-22 17:46 Harig, Mark A.
2002-07-22 23:01 ` 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=BADF3C947A1BD54FBA75C70C241B0B9E40F118@ex02.idirect.net \
--to=maharig@idirect.net \
--cc=cygwin@cygwin.com \
--cc=nwourms@yahoo.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).