public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "j130496 at live dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100140] New: Reference gcc development github mirror - Latest Development Build
Date: Mon, 19 Apr 2021 04:52:05 +0000	[thread overview]
Message-ID: <bug-100140-4@http.gcc.gnu.org/bugzilla/> (raw)

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
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: j130496 at live dot co.uk
  Target Milestone: ---

Dear sir

Posting as under:

Used ../configure --enable-multilib and then make -s from build directory
created inside source downloaded from
https://github.com/gcc-mirror/gcc/commit/d64720a07f611c55e8c815c775a852d650a2e738
(link of latest GCC administrator bump on GCC development github mirror)

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:

Posted as under on Github: 

Dear sir

As conveyed earlier - even after latest daily bump, the following error while
using ../configure --enable-multilib followed by make -s persists. Request you
and entire community of developers to look into - I am not a developer myself
otherwise I could look into this and resolve myself and would have posted pull
request to be merged instead of requesting again and again. Facing this make -s
error since last 3 days. As I have personal interest in testing new development
of GCC 11 version (although not a developer and also not knowing much about C
and C++) - I am daily testing after changes. Error copied from terminal screen
is as under:

113 | "~" |
| ^~~~~~~~
gengtype-lex.c:365:15: warning: this statement may fall through
[-Wimplicit-fallthrough=]
365 | #define YY_DO_BEFORE_ACTION
| ~~~~~~~~~~~~~^~~~~~~
../../gcc/gengtype-lex.l:138:1: note: in expansion of macro
‘YY_DO_BEFORE_ACTION’
138 | ;
| ^ ~
../../gcc/gengtype-lex.l:134:1: note: here
134 | "ENUM_BITFIELD"{WS}?"("{WS}?{ID}{WS}?")" {
| ^~~~
/usr/local/x86_64-pc-linux-gnu/bin/ld:
/home/admin/Downloads/gcc_18042021_1708hrs_IST/build/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(guard.o):
in function __gnu_cxx::__is_single_threaded()':
/home/admin/Downloads/gcc_18042021_1708hrs_IST/build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/atomicity.h:52:
undefined reference to __libc_single_threaded'
/usr/local/x86_64-pc-linux-gnu/bin/ld:
/home/admin/Downloads/gcc_18042021_1708hrs_IST/build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/atomicity.h:52:
undefined reference to __libc_single_threaded'
/usr/local/x86_64-pc-linux-gnu/bin/ld:
/home/admin/Downloads/gcc_18042021_1708hrs_IST/build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/atomicity.h:52:
undefined reference to __libc_single_threaded'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:3008: build/genpreds] Error 1
make[2]: *** [Makefile:4822: all-stage2-gcc] Error 2
make[1]: *** [Makefile:25993: stage2-bubble] Error 2
make: *** [Makefile:1001: all] Error 2

My OS details: OS - AlmaLinux 8.3 x86_64 - kernel - 5.11.11-1.el8.elrepo.x86_64

Current stable GCC version details from terminal screen:

[root@admin build]# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/10.3.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.3.0 (GCC)

Once again requesting all to look into. 

Thank you in advance.

Regards,

             reply	other threads:[~2021-04-19  4:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  4:52 j130496 at live dot co.uk [this message]
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
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
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100140-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).