* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
@ 2021-04-19 8:34 ` jakub at gcc dot gnu.org
2021-04-19 8:59 ` redi at gcc dot gnu.org
` (9 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-19 8:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
What glibc you are using?
libstdc++ refers to __libc_single_threaded only with
#elif __has_include(<sys/single_threaded.h>)
return ::__libc_single_threaded;
#else
and the sys/single_threaded.h header has been added in Glibc 2.32 together with
the __libc_single_threaded symbol.
So, are you doing a native build or cross-compilation (without sysroot?)?
Do you have some unrelated sys/single_threaded.h header around, or are
compiling against glibc 2.32+ headers and linking against glibc 2.31 or
earlier?
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
2021-04-19 8:34 ` [Bug c/100140] " jakub at gcc dot gnu.org
@ 2021-04-19 8:59 ` redi at gcc dot gnu.org
2021-04-19 9:20 ` j130496 at live dot co.uk
` (8 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-19 8:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(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 messages on Github development builds since last 2 days
> hence posting here:
Because it's an unofficial mirror that has nothing to do with the GCC project.
No GCC developers are involved in it and nobody reads anything there.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
2021-04-19 8:34 ` [Bug c/100140] " jakub at gcc dot gnu.org
2021-04-19 8:59 ` redi at gcc dot gnu.org
@ 2021-04-19 9:20 ` j130496 at live dot co.uk
2021-04-19 9:33 ` j130496 at live dot co.uk
` (7 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 9:20 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #3 from Jignesh <j130496 at live dot co.uk> ---
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 downloaded via
command git clone https://github.com/gcc-mirror/gcc target_directory in
terminal. Than in target directory I created build directory then - cd build,
../configure --enable-multilib followed by make -s and stopped at error.
Is this method a native build or cross compilation - sorry - but I cannot get
that.
As written in another comment, which is the official source of getting the
developmental version?
If I am doing something fundamentally wrong please let me know. I tried git
build of around 12-04-2021 and it was very successful in make -s and then make
install. So it seems that error has crept in after that by someone's pull
request which has this side effect (this is my thinking).
Thank you both of you again.
Regards,
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (2 preceding siblings ...)
2021-04-19 9:20 ` j130496 at live dot co.uk
@ 2021-04-19 9:33 ` j130496 at live dot co.uk
2021-04-19 9:39 ` j130496 at live dot co.uk
` (6 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 9:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #4 from Jignesh <j130496 at live dot co.uk> ---
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 <stdio.h>
#include <stdlib.h>
#include <gnu/libc-version.h>
int main(int argc, char *argv[]) {
printf("GNU libc version: %s\n", gnu_get_libc_version());
exit(EXIT_SUCCESS);
}
Thank you.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (3 preceding siblings ...)
2021-04-19 9:33 ` j130496 at live dot co.uk
@ 2021-04-19 9:39 ` j130496 at live dot co.uk
2021-04-19 9:45 ` j130496 at live dot co.uk
` (5 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 9:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #5 from Jignesh <j130496 at live dot co.uk> ---
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 was corrected in 2.32. I
will try doing that and post the results here.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (4 preceding siblings ...)
2021-04-19 9:39 ` j130496 at live dot co.uk
@ 2021-04-19 9:45 ` j130496 at live dot co.uk
2021-04-19 9:50 ` jakub at gcc dot gnu.org
` (4 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 9:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #6 from Jignesh <j130496 at live dot co.uk> ---
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 successfully. My new
libraries of glibc 2.33.9000 are at /usr/local/lib.
Thank you.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (5 preceding siblings ...)
2021-04-19 9:45 ` j130496 at live dot co.uk
@ 2021-04-19 9:50 ` jakub at gcc dot gnu.org
2021-04-19 9:58 ` redi at gcc dot gnu.org
` (3 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-19 9:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
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 documentation you'll see (and configure warns loudly) that
configuring glibc for prefix other than /usr is highly discouraged.
GCC has https://gcc.gnu.org home page with documentation and sources in
https://gcc.gnu.org/git/gcc.git
Anyway, this looks like a user error to me.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (6 preceding siblings ...)
2021-04-19 9:50 ` jakub at gcc dot gnu.org
@ 2021-04-19 9:58 ` redi at gcc dot gnu.org
2021-04-19 10:06 ` j130496 at live dot co.uk
` (2 subsequent siblings)
10 siblings, 0 replies; 12+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-19 9:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, you are trying to use a new version of glibc instead of the one in /usr
but you are not doing that correctly. The GCC build is finding the new headers,
but not the new libc.so that matches the headers.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (7 preceding siblings ...)
2021-04-19 9:58 ` redi at gcc dot gnu.org
@ 2021-04-19 10:06 ` j130496 at live dot co.uk
2021-04-19 10:10 ` redi at gcc dot gnu.org
2021-04-19 10:28 ` j130496 at live dot co.uk
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 10:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Jignesh <j130496 at live dot co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
Resolution|INVALID |FIXED
--- Comment #9 from Jignesh <j130496 at live dot co.uk> ---
Thank you both of you for quick responses and pointing out my error. I will do
the needful as suggested and then if find anything will post a new issue. I am
closing the thread now. Thank you again with regards and best wishes.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (8 preceding siblings ...)
2021-04-19 10:06 ` j130496 at live dot co.uk
@ 2021-04-19 10:10 ` redi at gcc dot gnu.org
2021-04-19 10:28 ` j130496 at live dot co.uk
10 siblings, 0 replies; 12+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-19 10:10 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |INVALID
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c/100140] Reference gcc development github mirror - Latest Development Build
2021-04-19 4:52 [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build j130496 at live dot co.uk
` (9 preceding siblings ...)
2021-04-19 10:10 ` redi at gcc dot gnu.org
@ 2021-04-19 10:28 ` j130496 at live dot co.uk
10 siblings, 0 replies; 12+ messages in thread
From: j130496 at live dot co.uk @ 2021-04-19 10:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100140
--- Comment #10 from Jignesh <j130496 at live dot co.uk> ---
It was valuable insight for me - connection between gcc and glibc and how new
version of glibc impacts gcc compilation.
^ permalink raw reply [flat|nested] 12+ messages in thread