[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Aspell-user] can't compile aspell 0.60 under cygwin
From: |
Randal Walser |
Subject: |
Re: [Aspell-user] can't compile aspell 0.60 under cygwin |
Date: |
Mon, 27 Sep 2004 05:51:19 -0700 |
>It turns out that libtool needs the -no-undefined flag. Try running
>configure with:
>
> ./configure LDFLAGS=-no-undefined ...
>
>You will also need to remove the cygwin hack in common/iostream.hpp.
Kevin,
Thanks very much for looking into this. Unfortunately, the LDFLAGS
trick isn't working for me, as g++ reports that -no-defined is an
unrecognized option. I notice that ld version 2.15.91 (the latest
from cygwin, which accompanies g++ v. 3.3.3) has a "--no-defined"
(with a two-dash prefix), but when I try that as LDFLAGS' value, g++
sees it as "-fno-defined" and then fails. Somehow, the "--" is
transliterated to "-f". I'm not sure if that's happening in your
configure script, or where, but for the moment I've run out of time to
investigate further.
Here's the relevant fragment from config.log:
----------------------------------------------------------------------
gcc version 3.3.3 (cygwin special)
configure:2280: $? = 0
configure:2282: g++ -V 3.3.3 </dev/null >&5
i686-pc-cygwin-gcc-3.3.3: no input files
configure:2285: $? = 1
configure:2308: checking for C++ compiler default output file name
configure:2311: g++ -no-undefined conftest.cc >&5
g++: unrecognized option `-no-undefined'
g++: installation problem, cannot exec
`/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/collect2.exe': Resource temporarily
unavailable
configure:2314: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "GNU Aspell"
| #define PACKAGE_TARNAME "aspell"
| #define PACKAGE_VERSION "0.60"
| #define PACKAGE_STRING "GNU Aspell 0.60"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "aspell"
| #define VERSION "0.60"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2353: error: C++ compiler cannot create executables
----------------------------------------------------------------------
Also, notice that I had to add a specific argument (3.3.3) for the g++
-V flag in configure. Otherwise, g++ reports "`-V' option must have
argument" and configure fails. This wasn't a problem with g++ version
3.2, so it appears there have been some changes to g++ that affect
your build procedure. I no longer have g++ version 3.2, so I can't
(easily) go back and ferret out the differences.
Again, thanks for looking into this, and for Aspell in general.
Version 0.50.3 is way cool enough :)
Randal