From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Unable to extract GMP version information from gmp_version :mingw
Date: Sat, 24 Oct 2020 23:17:40 -0600 [thread overview]
Message-ID: <ee5c801b-b5a8-45d1-8dfe-c3c1194ce66d@SystematicSw.ab.ca> (raw)
In-Reply-To: <2111881895.3069057.1603601059475@mail.yahoo.com>
On 2020-10-24 22:44, Jim McNamara via Cygwin wrote:
> I am experimenting with mingW64 with cygwin.
> My ./configure looks like this:
> $ echo $LD_LIBRARY_PATHC:/cygwin/lib
> $ ./configure --prefix=/home/user/cobol-3.1-rc1 --host=x86_64-w64-mingw32
> checking for gmp... nochecking for libgmp... nochecking gmp.h usability... yeschecking gmp.h presence... yeschecking for gmp.h... yeschecking for gmp.h... (cached) yeschecking if linking against libgmp with "-lgmp" works... yeschecking matching GMP version... configure: error: Unable to extract GMP version information from gmp_version
> I installed the gmp package for mingw64. I went in and installed libgmp mingW64 package and the headers for in devel section of the cygwin installer.
> I have the file libgmp.dll.a in c:/cygwin/lib
> Please let me know if there is anything i can do to get past this error.
Please figure out how to copy and paste including line terminators, or paste
into an editor and reformat before pasting into email.
You should normally be building in a directory e.g build, separate from that in
which configure resides e.g.
$ mkdir build
$ cd build
$ ../src/configure ...
in which you should find config.log which should show all the details of all the
programs generated and run to check all the features required and all the
results from those runs.
I have found it useful if not necessary to install libgmp-devel with
mingw64-{x86_64,i686}-gmp, pkg-config with mingw64-{x86_64,i686}-pkg-config, and
similarly with other packages required for cross-builds.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-10-25 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2111881895.3069057.1603601059475.ref@mail.yahoo.com>
2020-10-25 4:44 ` Jim McNamara
2020-10-25 5:17 ` Brian Inglis [this message]
2020-10-25 8:00 ` Achim Gratz
2020-10-25 8:12 ` Fwd: " Jim McNamara
2020-10-25 9:05 ` Jim McNamara
[not found] <1593712335.3089083.1603612043638.ref@mail.yahoo.com>
2020-10-25 7:47 ` thanks Brian! MinGW/cygwin. Have a cool weekend :-) Jim McNamara
2020-10-25 16:19 ` Unable to extract GMP version information from gmp_version :mingw Brian Inglis
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=ee5c801b-b5a8-45d1-8dfe-c3c1194ce66d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).