Re: [rt.cpan.org #118053] Problem with packed perl archive for biber on 64-bit Cygwin

[email protected] ("Ken Brown via RT")
Newsgroups perl.par
Message-ID <[email protected]>
Mon Sep 26 09:51:06 2016: Request 118053 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: PAR-Packer
     Subject: Re: [rt.cpan.org #118053] Problem with packed perl archive for biber on 64-bit Cygwin
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=118053 >


On 9/26/2016 6:17 AM, Roderich Schupp via RT wrote:
> <URL: https://rt.cpan.org/Ticket/Display.html?id=118053 >
>
> Am 2016-09-25 13:37:42, [email protected] schrieb:
>> Actually, there's still one glitch.  If I run biber with no arguments,
>> it unpacks itself and gives me a usage message.  It also works fine if I
>> run 'biber --help'.  But if I give it a file as an argument (e.g.,
>> 'biber test.bcf') before the cache is created, it unpacks itself and
>> then hangs.  After I kill it, I can rerun it with no problem.
>
> Sorry, no clue. If "biber --help" works, then basically PAR::Packer's job
> is done (though there might still be missing files etc, but typically that
> doesn't result in a hang). Does this hang occur also on the machine
> where you packed biber?

It did originally, but I just repacked biber (which a slight change), 
and now I can't reproduce the problem anymore.  The change was to remove 
these two arguments from the invocation of pp:

   --link=/usr/bin/cygssp-0.dll
   --link=/usr/bin/cygcrypt-0.dll

The first is not needed because cygssp-0.dll is contained in a minimal 
Cygwin install, and the second is not needed now that cygcrypt-0.dll is 
embedded.

I'm not sure whether (or why) these changes made a difference, but in 
any case the problem seems to be gone.

Thanks for your help.

Ken
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.