public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Fergus" <fergus@bonhard.uklinux.net>
To: <cygwin@cygwin.com>
Cc: "'Fergus'" <fergus@bonhard.uklinux.net>
Subject: RE: readline in Cygwin64?
Date: Mon, 03 Dec 2018 07:05:00 -0000	[thread overview]
Message-ID: <000301d48ad6$9a8021f0$cf8065d0$@bonhard.uklinux.net> (raw)
In-Reply-To: <000e01d48a76$621a45d0$264ed170$@bonhard.uklinux.net>

>> Just installed Cygwin64. Beautiful.
>> However, I need to build an executable. In Cygwin32 the build proceeds
>> without exception but in Cygwin64 two error msgs are generated during the
>> attempt:
>> 1)	fatal error: readline/readline.h: No such file or directory
>> 2)	cannot find -lreadline
>> Both platforms Cygwin32(64) are identically bespoke and are constructed
>> using the command
>> setup-x86(_64).exe -P <blah>,readline,<blah>
>> In Cygwin32 this results in the creation of all 3 files
>> /usr/include/readline/readline.h
>> /usr/lib/libreadline.a

> Cygwin32 has an obsoletion package for "readline" that pulls in the
> development headers as the old package had everything bundled.  On
> Cygwin64 that readline package never existed, so you'll need
> libreadline-devel.

>> /usr/lib/libreadline.dll.a
>> but none of these are created in Cygwin64. This is what breaks the build
of
>> the executable required.
>> (Possibly it is another element of <blah> that has this consequence for
>> Cygwin32, but whatever the trigger there is the same lack in Cygwin64.)
>> Can these necessary components be recovered in Cygwin64 by some amendment
to
>> the "setup -P .. .." instruction?

> cygcheck -p libreadline.dll.a

Just brilliant. Solved all.
Thank you.


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

      parent reply	other threads:[~2018-12-03  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 19:36 Fergus
2018-12-02 20:27 ` Achim Gratz
2018-12-03  7:05 ` Fergus [this message]

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='000301d48ad6$9a8021f0$cf8065d0$@bonhard.uklinux.net' \
    --to=fergus@bonhard.uklinux.net \
    --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).