gcc -pg broken after cygwin update?

[Daniel Abrahamsson]

> 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__'
> > > 
> > > 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?
> 
> > 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
> > release cygwin-3.5.0-0.17.g95f5b0a62036 is currently not building due to
> > some hiccup on cygwin.com.  I'll send a new mail as soon as this is
> > fixed and you can test it (provided you run at least Windows 8.1).
>
> 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!

Regards,
Daniel