public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Cygwin latest: grep and other self-compiled Cygwin-programs are crashing
Date: Tue, 08 Feb 2022 07:08:36 +0100	[thread overview]
Message-ID: <877da5ao0r.fsf@Otto.invalid> (raw)
In-Reply-To: <172810776.1509902.1644265991761@webmail.mymagenta.at> (Mario Mario mattl2's message of "Mon, 7 Feb 2022 21:33:11 +0100 (CET)")

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

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.


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

  parent reply	other threads:[~2022-02-08  6:08 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 [this message]
     [not found]       ` <d958864a3e524a40b47f3049abc57465@frims060.wamas.com>
2022-02-08  8:43         ` WG: [UNVERIFIED SENDER]Re: " Mario Mattl

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=877da5ao0r.fsf@Otto.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).