From: Mario Mattl <mario.mattl1@inode.at>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: WG: [UNVERIFIED SENDER]Re: Cygwin latest: grep and other self-compiled Cygwin-programs are crashing
Date: Tue, 8 Feb 2022 09:43:08 +0100 (CET) [thread overview]
Message-ID: <906245968.1727862.1644309788282@webmail.mymagenta.at> (raw)
In-Reply-To: <d958864a3e524a40b47f3049abc57465@frims060.wamas.com>
> -----Ursprüngliche Nachricht-----
> Von: Cygwin <cygwin-bounces+mario.mattl=ssi-schaefer.com@cygwin.com> Im Auftrag von ASSI
> Gesendet: Dienstag, 8. Februar 2022 07:09
> An: cygwin@cygwin.com
> Betreff: [UNVERIFIED SENDER]Re: Cygwin latest: grep and other self-compiled Cygwin-programs are crashing
>
> CAUTION: This email originated from outside SSI SCHAEFER Group. Do not click or open attachments unless you recognise the sender and know the content is safe.
>
>
>
> Mario Mario.mattl2@inode.at writes:
> > grep-3.7-2 from your GIT-repo
> > and compiled using "cygport"
> >
> > The linked binary grep.exe crashes
>
> Either update gnulib (or at least threadlib.m4) or add
>
> export gl_cv_have_weak=no
>
Yes. Setting this environment helps to solve the issue.
Tested with packages "grep" and "diffutils"
> to the cygport (or set it as an environment variable during configure).
>
> > Maybe the newer binutils require additional compiler flags, those haven't been provided yet?
>
> The newer binutils changed they way weak symbols (which are not available for non-ELF platforms) are treated for PE/PEP object files and that triggered a latent bug in how gnulib tested for their usability.
> The binutils issue is still under investigation, I expect that the next release will have a fix.
>
Thank you for your really helpful hint and the explanation.
Looking forward to the upcoming binutil release....
Regards, Mario
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Wavetables for the Terratec KOMPLEXER:
> http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
prev parent reply other threads:[~2022-02-08 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0a45073e2ce940309b82d74f3baa667a@frims060.wamas.com>
[not found] ` <97de4ae40364445d92e8b8ed682890d6@frims060.wamas.com>
2022-02-07 20:33 ` Mario Mario.mattl2@inode.at
2022-02-07 22:37 ` Adam Dinwoodie
2022-02-08 6:08 ` ASSI
[not found] ` <d958864a3e524a40b47f3049abc57465@frims060.wamas.com>
2022-02-08 8:43 ` Mario Mattl [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=906245968.1727862.1644309788282@webmail.mymagenta.at \
--to=mario.mattl1@inode.at \
--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).