https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #10 from Jignesh ---
It was valuable insight for me - connection between gcc and glibc and how new
version of glibc impacts gcc compilation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Jignesh changed:
What|Removed |Added
Status|RESOLVED|CLOSED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #6 from Jignesh ---
As per guidance somewhere I will need to change configure script CFLAGS and
some other flag to point to new glibc. Can you please guide what and where I
will have to change to recompile gcc developmental version s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #5 from Jignesh ---
I think if I will compile using the new glibc version by pointing to the path
of that glibc - perhaps the problem will be resolved - It seems that the system
is compiling via 2.28 version while this single thread
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #4 from Jignesh ---
Again regarding glibc version:
through command ldd -version the output is 2.33.9000 while through following
script it is 2.28:
Script for glibc version:
#include
#include
#include
int main(int argc, char *a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #3 from Jignesh ---
Thank you for your responses
glibc version: 2.33.900 (developmental version installed from github) Source:
git clone https://github.com/bminor/glibc.
As far as I understand - I am doing a native build. I first d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Bug ID: 100140
Summary: Reference gcc development github mirror - Latest
Development Build
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
