01ed2c499d
* Support negative-valued action parameters by converting them in the Python helper code into a positive value whose bit pattern is the 2's complement representation of the negative value. * Add new bash function used several times in install script Also delete some old comments. These changes help to make the script have fewer diffs with the following script that it was derived from: https://github.com/jafingerhut/p4-guide/blob/master/bin/install-p4dev-v6.sh * Fix copy & paste mistake
227 lines
7.3 KiB
Bash
Executable File
227 lines
7.3 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Print script commands and exit on errors.
|
|
set -xe
|
|
|
|
#Src
|
|
BMV2_COMMIT="6ee70b5eff7f510b32c074aaa4f00358f594fecb" # 2023-Jul-01
|
|
PI_COMMIT="f043e6f5f4271076ad7e58aa9889c82dbfc8c3ca" # 2023-Jul-01
|
|
P4C_COMMIT="c7a503d5b6f5711cf61e7e2878eaa670fd90c71d" # 2023-Jul-01
|
|
PTF_COMMIT="d2e2d8ad005a451ad11f9d21af50079a0552921a" # 2023-Jul-01
|
|
PROTOBUF_COMMIT="v3.18.1"
|
|
GRPC_COMMIT="tags/v1.43.2"
|
|
|
|
#Get the number of cores to speed up the compilation process
|
|
NUM_CORES=`grep -c ^processor /proc/cpuinfo`
|
|
|
|
# Change this to a lower value if you do not like all this extra debug
|
|
# output. It is occasionally useful to debug why Python package
|
|
# install files, or other files installed system-wide, are not going
|
|
# to the places where one might hope.
|
|
DEBUG_INSTALL=2
|
|
|
|
debug_dump_many_install_files() {
|
|
local OUT_FNAME="$1"
|
|
if [ ${DEBUG_INSTALL} -ge 2 ]
|
|
then
|
|
find /usr/lib /usr/local $HOME/.local | sort > "${OUT_FNAME}"
|
|
fi
|
|
}
|
|
|
|
# The install steps for p4lang/PI and p4lang/behavioral-model end
|
|
# up installing Python module code in the site-packages directory
|
|
# mentioned below in this function. That is were GNU autoconf's
|
|
# 'configure' script seems to find as the place to put them.
|
|
|
|
# On Ubuntu systems when you run the versions of Python that are
|
|
# installed via Debian/Ubuntu packages, they only look in a
|
|
# sibling dist-packages directory, never the site-packages one.
|
|
|
|
# If I could find a way to change the part of the install script
|
|
# so that p4lang/PI and p4lang/behavioral-model install their
|
|
# Python modules in the dist-packages directory, that sounds
|
|
# useful, but I have not found a way.
|
|
|
|
# As a workaround, after finishing the part of the install script
|
|
# for those packages, I will invoke this function to move them all
|
|
# into the dist-packages directory.
|
|
|
|
# Some articles with questions and answers related to this.
|
|
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765022
|
|
# https://bugs.launchpad.net/ubuntu/+source/automake/+bug/1250877
|
|
# https://unix.stackexchange.com/questions/351394/makefile-installing-python-module-out-of-of-pythonpath
|
|
|
|
PY3LOCALPATH=`${HOME}/py3localpath.py`
|
|
|
|
move_usr_local_lib_python3_from_site_packages_to_dist_packages() {
|
|
local SRC_DIR
|
|
local DST_DIR
|
|
local j
|
|
local k
|
|
|
|
SRC_DIR="${PY3LOCALPATH}/site-packages"
|
|
DST_DIR="${PY3LOCALPATH}/dist-packages"
|
|
|
|
# When I tested this script on Ubunt 16.04, there was no
|
|
# site-packages directory. Return without doing anything else if
|
|
# this is the case.
|
|
if [ ! -d ${SRC_DIR} ]
|
|
then
|
|
return 0
|
|
fi
|
|
|
|
# Do not move any __pycache__ directory that might be present.
|
|
sudo rm -fr ${SRC_DIR}/__pycache__
|
|
|
|
echo "Source dir contents before moving: ${SRC_DIR}"
|
|
ls -lrt ${SRC_DIR}
|
|
echo "Dest dir contents before moving: ${DST_DIR}"
|
|
ls -lrt ${DST_DIR}
|
|
for j in ${SRC_DIR}/*
|
|
do
|
|
echo $j
|
|
k=`basename $j`
|
|
# At least sometimes (perhaps always?) there is a directory
|
|
# 'p4' or 'google' in both the surce and dest directory. I
|
|
# think I want to merge their contents. List them both so I
|
|
# can see in the log what was in both at the time:
|
|
if [ -d ${SRC_DIR}/$k -a -d ${DST_DIR}/$k ]
|
|
then
|
|
echo "Both source and dest dir contain a directory: $k"
|
|
echo "Source dir $k directory contents:"
|
|
ls -l ${SRC_DIR}/$k
|
|
echo "Dest dir $k directory contents:"
|
|
ls -l ${DST_DIR}/$k
|
|
sudo mv ${SRC_DIR}/$k/* ${DST_DIR}/$k/
|
|
sudo rmdir ${SRC_DIR}/$k
|
|
else
|
|
echo "Not a conflicting directory: $k"
|
|
sudo mv ${SRC_DIR}/$k ${DST_DIR}/$k
|
|
fi
|
|
done
|
|
|
|
echo "Source dir contents after moving: ${SRC_DIR}"
|
|
ls -lrt ${SRC_DIR}
|
|
echo "Dest dir contents after moving: ${DST_DIR}"
|
|
ls -lrt ${DST_DIR}
|
|
}
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-1-before-protobuf.txt
|
|
|
|
# --- Protobuf --- #
|
|
git clone https://github.com/protocolbuffers/protobuf
|
|
cd protobuf
|
|
git checkout ${PROTOBUF_COMMIT}
|
|
git submodule update --init --recursive
|
|
./autogen.sh
|
|
# install-p4dev-v6.sh script doesn't have --prefix=/usr option here.
|
|
./configure --prefix=/usr
|
|
make -j${NUM_CORES}
|
|
sudo make install
|
|
sudo ldconfig
|
|
cd ..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-2-after-protobuf.txt
|
|
|
|
# --- gRPC --- #
|
|
git clone https://github.com/grpc/grpc.git
|
|
cd grpc
|
|
git checkout ${GRPC_COMMIT}
|
|
git submodule update --init --recursive
|
|
mkdir -p cmake/build
|
|
cd cmake/build
|
|
cmake ../..
|
|
make -j${NUM_CORES}
|
|
sudo make install
|
|
# I believe the following 2 'pip3 install ...' commands, adapted from
|
|
# similar commands in src/python/grpcio/README.rst, should install the
|
|
# Python3 module grpc.
|
|
debug_dump_many_install_files $HOME/usr-local-2b-before-grpc-pip3.txt
|
|
pip3 list | tee $HOME/pip3-list-2b-before-grpc-pip3.txt
|
|
cd ../..
|
|
# Before some time in 2023-July, the `sudo pip3 install
|
|
# -rrequirements.txt` command below installed the Cython package
|
|
# version 0.29.35. After that time, it started installing Cython
|
|
# package version 3.0.0, which gives errors on the `sudo pip3 install
|
|
# .` command afterwards. Fix this by forcing installation of a known
|
|
# working version of Cython.
|
|
sudo pip3 install Cython==0.29.35
|
|
sudo pip3 install -rrequirements.txt
|
|
GRPC_PYTHON_BUILD_WITH_CYTHON=1 sudo pip3 install .
|
|
sudo ldconfig
|
|
cd ..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-3-after-grpc.txt
|
|
|
|
# Note: This is a noticeable difference between how an earlier
|
|
# user-bootstrap.sh version worked, where it effectively ran
|
|
# behavioral-model's install_deps.sh script, then installed PI, then
|
|
# went back and compiled the behavioral-model code. Building PI code
|
|
# first, without first running behavioral-model's install_deps.sh
|
|
# script, might result in less PI project features being compiled into
|
|
# its binaries.
|
|
|
|
# --- PI/P4Runtime --- #
|
|
git clone https://github.com/p4lang/PI.git
|
|
cd PI
|
|
git checkout ${PI_COMMIT}
|
|
git submodule update --init --recursive
|
|
./autogen.sh
|
|
# install-p4dev-v6.sh adds more --without-* options to the configure
|
|
# script here. I suppose without those, this script will cause
|
|
# building PI code to include more features?
|
|
./configure --with-proto
|
|
make -j${NUM_CORES}
|
|
sudo make install
|
|
make clean
|
|
move_usr_local_lib_python3_from_site_packages_to_dist_packages
|
|
sudo ldconfig
|
|
cd ..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-4-after-PI.txt
|
|
|
|
# --- Bmv2 --- #
|
|
git clone https://github.com/p4lang/behavioral-model.git
|
|
cd behavioral-model
|
|
git checkout ${BMV2_COMMIT}
|
|
./install_deps.sh
|
|
./autogen.sh
|
|
./configure --enable-debugger --with-pi --with-thrift
|
|
make -j${NUM_CORES}
|
|
sudo make install-strip
|
|
sudo ldconfig
|
|
# install-p4dev-v6.sh script does this here:
|
|
move_usr_local_lib_python3_from_site_packages_to_dist_packages
|
|
cd ..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-5-after-behavioral-model.txt
|
|
|
|
# --- P4C --- #
|
|
git clone https://github.com/p4lang/p4c
|
|
cd p4c
|
|
git checkout ${P4C_COMMIT}
|
|
git submodule update --init --recursive
|
|
mkdir -p build
|
|
cd build
|
|
cmake .. -DENABLE_TEST_TOOLS=ON
|
|
# The command 'make -j${NUM_CORES}' works fine for the others, but
|
|
# with 2 GB of RAM for the VM, there are parts of the p4c build where
|
|
# running 2 simultaneous C++ compiler runs requires more than that
|
|
# much memory. Things work better by running at most one C++ compilation
|
|
# process at a time.
|
|
make -j1
|
|
sudo make install
|
|
sudo ldconfig
|
|
cd ../..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-6-after-p4c.txt
|
|
|
|
# --- PTF --- #
|
|
git clone https://github.com/p4lang/ptf
|
|
cd ptf
|
|
git checkout ${PTF_COMMIT}
|
|
sudo pip3 install .
|
|
cd ..
|
|
|
|
debug_dump_many_install_files $HOME/usr-local-8-after-ptf-install.txt
|