From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Stefan Ring <stefanrin@gmail.com>
Cc: Mohana <s18002@students.iitmandi.ac.in>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Building gcc6.3.0 on Ubuntu-20.04
Date: Tue, 18 Aug 2020 10:01:45 +0100 [thread overview]
Message-ID: <CAH6eHdT4BE=CEXgcVEiJNHg0HoFZmYMvf5QeQixO0OzDc=A4OQ@mail.gmail.com> (raw)
In-Reply-To: <CAAxjCEy4izRy1ZZXYUAhYy9XG5HBqiVLQW-Z9S7wf1tKOJ7RzA@mail.gmail.com>
On Tue, 18 Aug 2020 at 09:29, Stefan Ring via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> On Mon, Aug 17, 2020 at 2:08 PM Mohana <s18002@students.iitmandi.ac.in> wrote:
> >
> > Hello,
> >
> > make[5]: Leaving directory
> > '/home/mohana/gccbuild/x86_64-pc-linux-gnu/32/libgcc'
> >
> > make[4]: *** [Makefile:1161: multi-do] Error 1
> >
> > make[4]: Leaving directory
> > '/home/mohana/gccbuild/x86_64-pc-linux-gnu/libgcc'
> >
> > make[3]: *** [Makefile:120: all-multi] Error 2
> >
> > make[3]: *** Waiting for unfinished jobs....
> >
> > make[3]: Leaving directory
> > '/home/mohana/gccbuild/x86_64-pc-linux-gnu/libgcc'
> >
> > make[2]: *** [Makefile:20436: all-stage1-target-libgcc] Error 2
> >
> > make[2]: Leaving directory '/home/mohana/gccbuild'
> >
> > make[1]: *** [Makefile:25715: stage1-bubble] Error 2
> >
> > Any leads will be highly appreciated!
>
> You should show the actual error, which seems to be this:
>
> make[5]: Entering directory '/home/build/gcbuild/x86_64-pc-linux-gnu/32/libgcc'
> # If this is the top-level multilib, build all the other
> # multilibs.
> /home/build/gcbuild/./gcc/xgcc -B/home/build/gcbuild/./gcc/
> -B/home/build/gcc6/x86_64-pc-linux-gnu/bin/
> -B/home/build/gcc6/x86_64-pc-linux-gnu/lib/ -isystem
> /home/build/gcc6/x86_64-pc-linux-gnu/include -isystem
> /home/build/gcc6/x86_64-pc-linux-gnu/sys-include -g -O2 -m32 -O2
> -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
> -Wno-format -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -isystem ./include -fpic -mlong-double-80
> -DUSE_ELF_SYMVER -g -DIN_LIBGCC2 -fbuilding-libgcc
> -fno-stack-protector -fpic -mlong-double-80 -DUSE_ELF_SYMVER -I. -I.
> -I../../.././gcc -I../../../../gcc-6.3.0/libgcc
> -I../../../../gcc-6.3.0/libgcc/. -I../../../../gcc-6.3.0/libgcc/../gcc
> -I../../../../gcc-6.3.0/libgcc/../include
> -I../../../../gcc-6.3.0/libgcc/config/libbid
> -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o unwind-dw2.o
> -MT unwind-dw2.o -MD -MP -MF unwind-dw2.dep -fexceptions -c
> ../../../../gcc-6.3.0/libgcc/unwind-dw2.c -fvisibility=hidden
> -DHIDE_EXPORTS
> In file included from ../../../../gcc-6.3.0/libgcc/unwind-dw2.c:401:0:
> ./md-unwind-support.h: In function 'x86_fallback_frame_state':
> ./md-unwind-support.h:141:18: error: field 'uc' has incomplete type
> struct ucontext uc;
> ^~
> make[5]: *** [../../../../gcc-6.3.0/libgcc/shared-object.mk:14:
This GCC code was actually not following the relevant standards and
was broken by a change in glibc when glibc got stricter.
You can fix it by replacing "struct ucontext" with "ucontext_t" in the
relevant files.
next prev parent reply other threads:[~2020-08-18 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 12:05 Mohana
2020-08-18 8:27 ` Stefan Ring
2020-08-18 9:01 ` Jonathan Wakely [this message]
2020-08-18 11:05 ` Mohana
2020-08-18 13:15 ` Jonathan Wakely
2020-08-18 15:31 ` Mohana
2020-08-18 15:58 ` Jonathan Wakely
2020-08-18 16:19 ` Dan Kegel
2020-08-19 4:35 ` Mohana
2020-08-19 6:37 ` Jonathan Wakely
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='CAH6eHdT4BE=CEXgcVEiJNHg0HoFZmYMvf5QeQixO0OzDc=A4OQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=s18002@students.iitmandi.ac.in \
--cc=stefanrin@gmail.com \
/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).