public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Daniel Abrahamsson via Cygwin <cygwin@cygwin.com>
Subject: Re: gcc -pg broken after cygwin update?
Date: Wed, 7 Dec 2022 16:09:54 +0100	[thread overview]
Message-ID: <Y5CswuzdEwENyRBm@calimero.vinschen.de> (raw)
In-Reply-To: <AS8PR08MB6936034B363027E094E4F102E91A9@AS8PR08MB6936.eurprd08.prod.outlook.com>

On Dec  7 15:05, Daniel Abrahamsson via Cygwin wrote:
> > On Dec  7 12:50, Corinna Vinschen via Cygwin wrote:
> > > On Dec  7 08:58, Daniel Abrahamsson via Cygwin wrote:
> > > > 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__'
> > > > [...]
> > > Thanks for the report.
> > > 
> > > This is a dumb bug I introduced into the build system in 3.4.0.  I fixed
> > > that in the git repo, but the automated build of the matching test
> > > [...]
> > Automated builds have been picked up again and the Cygwin test package
> > 3.5.0-0.17.g95f5b0a62036 should be available later today.  You can
> > install it using setup.exe, just like any other test release.
> >
> > Don't forget to install the matching cygwin-devel package, too, that's
> > the one containing the library libgmon.a, which is what gets linked in
> > with `gcc -pg'.
> 
> I can confirm 3.5.0-0.17.g95f5b0a62036 solves the issue with the "-pg"
> flag. Thank you!

Thanks for your feedback!


Corinna

  reply	other threads:[~2022-12-07 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:58 Daniel Abrahamsson
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 [this message]
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=Y5CswuzdEwENyRBm@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).