public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Abrahamsson <daniel.abrahamsson@prover.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: gcc -pg broken after cygwin update?
Date: Wed, 7 Dec 2022 08:58:15 +0000	[thread overview]
Message-ID: <AS8PR08MB6936BAD1D7274720E4449505E91A9@AS8PR08MB6936.eurprd08.prod.outlook.com> (raw)

Hi,

This morning I updated cygwin, and after that gcc started producing errors like this:

>  gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE -c -o ../obj/<somefile>.o <somefile>.c
> gcc -o ../bin/<mybin> ../obj/<somefile>.o -pg
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: ../obj/<somefile>.o: in function `exit_eval_failure':
/home/daab/dev/someproj/src/<somefile>.c:17: undefined reference to `__fentry__'

If I drop the "pg" flags from the compilation and linking stages, everything works.

I typically update cygwin packages once per week, but now it has been maybe a month since I last updated. As far as I can tell from the cygwin-announce archives, there has not been any gcc updates in that period, but I do note that cygwin itself has been updated. Could that be related?

Regards,
Daniel

             reply	other threads:[~2022-12-07  8:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:58 Daniel Abrahamsson [this message]
2022-12-07 11:50 ` Corinna Vinschen
2022-12-07 12:40   ` Corinna Vinschen
2022-12-07 15:05     ` Daniel Abrahamsson
2022-12-07 15:09       ` Corinna Vinschen
2022-12-07 14:47   ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-07 15:07     ` Corinna Vinschen
2022-12-07 17:59       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08  9:40         ` Corinna Vinschen
2022-12-08 14:47           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08 15:32             ` Corinna Vinschen
2022-12-08 16:02               ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08 16:06                 ` Corinna Vinschen

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=AS8PR08MB6936BAD1D7274720E4449505E91A9@AS8PR08MB6936.eurprd08.prod.outlook.com \
    --to=daniel.abrahamsson@prover.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).