public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Wild <themiwi@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: UPX compressed setup-x86_64.exe crashes on Win10
Date: Mon, 21 Jan 2019 21:12:00 -0000	[thread overview]
Message-ID: <CAALQ5r=SDcAhQ-Su_ynew=QU=dNqTF511tjvFg3dsadgV52WNQ@mail.gmail.com> (raw)
In-Reply-To: <87h8e1vl97.fsf@Rainer.invalid>

On Mon, 21 Jan 2019, 20:55 Achim Gratz wrote:

> Michael Wild writes:
> > Thanks. I have very little hope of getting it whitelisted... Is UPX
> > compression really a necessity? Otherwise I'll have to resort to my
> custom
> > compiled versions.
>
> No, that's just so the download is smaller.  Which isn't the point if
> you've built it yourself anyway… you could decompress it if you really
> don't trust your own version or want to skip building it.
>

Interesting. Somehow I assumed that this was a one-way process. But how do
I bootstrap? Can I just use the download from upx.github.io? That'll be
what I try next then.

Michael

>

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

  reply	other threads:[~2019-01-21 21:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  8:03 Michael Wild
2019-01-21 17:19 ` Achim Gratz
2019-01-21 18:25   ` Michael Wild
2019-01-21 19:55     ` Achim Gratz
2019-01-21 21:12       ` Michael Wild [this message]
2019-01-22 16:53         ` Brian Inglis
2019-01-22 17:28           ` Michael Wild
2019-01-22 18:34             ` 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='CAALQ5r=SDcAhQ-Su_ynew=QU=dNqTF511tjvFg3dsadgV52WNQ@mail.gmail.com' \
    --to=themiwi@gmail.com \
    --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).