dyncall: configure comparison

comparison configure @ 267:f8fe0f87b7c1

- removed configure-based checks for using --noexecstack / -Wa,--noexecstack in make A{S,C,}FLAGS variables, b/c inconsistent behaviour across platforms and often unusable, b/c: * braindead defaults (e.g. ASFLAGS on pretty much everything GNU, used in default suffix rules with *both* cc for .S and as for .s) * often took decisions on bogus private STACK headers in ELF files, set on platforms that lack any implementation, so pointless * tests have shown that only some GNU/* platforms and FreeBSD actually make use of this, if at all, that is... and for those, will switch back to .section .note.GNU-stack (next commit)

author	Tassilo Philipp
date	Sat, 27 May 2017 19:18:23 +0200
parents	91fd7be165f1
children	1032015f77ee

comparison

equal deleted inserted replaced

-:91fd7be165f1
+:f8fe0f87b7c1
 exit 0
 ;;
 esac
-# Assure objects not asking for an execstack (or binary that links dyncall might end
+# removed, b/c platform support not consistent and ELF flags checked often not having any result
-# up with one, for no reason).
+#
+## Assure objects not asking for an execstack (or binary that links dyncall might end
-# .s.o/.S.o rules often use ${CC} which then invokes the tools needed. GCC and
+## up with one, for no reason).
-# others might (annoyingly) assume that an executable stack may be required for
+#
-# those sources, if not told explicitly that it isn't.
+## .s.o/.S.o rules often use ${CC} which then invokes the tools needed. GCC and
-# Neither specifying this per source (e.g. via .section .note.GNU-stack,"",...), nor
+## others might (annoyingly) assume that an executable stack may be required for
-# per toolchain flags (e.g. as' --noexecstack) turned out to be portable across our
+## those sources, if not told explicitly that it isn't.
-# supported platforms, toolchains, and different versions of the latter (some even
+## Neither specifying this per source (e.g. via .section .note.GNU-stack,"",...), nor
-# producing the opposite result).
+## per toolchain flags (e.g. as' --noexecstack) turned out to be portable across our
-# Find needed build flags by running a few tests; use default if none result in "rw-".
+## supported platforms, toolchains, and different versions of the latter (some even
+## producing the opposite result).
-RWXTESTPREFIX="rwxtest" # @@@ put this maybe all in Makefile.generic? out of source builds?
+## Find needed build flags by running a few tests; use default if none result in "rw-".
-for s in S s ; do (
+#
-cd "$BLDTOP"
+#RWXTESTPREFIX="rwxtest" # @@@ put this maybe all in Makefile.generic? out of source builds?
-# asm test file, with main and _main for portability.
+#for s in S s ; do (
-(echo '.text';(echo '.globl main';echo 'main:') | sed 'p;s/m/_m/') > $RWXTESTPREFIX.$s
+#  cd "$BLDTOP"
+#  # asm test file, with main and _main for portability.
-# Check var to be used, which depends on inference rules of this platform. E.g. ASFLAGS is only common on GNU, and
+#  (echo '.text';(echo '.globl main';echo 'main:') | sed 'p;s/m/_m/') > $RWXTESTPREFIX.$s
-# on some other platforms only CFLAGS is the only one used, others use AFLAGS with cc and thus need -Wa,... Check
+#
-# makes use of the config written so far, so use '+=' to not overwrite vars.
+#  # Check var to be used, which depends on inference rules of this platform. E.g. ASFLAGS is only common on GNU, and
-for f in "" "ASFLAGS+=-Wa,--noexecstack" "ACFLAGS+=-Wa,--noexecstack" "AFLAGS+=--noexecstack" "AFLAGS+=-Wa,--noexecstack" "CFLAGS+=-Wa,--noexecstack"; do
+#  # on some other platforms only CFLAGS is the only one used, others use AFLAGS with cc and thus need -Wa,... Check
-# dummy makefile triggering inference rules, reflecting dyncall's build
+#  # makes use of the config written so far, so use '+=' to not overwrite vars.
-make -f - <<MAKEFILE
+#  for f in "" "ASFLAGS+=-Wa,--noexecstack" "ACFLAGS+=-Wa,--noexecstack" "AFLAGS+=--noexecstack" "AFLAGS+=-Wa,--noexecstack" "CFLAGS+=-Wa,--noexecstack"; do
-include $C
+#    # dummy makefile triggering inference rules, reflecting dyncall's build
-$f
+#    make -f - <<MAKEFILE
-# Force dependency via .o, to avoid .[sS].out rules that might be set - also set command as not all platforms set .o.out
+#include $C
-$RWXTESTPREFIX.out: $RWXTESTPREFIX.o
+#$f
-	\${CC} \${CFLAGS} \${LDFLAGS} $RWXTESTPREFIX.o \${LDLIBS} -o $RWXTESTPREFIX.out
+## Force dependency via .o, to avoid .[sS].out rules that might be set - also set command as not all platforms set .o.out
-MAKEFILE
+#$RWXTESTPREFIX.out: $RWXTESTPREFIX.o
+#	\${CC} \${CFLAGS} \${LDFLAGS} $RWXTESTPREFIX.o \${LDLIBS} -o $RWXTESTPREFIX.out
-# Check what stack of a built test binary would result in.
+#MAKEFILE
-# @@@ add xxd hexdump based versions for when objdump is not available; also check for those if we deal with ELF files
+#
-# @@@ maybe also limit to ELF files
+#    # Check what stack of a built test binary would result in.
-STACKFLAGS=`(which objdump && objdump -p $RWXTESTPREFIX.out) | sed -e '/STACK/bx' -e 'd' -e ':x' -e 'N' -e 's/^.*flags[ \t]\([^ \t]*\).*/\1/'`
+## @@@ add xxd hexdump based versions for when objdump is not available; also check for those if we deal with ELF files
-rm $RWXTESTPREFIX.out $RWXTESTPREFIX.o
+## @@@ maybe also limit to ELF files
-if [ "$STACKFLAGS" = "rw-" ]; then
+#    STACKFLAGS=`(which objdump && objdump -p $RWXTESTPREFIX.out) | sed -e '/STACK/bx' -e 'd' -e ':x' -e 'N' -e 's/^.*flags[ \t]\([^ \t]*\).*/\1/'`
-printf "$f\n"
+#    rm $RWXTESTPREFIX.out $RWXTESTPREFIX.o
-break
+#    if [ "$STACKFLAGS" = "rw-" ]; then
-fi
+#      printf "$f\n"
+#      break
-done
+#    fi
+#
-rm $RWXTESTPREFIX.$s
+#  done
+#
-) done 2>&1 | grep '^[ASC]\+FLAGS.*noexecstack$' | uniq >>$C
+#  rm $RWXTESTPREFIX.$s
+#
+#) done 2>&1 | grep '^[ASC]\+FLAGS.*noexecstack$' | uniq >>$C
 # Generate all makefiles needed
 include $BLDTOP/Makefile.config
 include \${VPATH}/Makefile.generic
 EOF
 done
-echo "Configuration written do $C"
+echo "Configuration written to $C"

Mercurial > pub > dyncall > dyncall

comparison configure @ 267:f8fe0f87b7c1