[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
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.

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 Jonathan Wakely changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 Jignesh changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRME

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 --- Comment #7 from Jakub Jelinek --- Neither of these projects lives on github. For glibc documentation see https://www.gnu.org/software/libc/libc.html sources should be grabbed from https://www.gnu.org/software/libc/sources.html but in the doc

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
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

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
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

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
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

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread j130496 at live dot co.uk via Gcc-bugs
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

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 --- Comment #2 from Jonathan Wakely --- (In reply to Jignesh from comment #0) > I am reproducing the comment posted there which gives entire details > required for bug tracking and resolving. Unfortunately, no developers are > responding to my m

[Bug c/100140] Reference gcc development github mirror - Latest Development Build

2021-04-19 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1