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: Mon, 22 Mar 2021 19:53:39 +0000	[thread overview]
Message-ID: <bug-99703-4-ob33e6aqfp@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 #16 from Worx <worx at pouf dot org> ---
(In reply to H.J. Lu from comment #11)
> (In reply to Worx from comment #10)
> > When I deep dive, in the logs
> > 
> > No issue at the root level : 
> > 
> > c3eden /opt/gcc-10.2.0 # ./configure --disable-cet
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking target system type... i686-pc-linux-gnu
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether ln works... yes
> > [..]
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > configure: creating ./config.status
> > config.status: creating Makefile
> > c3eden /opt/gcc-10.2.0 #
> > 
> > ========
> > But : 
> > ========
> > 
> > c3eden /opt/gcc-10.2.0 # lto-plugin/configure --disable-cet
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking target system type... i686-pc-linux-gnu
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for a thread-safe mkdir -p... /bin/mkdir -p
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > checking for style of include used by make... GNU
> > checking for gcc... gcc
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables...
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking for gcc option to accept ISO C89... none needed
> > checking whether gcc understands -c and -o together... yes
> > checking dependency style of gcc... gcc3
> > checking how to run the C preprocessor... gcc -E
> > checking for grep that handles long lines and -e... /bin/grep
> > checking for egrep... /bin/grep -E
> > checking for ANSI C header files... yes
> > checking for sys/types.h... yes
> > checking for sys/stat.h... yes
> > checking for stdlib.h... yes
> > checking for string.h... yes
> > checking for memory.h... yes
> > checking for strings.h... yes
> > checking for inttypes.h... yes
> > checking for stdint.h... yes
> > checking for unistd.h... yes
> > checking minix/config.h usability... no
> > checking minix/config.h presence... no
> > checking for minix/config.h... no
> > checking whether it is safe to define __EXTENSIONS__... yes
> > checking for gcc... (cached) gcc
> > checking whether we are using the GNU C compiler... (cached) yes
> > checking whether gcc accepts -g... (cached) yes
> > checking for gcc option to accept ISO C89... (cached) none needed
> > checking whether gcc understands -c and -o together... (cached) yes
> > checking dependency style of gcc... (cached) gcc3
> > checking for special C compiler options needed for large files... no
> > checking for _FILE_OFFSET_BITS value needed for large files... 64
> > checking whether gcc supports -Wall... yes
> > checking for -static-libgcc... yes
> > checking for CET support... configure: error: Intel CET must be enabled on
> > Intel CET enabled host
> > c3eden /opt/gcc-10.2.0 #
> 
> In which directory did it fail?

lto-plugin directory

  parent reply	other threads:[~2021-03-22 19:53 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 [this message]
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
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-ob33e6aqfp@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).