public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Perl Illegal Instruction
Date: Tue, 16 Jul 2019 05:37:00 -0000	[thread overview]
Message-ID: <87zhleee0j.fsf@Rainer.invalid> (raw)
In-Reply-To: <802fce1aec7fcce7b453fafc36b0b310@plebeian.com> (Chris Wagner's	message of "Mon, 15 Jul 2019 16:36:01 -0400")

Chris Wagner writes:
> Of course it's up to date...

I'll let that stand, although I've seen sufficiently many Win7 systems
lately to be wary of any such statement.

> That is not BLODA.  That's the standard list of libraries.  I changed
> nothing; it worked yesterday; today it didn't.  Every other Cygwin
> executable I've tried works without problem.  I even tried
> reextracting the files from perl_base.

So again, something changed and you have no idea what.  If you rule out
a hardware error (memory most likely if it always strikes at the same
place) and you didn't actively made changes (not limited to Cygwin),
then the culprit must by definition be some change that occured
elsewhere in the system.  If it was some automatic update there might
be a restore point pertaining to those changes and certainly something
in the event logs.

>>> $ uname -a
>>> CYGWIN_NT-6.1 applejack 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64
>>> Cygwin
>>
>> A current Cygwin...
>>
>>> $ cygcheck -c perl perl_base
>>> Cygwin Package Information
>>> Package              Version        Status
>>> perl                 5.22.4-1       OK
>>> perl_base            5.22.4-1       OK
>>
>> combined with an outdated Perl (Cygwin is at 5.26.3 now).  What are you
>> trying to achieve?  Please fully update Cygwin after checking your
>> system.  Also, you might want to clean up your PATH a bit.
>
> I'm not going to recompile all my modules and rework the new lib paths
> until I have a really good reason to.

As they say, "you break it, you get to keep the broken pieces".  Trying
to lock down part(s) of Cygwin is a losing proposition unless you are
building everything yourself, at which point building a bunch of Perl
modules after an update ceases to be an issue anyway.

> I'ld be happy to run any other diagnostic command anyone can think of.

Well, as I said, try to start with some halfway sane PATH perhaps? In
other words, something like

env PATH=/bin perl --version

for starters.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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:[~2019-07-16  5:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 17:57 Chris Wagner
2019-07-15 18:50 ` Andrey Repin
2019-07-15 19:46 ` Achim Gratz
2019-07-15 19:58   ` Achim Gratz
2019-07-15 20:36   ` Chris Wagner
2019-07-15 21:01     ` Vince Rice
2019-07-16  5:37     ` Achim Gratz [this message]
2019-08-15 16:22       ` Chris Wagner

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=87zhleee0j.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).