public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug build/26700] New: glibc 2.32 has default_cflags="-g -O" instead of "-g -O2"
@ 2020-10-02 12:14 loic.yhuel at gmail dot com
2020-10-02 19:37 ` [Bug build/26700] " carlos at redhat dot com
2020-10-02 19:38 ` carlos at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: loic.yhuel at gmail dot com @ 2020-10-02 12:14 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26700
Bug ID: 26700
Summary: glibc 2.32 has default_cflags="-g -O" instead of "-g
-O2"
Product: glibc
Version: 2.32
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: loic.yhuel at gmail dot com
CC: carlos at redhat dot com
Target Milestone: ---
default_cflags are set by Makeconfig when calling configure with an empty (but
set) CFLAGS, which is currently the case on crosstool-ng master for example.
ifeq ($(release),stable)
default_cflags := -g -O2
else
default_cflags := -g -O
endif
But 2.32 defines RELEASE as "release" in version.h, instead of "stable" for
previous versions.
So either the version.h should switch back to "stable", or the test in
Makeconfig should be changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug build/26700] glibc 2.32 has default_cflags="-g -O" instead of "-g -O2"
2020-10-02 12:14 [Bug build/26700] New: glibc 2.32 has default_cflags="-g -O" instead of "-g -O2" loic.yhuel at gmail dot com
@ 2020-10-02 19:37 ` carlos at redhat dot com
2020-10-02 19:38 ` carlos at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: carlos at redhat dot com @ 2020-10-02 19:37 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26700
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Loïc Yhuel from comment #0)
> default_cflags are set by Makeconfig when calling configure with an empty
> (but set) CFLAGS, which is currently the case on crosstool-ng master for
> example.
>
> ifeq ($(release),stable)
> default_cflags := -g -O2
> else
> default_cflags := -g -O
> endif
>
> But 2.32 defines RELEASE as "release" in version.h, instead of "stable" for
> previous versions.
>
> So either the version.h should switch back to "stable", or the test in
> Makeconfig should be changed.
This was my mistake and is present only on release/2.32/master.
Fixed on the release branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug build/26700] glibc 2.32 has default_cflags="-g -O" instead of "-g -O2"
2020-10-02 12:14 [Bug build/26700] New: glibc 2.32 has default_cflags="-g -O" instead of "-g -O2" loic.yhuel at gmail dot com
2020-10-02 19:37 ` [Bug build/26700] " carlos at redhat dot com
@ 2020-10-02 19:38 ` carlos at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: carlos at redhat dot com @ 2020-10-02 19:38 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26700
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.32
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
Fixed and if we roll a 2.32.1 this will be included.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-10-02 19:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-02 12:14 [Bug build/26700] New: glibc 2.32 has default_cflags="-g -O" instead of "-g -O2" loic.yhuel at gmail dot com
2020-10-02 19:37 ` [Bug build/26700] " carlos at redhat dot com
2020-10-02 19:38 ` carlos at redhat dot com
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).