search for: nocrypto

...ached PGP signature using your PGP utility. ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-crypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-crypto.bin.gz.asc ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-nocrypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-nocrypto.bin.gz.asc ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.7-i386-crypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.7-i386-crypto.bin.gz.asc ftp://ftp.FreeBS...

...ached PGP signature using your PGP utility. ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-crypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-crypto.bin.gz.asc ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-nocrypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.6-i386-nocrypto.bin.gz.asc ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.7-i386-crypto.bin.gz ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/SA-03:07/sendmail-4.7-i386-crypto.bin.gz.asc ftp://ftp.FreeBS...

...any files locally, FreeBSD Update may not be able to update them automatically (it will complain). With the latest version of FreeBSD Update (version 1.5), you can use one of the following commands: # /usr/local/sbin/freebsd-update --branch crypto fetch or # /usr/local/sbin/freebsd-update --branch nocrypto fetch depending upon whether you installed the "crypto" distribution, to force files to be updated. (If you're not sure if you installed the "crypto" distribution, you almost certainly did). FreeBSD Update will update a 5.2-RELEASE system to the exact binaries distribut...

.../tmp/test.o $ ./arm-eabi-gcc -march=armv8-a -mfpu=auto -c /tmp/test.c -o /tmp/test.o $ ./arm-eabi-gcc -march=armv8-a+dotprod -c /tmp/test.c -o /tmp/test.o arm-eabi-gcc: error: 'armv8-a' does not support feature 'dotprod' arm-eabi-gcc: note: valid feature names are: crc simd crypto nocrypto nofp $ ./arm-eabi-gcc -march=armv7-m -mfpu=neon-fp16 -c /tmp/test.c -o /tmp/test.o (same example given for Clang above, should be invalid) Clang AArch64 ============= The '+' syntax still applies but mfpu is replaced with '+' extensions. $ ./clang --target=aarch64-arm-none-eabi...

.../tmp/test.o $ ./arm-eabi-gcc -march=armv8-a -mfpu=auto -c /tmp/test.c -o /tmp/test.o $ ./arm-eabi-gcc -march=armv8-a+dotprod -c /tmp/test.c -o /tmp/test.o arm-eabi-gcc: error: 'armv8-a' does not support feature 'dotprod' arm-eabi-gcc: note: valid feature names are: crc simd crypto nocrypto nofp $ ./arm-eabi-gcc -march=armv7-m -mfpu=neon-fp16 -c /tmp/test.c -o /tmp/test.o (same example given for Clang above, should be invalid) Clang AArch64 ============= The '+' syntax still applies but mfpu is replaced with '+' extensions. $ ./clang --target=aarch64-arm-none-eabi...

.../tmp/test.o $ ./arm-eabi-gcc -march=armv8-a -mfpu=auto -c /tmp/test.c -o /tmp/test.o $ ./arm-eabi-gcc -march=armv8-a+dotprod -c /tmp/test.c -o /tmp/test.o arm-eabi-gcc: error: 'armv8-a' does not support feature 'dotprod' arm-eabi-gcc: note: valid feature names are: crc simd crypto nocrypto nofp $ ./arm-eabi-gcc -march=armv7-m -mfpu=neon-fp16 -c /tmp/test.c -o /tmp/test.o (same example given for Clang above, should be invalid) Clang AArch64 ============= The '+' syntax still applies but mfpu is replaced with '+' extensions. $ ./clang --target=aarch64-arm-none-eabi...