gcc -pg broken after cygwin update?

gcc -pg broken after cygwin update?

[Daniel Abrahamsson]

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

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

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).


Thanks,
Corinna

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

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'.


Thanks,
Corinna

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> provided you run at least Windows 8.1

Why would that be a requirement?

Anton Lavrentiev
Contractor NIH/NLM/NCBI

RE: 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

Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

On Dec  7 14:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > provided you run at least Windows 8.1
> 
> Why would that be a requirement?

Test releases are created from the master branch which already
bumped version to 3.5.0 and contains patches dropping W7 and W8
support:

https://cygwin.com/pipermail/cygwin-announce/2022-December/010821.html


Corinna

Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

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

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> contains patches dropping W7 and W8 support:

Hmm... I understood that "dropping support" was not something that would _require_ newer OS,
but that it may not work (or not guaranteed to work, patches not checked for compatibility, etc)
on the older OSes...  Are you saying that W7 and W8 would be actively rejected?  (Like some
M$ products do so now.)

Anton Lavrentiev
Contractor NIH/NLM/NCBI

Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

On Dec  7 17:59, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > contains patches dropping W7 and W8 support:
> 
> Hmm... I understood that "dropping support" was not something that
> would _require_ newer OS, but that it may not work (or not guaranteed
> to work, patches not checked for compatibility, etc) on the older
> OSes...  Are you saying that W7 and W8 would be actively rejected?

Supporting older OSes requires to keep workarounds in the code and
sometimes leads to the inability to implement stuff in ways only
available on newer OSes.

Each deprecation of older OSes in Cygwin worked like this so far, and
for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
since the first 3.3.0 release in October 2021.


Corinna

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
> since the first 3.3.0 release in October 2021.

I saw that.  It did not look alarming.  It basically was like "you'll be on your own".

> Supporting older OSes requires to keep workarounds in the code and

Understood.  But you did not answer my question:

> Are you saying that W7 and W8 would be actively rejected?

and I meant by Cygwin?

Anton Lavrentiev
Contractor NIH/NLM/NCBI

Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

On Dec  8 14:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
> > since the first 3.3.0 release in October 2021.
> 
> I saw that.  It did not look alarming.  It basically was like "you'll be on your own".
> 
> > Supporting older OSes requires to keep workarounds in the code and
> 
> Understood.  But you did not answer my question:
> 
> > Are you saying that W7 and W8 would be actively rejected?
> 
> and I meant by Cygwin?

Not "rejected" as such.  It just won't run correctly anymore on W7/8,
because

- the special treatment required for those OSes isn't in the DLL
  anymore, and
- the DLL uses functions not available on these OSes.


Corinna

RE: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

Sorry for pressing this, I must be slow today.

> just won't run correctly anymore on W7/8

Won't or may not?

Anton Lavrentiev
Contractor NIH/NLM/NCBI

Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?

[Corinna Vinschen]

On Dec  8 16:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> Sorry for pressing this, I must be slow today.
> 
> > just won't run correctly anymore on W7/8
> 
> Won't or may not?

Won't


Corinna