From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: missing file cyggc-1.dll
Date: Sun, 28 Jan 2018 14:20:00 -0000 [thread overview]
Message-ID: <5046043d-a655-edc0-eff2-a14fd257d145@SystematicSw.ab.ca> (raw)
In-Reply-To: <7edb3627-4cdf-a1fa-ff21-b492ee8aa8d6@gmail.com>
On 2018-01-28 01:20, Marco Atzeri wrote:
> On 27/01/2018 21:46, Brian Inglis wrote:
>> On 2018-01-27 13:16, U-BLASTER-6000\mtdew wrote:
>>> I ran into a small problem (for the gurus).
>>> I ran configure and the make. Make got hung with the following error.
>>> $ cygcheck /usr/bin/make.exe
> ...
>>> cygcheck: track_down: could not find cyggc-1.dll
>>> It appears that I have this installed in the package libgc-1 and
>>> libgc-devel. I am not sure why make cannot see this file. Is there a way
>>> so that I can trick it to find that library file?
>>
>> Check that /bin/cyggc-1.dll exists, its permissions are a+rx, and chmod those
>> permissions if not, or reinstall package libgc-devel.
>
> Ehm, libgc-devel does not contain it.
>
> So reinstall libgc1.
>
> see content on
> https://cygwin.com/packages/x86_64/libgc1/libgc1-7.6.0-2
Thinking install not reinstall - so as above - or both in case anything else is
missing. Can also run cygcheck -svr > cygcheck.out to check everything.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
prev parent reply other threads:[~2018-01-28 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 20:16 U-BLASTER-6000\mtdew
2018-01-27 20:47 ` Brian Inglis
2018-01-28 8:20 ` Marco Atzeri
2018-01-28 14:20 ` Brian Inglis [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=5046043d-a655-edc0-eff2-a14fd257d145@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).