From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) by sourceware.org (Postfix) with ESMTPS id 6849038369CC for ; Wed, 7 Dec 2022 11:50:43 +0000 (GMT) Authentication-Results: sourceware.org; dmarc=permerror header.from=cygwin.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=cygwin.com Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPSA (Nemesis) id 1Mhl0I-1oPPOp2FUW-00dkjK; Wed, 07 Dec 2022 12:50:39 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id 87E4DA80971; Wed, 7 Dec 2022 12:50:38 +0100 (CET) Date: Wed, 7 Dec 2022 12:50:38 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Cc: Daniel Abrahamsson Subject: Re: gcc -pg broken after cygwin update? Message-ID: Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, Daniel Abrahamsson References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:872c7obHe5xkNrbNQyyz7flAfh33ADIaXRsDbnBcHC07fYfHn5Y Kd880Bxe0TtLCWHFXuk5FT06sryzW+rFQsP7hYeOT8GNjtzuEAb8Jm0BFvKB8q9tFdzBkTy SGvwObrkCBuj2TVOqQl7Y1SYdEZZwzZwU6s/KwCJ+18mEIXXBop2+Xp+lbmzqhQqXjDgGj6 7ty8SJLh7/Qwk7YxGgehw== X-UI-Out-Filterresults: notjunk:1;V03:K0:BIhvpwaE2ac=:7aXSeci03YtFz/URejlU8A +avLI18Zw8/LDACVaECUIAkbpnxvH6VYyylGXabihytg4Xe7tW++evlk1Fj8qrre3GPll14Cs wt9nCgCRw3QrwXHIOe6dNkrCO9X6MWOrgvIjy8fw00iICNjKAkF/RJYOGRz5t0P3zDJCjXdB3 /lvhROgHXEDe3XoQtqKAZ7zwmrqDtXlji+uWveeSvHrVwVqbOjnBYTMY2TVG6+Zc7GylElAY2 LyG75owq8SGSNBN9xm6Xgw3YpAbnDoVkzaLxdgNETfW0dQiF5cHbbsrlRhcdgpt3yQS5HJ35x Qgyc37DwdwDK/StEohRZFLmOhRYcmo1bK15THWwG9mdE5x1SQrvkGTQhT8xJeoc3Sr5+Kfy5P LiBKyl7NGPYbXlGeDKT2wwG/Eh8hxUQqS/NP6UG3oc36k0TLqavky2Z8VLb9ByVYenkV9ygji YWSSKlpaM2eawCH0Rl76i5Mp9+1gZ638aQS4NORy13SFJxN5wEmp+ng+hAmmrfA0Eb5kI8czw Rdao+TIkAbFKnMudk+5BGvi5bRtfj4PhfWWa7ItH0KxkAq6IfCHa+sRLqkew3FuzH7S1uBC4j QXOOYPWq8vYLMqkoxhdzjTIKtJu+ytaJ+aJ4Oo2Y0QFOd4g+y3BcreavyOLUXNSF1DPppkT5o +/97JUJ7t1dp1teC+fU/UX53V0nSVIWmNnAQsHrxDNsFrfUuPsLx/EEIrF8yjjcDOkvxLO6Xt izmg2h3kZvzclYcJwLqfkzB7nif+SNtSj9CdFSobBXUbvOmZuEjiwyLDeS8+bJw1Vy8XyBXk+ h43EtdYMDN2NL8alG++/cQYyFCauQ== X-Spam-Status: No, score=-95.4 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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/.o .c > > gcc -o ../bin/ ../obj/.o -pg > > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: ../obj/.o: in function `exit_eval_failure': > /home/daab/dev/someproj/src/.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