mirror of
https://github.com/samba-team/samba.git
synced 2025-01-27 14:04:05 +03:00
830c020645
This ensures that LANG=en_US.UTF8 is set, which Samba's build system needs to operate in UTF8 mode. The change to use flex to generate code meant that this difference between GitLab CI and oss-fuzz was exposed. REF: https://github.com/google/oss-fuzz/pull/4366 Signed-off-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz> Autobuild-User(master): Andrew Bartlett <abartlet@samba.org> Autobuild-Date(master): Wed Aug 26 03:20:46 UTC 2020 on sn-devel-184
98 lines
2.6 KiB
Bash
Executable File
98 lines
2.6 KiB
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# This is not a general-purpose build script, but instead one specific to the Google oss-fuzz compile environment.
|
|
#
|
|
# https://google.github.io/oss-fuzz/getting-started/new-project-guide/#Requirements
|
|
#
|
|
# https://github.com/google/oss-fuzz/blob/master/infra/base-images/base-builder/README.md#provided-environment-variables
|
|
#
|
|
# We have to push to oss-fuzz CFLAGS into the waf ADDITIONAL_CFLAGS
|
|
# as otherwise waf's configure fails linking the first test binary
|
|
#
|
|
# CFLAGS are supplied by the caller, eg the oss-fuzz compile command
|
|
#
|
|
# Additional arguments are passed to configure, to allow this to be
|
|
# tested in autobuild.py
|
|
#
|
|
|
|
# Ensure we give good trace info, fail right away and fail with unset
|
|
# variables
|
|
set -e
|
|
set -x
|
|
set -u
|
|
|
|
# It is critical that this script, just as the rest of Samba's GitLab
|
|
# CI docker has LANG set to en_US.utf8 (oss-fuzz fails to set this)
|
|
. /etc/default/locale
|
|
export LANG
|
|
export LC_ALL
|
|
|
|
ADDITIONAL_CFLAGS="$CFLAGS"
|
|
export ADDITIONAL_CFLAGS
|
|
CFLAGS=""
|
|
export CFLAGS
|
|
LD="$CXX"
|
|
export LD
|
|
|
|
# Use the system Python, not the OSS-Fuzz provided statically linked
|
|
# and instrumented Python, because we can't statically link.
|
|
|
|
PYTHON=/usr/bin/python3
|
|
export PYTHON
|
|
|
|
# $SANITIZER is provided by the oss-fuzz "compile" command
|
|
#
|
|
# We need to add the waf configure option as otherwise when we also
|
|
# get (eg) -fsanitize=address via the CFLAGS we will fail to link
|
|
# correctly
|
|
|
|
case "$SANITIZER" in
|
|
address)
|
|
SANITIZER_ARG='--address-sanitizer'
|
|
;;
|
|
undefined)
|
|
SANITIZER_ARG='--undefined-sanitizer'
|
|
;;
|
|
coverage)
|
|
SANITIZER_ARG=''
|
|
;;
|
|
esac
|
|
|
|
# $LIB_FUZZING_ENGINE is provided by the oss-fuzz "compile" command
|
|
#
|
|
|
|
./configure -C --without-gettext --enable-debug --enable-developer \
|
|
--enable-libfuzzer \
|
|
$SANITIZER_ARG \
|
|
--disable-warnings-as-errors \
|
|
--abi-check-disable \
|
|
--fuzz-target-ldflags="$LIB_FUZZING_ENGINE" \
|
|
--nonshared-binary=ALL \
|
|
"$@" \
|
|
LINK_CC="$CXX"
|
|
|
|
make -j
|
|
|
|
# Make a directory for the system shared libraries to be copied into
|
|
mkdir -p $OUT/lib
|
|
|
|
# We can't static link to all the system libs with waf, so copy them
|
|
# to $OUT/lib and set the rpath to point there. This is similar to how
|
|
# firefox handles this.
|
|
|
|
for x in bin/fuzz_*
|
|
do
|
|
cp $x $OUT/
|
|
bin=`basename $x`
|
|
|
|
# Copy any system libraries needed by this fuzzer to $OUT/lib
|
|
ldd $OUT/$bin | cut -f 2 -d '>' | cut -f 1 -d \( | cut -f 2 -d ' ' | xargs -i cp \{\} $OUT/lib/
|
|
|
|
# Change RUNPATH so that the copied libraries are found on the
|
|
# runner
|
|
chrpath -r '$ORIGIN/lib' $OUT/$bin
|
|
|
|
# Truncate the original binary to save space
|
|
echo -n > $x
|
|
done
|