CI: intel moved the script for ICC

Akim Demaille <[email protected]>
Newsgroups gmane.comp.parsers.bison.patches
Message-ID <[email protected]>
I'm pushing this, though it's a bit useless: ICC seems to dislike our code, for no good reason AFAICT (https://travis-ci.org/github/akimd/bison/jobs/716798713):

../src/symlist.c(75) (col. 3): error #2102: violation of ansi-alias rules
../src/symlist.c(234) (col. 11): error #2102: violation of ansi-alias rules
../src/symlist.c(235) (col. 9): error #2102: violation of ansi-alias rules

When I have time, and if I find how to do it, I'll file a PR to ICC.

commit 3724b50ef951a05afe01ead58adfda6147861c35
Author: Akim Demaille <[email protected]>
Date:   Tue Aug 11 06:34:55 2020 +0200

    CI: intel moved the script for ICC
    
    * .travis.yml: Adjust.

diff --git a/.travis.yml b/.travis.yml
index 853d5488..ed804e02 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -50,6 +50,7 @@ jobs:
         - make -j2 dist-xz
         # Can help understanding why we get "dirty" tarballs.
         - git status
+        - git diff
         - dist=$(echo bison*.xz)
 
         # Unfortunately we cannot deterministically know the name of the tarball without the full
@@ -129,7 +130,7 @@ jobs:
         - CC=icc
         - CXX=icpc
       install:
-        - source /opt/intel/inteloneapi/compiler/latest/env/vars.sh
+        - source /opt/intel/oneapi/compiler/latest/env/vars.sh
       addons:
         apt:
           sources:
diff --git a/lib/.gitignore b/lib/.gitignore
index 58aeac63..37ec5dec 100644
--- a/lib/.gitignore
+++ b/lib/.gitignore
@@ -336,6 +336,7 @@
 /sys_types.in.h
 /sys_wait.in.h
 /sysexits.in.h
+/termios.h
 /termios.in.h
 /textstyle.h
 /textstyle.in.h
diff --git a/m4/.gitignore b/m4/.gitignore
index 8d7a965a..9c84195a 100644
--- a/m4/.gitignore
+++ b/m4/.gitignore
@@ -67,6 +67,7 @@
 /intlmacosx.m4
 /intmax.m4
 /intmax_t.m4
+/inttypes-pri.m4
 /inttypes.m4
 /inttypes_h.m4
 /isnan.m4
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.