public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: ASSI <Stromeko@nexgo.de>
Cc: cygwin@cygwin.com
Subject: Re: how to "re-enable" perl after 5.32 install; how to reinstall all perl-mods?
Date: Wed, 02 Jun 2021 12:05:02 -0700	[thread overview]
Message-ID: <60B7D65E.6040206@tlinx.org> (raw)
In-Reply-To: <87wnrcg6m3.fsf@Otto.invalid>

On 2021/06/01 22:47, ASSI wrote:
> L A Walsh writes:
>   
>> updated cygwin and it reinstalled a new version of perl,
>> but when I try to run any perl progs nothing runs (see below).
>>
>> So I'd like to try to reinstall all the cygwin
>> perl-mods that I have installed.
>>     
>
> You didn't say how you updated Cygwin, but if you used setup then it
> already did exactly that.
>   
----
    Why would it have reinstalled all of the modules it just
installed?

    I need to _RE_-install (to make sure all of the existing
modules correspond to what was downloaded by the 5.32 update.

I have possible doubts as to their integrity.
>   
>> How can I select "all" among the perl mods? and install?
>>
>> I can select for only the "installed" perl mods, but how can
>> I tell it to reinstall all of them?
>>     
>
> I'm not sure I understand your question, but how would you re-install a
> not installed module?
>   
----
    I wanted to re-install all of the **installed** modules to verify
integrity.

>   
>> According to /etc/setup, there are about 202 modules that need
>> to be reinstalled, but I don't see howto tell setup to re-install
>> all the "installed" modules (so I can be sure they are all "refreshed".
>>     
>
> Again, they already should be.
>   
---
    Not necessarily iff I'm getting coredumps/missing
modules from my existing perl programs. 
>   
>> Thanks
>>
>> (errors from 2 of my local perl progs, "pcalc" and "dedup")
>> and trying cpan....which also doesn't work. :-(
>>
>>
>>
>>     
>>>  pcalc
>>>       
>> Segmentation fault (core dumped)
>>     
>
> Well, I'm afraid I can't help you with an error so non-specific.
>   
---
    Yeah...
>> Signal SEGV at
>> /usr/local/lib/perl5/site_perl/5.32/x86_64-cygwin-threads/Term/Size.pm 
>> line 14.
>>     
> None of the stuff in /usr/local/ comes from Cygwin, that was all put
> there by yourself.  How about you move that away first?
>   
> So your ExtUtils::MakeMaker installation seems incomplete, you need to
> install the perl-ExtUtils-MakeMaker package at least.
>
> Yeah...
>   
Yeah, I had a bunch of modules in the previous 5.30 tree from
'site' that didn't get remade and I didn't know perl 5.32
was going to cause so many problems that I couldn't run most
of the stuff I had.

On linux I had backups in the worst case and could restore
a perl dir to capture all the modules I would need to recompile
from cpan, but on windows, don't have a good backup program since
MS removed MSbackup in Win7, so people couldn't backup binary
programs (except via image restores).  Grr.

I think that the problem I have in Cygwin-setup is it is
difficult to 'keep' an older binary install from something like perl
as one has to go through and 'keep' every compat module that
is installed for perl along the way every time you run setup.

Cygwin really needs to use something like rpm for POSIX-compatible
package management and only use setup for the cygwin-binaries
that need to be installed outside of
setup.

Then cygwin could use all the package management utils
from linux (RH, Suse, et al.) that would allow more flexible
local package management.

Rt. now have to figure out how to make POSIX::RT::Semaphore
work in new perl...only emphasizing why perl is falling out of
favor as a devel. env.  *sigh*...




      reply	other threads:[~2021-06-02 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  2:57 L A Walsh
2021-06-02  4:32 ` Brian Inglis
2021-06-02 19:04   ` L A Walsh
2021-06-02  5:47 ` ASSI
2021-06-02 19:05   ` L A Walsh [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=60B7D65E.6040206@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=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).