public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: this must be a common problem, but repeated searching is not finding an answer
Date: Sat, 19 Mar 2022 11:57:53 -0600	[thread overview]
Message-ID: <79540473-1c96-9a9a-0c19-3c5ecded6b27@SystematicSw.ab.ca> (raw)

On Sat, 19 Mar 2022 08:12:15 -0700, Achim Gratz wrote:
> Clayton Cramer writes:
>> I installed everything from the setup program, but executing bc gives
>> "The code execution cannot proceed because readline4.dll was not
>> found.  Reinstalling the program may fix this problem."  From where do
>> I get readline4.dll?

> Cygwin's bc does not depend on this library and it would not give you
> this error message either.  I suggest you try "/usr/bin/bc" from a
> Cygwin shell and then think about what you want to have your PATH look
> like.

I wonder which setup program that was, and how your environment is set up?

That message is from a native Windows port of bc, installed under/by 
Mingw/64, Msys/2, Chocolatey or some other native Windows port installer 
that does not handle library dependencies. You would have to install 
that environment's readline library using their setup program.

If you have installed Cygwin, you must start it using (perhaps some 
minor variation of) the provided shortcuts, command files, or scripts, 
and ensure the Cygwin path is set with Cygwin /usr/bin/ near the start, 
possibly preceded by your own local script directory/-ies: e.g.

	$HOME/bin:/usr/local/bin:/usr/bin

-- 
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.]

             reply	other threads:[~2022-03-19 17:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 17:57 Brian Inglis [this message]
2022-03-19 18:15 ` Clayton Cramer
2022-03-19 18:23   ` Eliot Moss
2022-03-19 18:33     ` Clayton Cramer
2022-03-19 20:55       ` Eliot Moss
2022-03-19 21:51         ` Clayton Cramer
2022-03-19 23:18           ` Gary Johnson
2022-03-20 15:04             ` Clayton Cramer
2022-03-19 23:19           ` Eliot Moss
2022-03-19 23:24             ` Joel Rees
2022-03-20  2:20   ` clayton
  -- strict thread matches above, loose matches on Subject: below --
2022-03-19 14:49 Clayton Cramer
2022-03-19 15:11 ` Achim Gratz

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=79540473-1c96-9a9a-0c19-3c5ecded6b27@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).