public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "worx at pouf dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99703] gcc-10.2.0 with Via C3 Eden: configure: error: Intel CET must be enabled on Intel CET enabled host
Date: Tue, 23 Mar 2021 15:40:17 +0000 [thread overview]
Message-ID: <bug-99703-4-35ndRNBtUf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99703-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99703
--- Comment #19 from Worx <worx at pouf dot org> ---
It's seems that the patch fix the issue.
Unfortunately, I have another error, but it's maybe i do not proper configure
"-march=c3"
make[3]: Leaving directory '/opt/gcc/host-i686-pc-linux-gnu/libdecnumber'
make[3]: Entering directory '/opt/gcc/host-i686-pc-linux-gnu/gcc'
build/gengtype \
-S ../.././gcc -I gtyp-input.list -w tmp-gtype.state
/bin/sh ../.././gcc/../move-if-change tmp-gtype.state gtype.state
build/gengtype \
-r gtype.state
make[3]: *** [Makefile:2786: s-gtype] Illegal instruction
make[3]: Leaving directory '/opt/gcc/host-i686-pc-linux-gnu/gcc'
make[2]: *** [Makefile:4822: all-stage2-gcc] Error 2
make[2]: Leaving directory '/opt/gcc'
make[1]: *** [Makefile:25993: stage2-bubble] Error 2
make[1]: Leaving directory '/opt/gcc'
make: *** [Makefile:26213: bootstrap] Error 2
next prev parent reply other threads:[~2021-03-23 15:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 23:57 [Bug libgcc/99703] New: " worx at pouf dot org
2021-03-22 0:00 ` [Bug libgcc/99703] " worx at pouf dot org
2021-03-22 8:20 ` [Bug target/99703] " marxin at gcc dot gnu.org
2021-03-22 9:18 ` rguenth at gcc dot gnu.org
2021-03-22 12:47 ` worx at pouf dot org
2021-03-22 12:47 ` worx at pouf dot org
2021-03-22 12:48 ` worx at pouf dot org
2021-03-22 12:52 ` rguenth at gcc dot gnu.org
2021-03-22 12:52 ` marxin at gcc dot gnu.org
2021-03-22 12:59 ` jakub at gcc dot gnu.org
2021-03-22 13:10 ` worx at pouf dot org
2021-03-22 18:34 ` hjl.tools at gmail dot com
2021-03-22 19:10 ` slyfox at gcc dot gnu.org
2021-03-22 19:20 ` slyfox at gcc dot gnu.org
2021-03-22 19:27 ` slyfox at gcc dot gnu.org
2021-03-22 19:27 ` slyfox at gcc dot gnu.org
2021-03-22 19:53 ` worx at pouf dot org
2021-03-22 20:25 ` hjl.tools at gmail dot com
2021-03-23 0:52 ` worx at pouf dot org
2021-03-23 15:40 ` worx at pouf dot org [this message]
2021-03-23 15:44 ` hjl.tools at gmail dot com
2021-03-23 15:54 ` worx at pouf dot org
2021-03-23 16:00 ` hjl.tools at gmail dot com
2021-03-23 19:46 ` hjl.tools at gmail dot com
2021-03-23 21:46 ` worx at pouf dot org
2021-03-23 21:53 ` hjl.tools at gmail dot com
2021-03-23 21:57 ` worx at pouf dot org
2021-03-23 21:59 ` worx at pouf dot org
2021-03-23 22:09 ` hjl.tools at gmail dot com
2021-03-23 22:12 ` jakub at gcc dot gnu.org
2021-03-23 22:53 ` worx at pouf dot org
2021-03-23 23:06 ` worx at pouf dot org
2021-03-25 0:34 ` worx at pouf dot org
2021-03-26 1:16 ` worx at pouf dot org
2021-05-03 12:01 ` cvs-commit at gcc dot gnu.org
2021-05-03 12:01 ` cvs-commit at gcc dot gnu.org
2021-05-03 12:45 ` hjl.tools at gmail dot com
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-99703-4-35ndRNBtUf@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).