Mailing List Archive

Strange message seen on FreeBSD 14.0 amd64
Dear GnuPG type folks :

I don't know what this means. Can we just compile with a decent C
compiler such as the LLVM/Clang in FreeBSD ?


/*
Please not that your compiler does not support the GCC style
aligned attribute. Using this software may evoke bus errors.
*/



I saw that on a FreeBSD 14.0 server after a neat configure :


hydra$
hydra$ ./configure --prefix=/opt/bw \
> --disable-silent-rules --enable-dependency-tracking \
> --enable-static --enable-shared --disable-asm \
> --disable-aesni-support --disable-shaext-support \
> --disable-pclmul-support --disable-sse41-support \
> --disable-drng-support --disable-avx-support \
> --disable-avx2-support --disable-O-flag-munging \
> --disable-optimization --without-gnu-ld \
> --with-libgpg-error-prefix=/opt/bw --without-pth-prefix 2>&1 | tee
../libgcrypt-1.10.2_FreeBSD14_amd64.001.config.log
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether /usr/local/bin/gmake sets $(MAKE)... yes
checking whether /usr/local/bin/gmake supports nested variables... yes
checking build system type... x86_64-unknown-freebsd14.0
checking host system type... x86_64-unknown-freebsd14.0
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether /usr/local/bin/gmake supports nested variables...
(cached) yes
checking whether /usr/local/bin/gmake supports the include directive...
yes (GNU style)
checking for gcc... /usr/bin/cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/cc accepts -g... yes
checking for /usr/bin/cc option to accept ISO C89... none needed
checking whether /usr/bin/cc understands -c and -o together... yes
checking dependency style of /usr/bin/cc... gcc3
checking how to run the C preprocessor... /usr/bin/cc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether /usr/local/bin/gmake sets $(MAKE)... (cached) yes
checking for gcc... (cached) /usr/bin/cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/cc accepts -g... (cached) yes
checking for /usr/bin/cc option to accept ISO C89... (cached) none needed
checking whether /usr/bin/cc understands -c and -o together... (cached) yes
checking dependency style of /usr/bin/cc... (cached) gcc3
checking how to run the C preprocessor... /usr/bin/cc -E
checking dependency style of /usr/bin/cc... gcc3
checking for library containing strerror... none required
checking for gawk... (cached) nawk
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by /usr/bin/cc...
/usr/local/bin/x86_64-unknown-freebsd14.0-ld
checking if the linker (/usr/local/bin/x86_64-unknown-freebsd14.0-ld) is
GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/local/bin/nm -B
checking the name lister (/usr/local/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 393216
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking how to convert x86_64-unknown-freebsd14.0 file names to
x86_64-unknown-freebsd14.0 format... func_convert_file_noop
checking how to convert x86_64-unknown-freebsd14.0 file names to
toolchain format... func_convert_file_noop
checking for /usr/local/bin/x86_64-unknown-freebsd14.0-ld option to
reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/local/bin/nm -B output from /usr/bin/cc
object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if /usr/bin/cc supports -fno-rtti -fno-exceptions... yes
checking for /usr/bin/cc option to produce PIC... -fPIC -DPIC
checking if /usr/bin/cc PIC flag -fPIC -DPIC works... yes
checking if /usr/bin/cc static flag -static works... yes
checking if /usr/bin/cc supports -c -o file.o... yes
checking if /usr/bin/cc supports -c -o file.o... (cached) yes
checking whether the /usr/bin/cc linker
(/usr/local/bin/x86_64-unknown-freebsd14.0-ld) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... freebsd14.0 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... no
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for windres... no
checking whether byte ordering is bigendian... no
checking size of unsigned short... 2
checking size of unsigned int... 4
checking size of unsigned long... 8
checking size of unsigned long long... 8
checking size of void *... 8
checking for uintptr_t... yes
checking for UINT64_C... yes
checking size of uint64_t... 8
checking which symmetric ciphers to include... arcfour blowfish cast5
des aes twofish serpent rfc2268 seed camellia idea salsa20 gost28147
chacha20 sm4
checking which public-key ciphers to include... dsa elgamal rsa ecc
checking which message digests to include... crc gostr3411-94 md4 md5
rmd160 sha1 sha256 sha512 sha3 tiger whirlpool stribog blake2 sm3
checking which key derivation functions to include... s2k pkdf2 scrypt
checking which random module to use... default
checking whether use of /dev/random is requested... yes
checking whether the experimental random daemon is requested... no
checking whether MPI and cipher assembler modules are requested... no
checking whether memory guard is requested... no
checking whether to run large data tests... no
checking whether 'soft' HW feature bits are forced on... no
checking whether use of capabilities is requested... no
checking whether a HMAC binary check is requested... no
checking whether jitter entropy support is requested... yes
checking whether padlock support is requested... yes
checking whether AESNI support is requested... no
checking whether SHAEXT support is requested... no
checking whether PCLMUL support is requested... no
checking whether SSE4.1 support is requested... no
checking whether DRNG support is requested... no
checking whether AVX support is requested... no
checking whether AVX2 support is requested... no
checking whether NEON support is requested... yes
checking whether ARMv8 Crypto Extension support is requested... yes
checking whether PPC crypto support is requested... yes
checking whether a -O flag munging is requested... no
checking whether a instrumentation (-fprofile, -fsanitize) munging is
requested... yes
checking whether to enable AMD64 as(1) feature detection... yes
checking for gpg-error-config... /opt/bw/bin/gpg-error-config
checking for gpgrt-config... /opt/bw/bin/gpgrt-config
configure: Use gpgrt-config with /opt/bw/lib as gpg-error-config
checking for GPG Error - version >= 1.27... yes (1.47)
checking for pthread_create in -lpthread... yes
checking for library containing setsockopt... none required
checking for library containing setsockopt... (cached) none required
checking for unistd.h... (cached) yes
checking sys/auxv.h usability... yes
checking sys/auxv.h presence... yes
checking for sys/auxv.h... yes
checking sys/random.h usability... yes
checking sys/random.h presence... yes
checking for sys/random.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for pid_t... yes
checking for byte... no
checking for ushort... yes
checking for u16... no
checking for u32... no
checking for u64... no
checking for sys/socket.h... yes
checking for socklen_t... yes
checking for __builtin_bswap32... yes
checking for __builtin_bswap64... yes
checking for __builtin_ctz... yes
checking for __builtin_ctzl... yes
checking for __builtin_clz... yes
checking for __builtin_clzl... yes
checking for __sync_synchronize... yes
checking whether the variable length arrays are supported... yes
checking whether the visibility attribute is supported... yes
checking for broken visibility attribute... no
checking for broken alias attribute... no
checking if gcc supports -fvisibility=hidden... yes
checking whether the GCC style aligned attribute is supported... no
checking whether the GCC style packed attribute is supported... no
checking whether the GCC style may_alias attribute is supported... no
checking whether 'asm' assembler keyword is supported... no
checking whether '__asm__' assembler keyword is supported... yes
checking whether inline assembly memory barrier is supported... yes
checking whether GCC assembler is compatible for ARM assembly
implementations... n/a
checking whether GCC assembler is compatible for ARMv8/Aarch64 assembly
implementations... n/a
checking whether GCC assembler supports for CFI directives... no
checking whether GCC assembler supports for ELF directives... yes
checking for _ prefix in compiled symbols... no
checking architecture and mpi assembler functions... disabled
checking whether compiler supports 'ms_abi' function attribute... no
checking whether compiler supports 'sysv_abi' function attribute... no
checking whether GCC inline assembler supports SSSE3 instructions... n/a
checking whether GCC inline assembler supports PCLMUL instructions... n/a
checking whether GCC inline assembler supports SHA Extensions
instructions... n/a
checking whether GCC inline assembler supports SSE4.1 instructions... n/a
checking whether GCC inline assembler supports AVX instructions... n/a
checking whether GCC inline assembler supports AVX2 instructions... n/a
checking whether GCC inline assembler supports VAES and VPCLMUL
instructions... n/a
checking whether GCC inline assembler supports BMI2 instructions... n/a
checking whether GCC assembler handles division correctly... yes
checking whether GCC assembler is compatible for amd64 assembly
implementations... n/a
checking whether GCC assembler is compatible for Intel syntax assembly
implementations... n/a
checking whether compiler is configured for ARMv6 or newer
architecture... n/a
checking whether GCC inline assembler supports NEON instructions... n/a
checking whether GCC inline assembler supports AArch32 Crypto Extension
instructions... n/a
checking whether GCC inline assembler supports AArch64 NEON
instructions... n/a
checking whether GCC inline assembler supports AArch64 Crypto Extension
instructions... n/a
checking whether compiler supports PowerPC AltiVec/VSX intrinsics... n/a
checking whether GCC inline assembler supports PowerPC
AltiVec/VSX/crypto instructions... n/a
checking whether GCC inline assembler supports PowerISA 3.00
instructions... n/a
checking whether GCC inline assembler supports zSeries instructions... n/a
checking whether GCC inline assembler supports zSeries vector
instructions... n/a
checking for vprintf... yes
checking for _doprnt... no
checking for stpcpy... yes
checking for strcasecmp... yes
checking for strtoul... yes
checking for memmove... yes
checking for stricmp... no
checking for atexit... yes
checking for raise... yes
checking for strerror... yes
checking for rand... yes
checking for mmap... yes
checking for getpagesize... yes
checking for sysconf... yes
checking for waitpid... yes
checking for wait4... yes
checking for gettimeofday... yes
checking for getrusage... yes
checking for gethrtime... no
checking for clock_gettime... yes
checking for syslog... yes
checking for syscall... yes
checking for fcntl... yes
checking for ftruncate... yes
checking for flockfile... yes
checking for getauxval... no
checking for elf_aux_info... yes
checking for explicit_bzero... yes
checking for explicit_memset... no
checking for getentropy... yes
checking for mlock... yes
checking for sysconf... (cached) yes
checking for getpagesize... (cached) yes
checking whether mlock is broken... no
checking for getpid... yes
checking for clock... yes
checking for random device... yes
configure: checking for cc features
checking if gcc supports -fno-delete-null-pointer-checks... yes
checking whether non excutable stack support is requested... yes
checking whether assembler supports --noexecstack option... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating m4/Makefile
config.status: creating compat/Makefile
config.status: creating mpi/Makefile
config.status: creating cipher/Makefile
config.status: creating random/Makefile
config.status: creating doc/Makefile
config.status: creating src/Makefile
config.status: creating src/gcrypt.h
config.status: creating src/libgcrypt-config
config.status: creating src/libgcrypt.pc
config.status: creating src/versioninfo.rc
config.status: creating tests/Makefile
config.status: creating tests/hashtest-256g
config.status: creating tests/basic-disable-all-hwf
config.status: creating config.h
config.status: linking mpi/generic/mpih-add1.c to mpi/mpih-add1.c
config.status: linking mpi/generic/mpih-sub1.c to mpi/mpih-sub1.c
config.status: linking mpi/generic/mpih-mul1.c to mpi/mpih-mul1.c
config.status: linking mpi/generic/mpih-mul2.c to mpi/mpih-mul2.c
config.status: linking mpi/generic/mpih-mul3.c to mpi/mpih-mul3.c
config.status: linking mpi/generic/mpih-lshift.c to mpi/mpih-lshift.c
config.status: linking mpi/generic/mpih-rshift.c to mpi/mpih-rshift.c
config.status: linking mpi/generic/mpi-asm-defs.h to mpi/mpi-asm-defs.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing gcrypt-conf commands

Libgcrypt v1.10.2 has been configured as follows:

Platform: FreeBSD (x86_64-unknown-freebsd14.0)
Hardware detection module: none
Enabled cipher algorithms: arcfour blowfish cast5 des aes twofish
serpent rfc2268 seed camellia idea
salsa20
gost28147 chacha20 sm4
Enabled digest algorithms: crc gostr3411-94 md4 md5 rmd160 sha1
sha256 sha512 sha3 tiger whirlpool
stribog
blake2 sm3
Enabled kdf algorithms: s2k pkdf2 scrypt
Enabled pubkey algorithms: dsa elgamal rsa ecc
Random number generator: default
Try using jitter entropy: yes
Using linux capabilities: no
FIPS module version:
Try using Padlock crypto: n/a
Try using AES-NI crypto: n/a
Try using Intel SHAEXT: n/a
Try using Intel PCLMUL: n/a
Try using Intel SSE4.1: n/a
Try using DRNG (RDRAND): n/a
Try using Intel AVX: n/a
Try using Intel AVX2: n/a
Try using ARM NEON: n/a
Try using ARMv8 crypto: n/a
Try using PPC crypto: n/a

Please not that your compiler does not support the GCC style
aligned attribute. Using this software may evoke bus errors.

hydra$


So what does that mean ? I *must* use GCC to compile this source ?


--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional



_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Strange message seen on FreeBSD 14.0 amd64 [ In reply to ]
> Please not[e] that your compiler does not support the GCC style aligned attribute. Using this software may evoke bus errors.
I'd like to pose the question of why GnuPG should use the non-standard aligned attribute anyway, when to the best of my knowledge, the same functionality is supported in C11 with the alignas operator. Perhaps this was just overlooked? If support for pre-C11 GCC is a concern, maybe a wrapper macro could choose whichever method is supported.

I hope this can be considered as a solution.
Re: Strange message seen on FreeBSD 14.0 amd64 [ In reply to ]
Dennis Clarke via Gnupg-users wrote:
>
> Dear GnuPG type folks :
>
> I don't know what this means. Can we just compile with a decent C
> compiler such as the LLVM/Clang in FreeBSD ?
>
>
> [...]
>
> Libgcrypt v1.10.2 has been configured as follows:
>
> [...]
>
> Please not that your compiler does not support the GCC style
> aligned attribute. Using this software may evoke bus errors.
>
> hydra$
>
>
> So what does that mean ? I *must* use GCC to compile this source ?

It means that the sources use a GNU extension that configure has
detected that Clang does not properly implement. The specific example
cited ("aligned") should be non-critical for you, since you are running
on AMD64 and that architecture does not actually require proper
alignment. The resultant executables should work in your case, but at
reduced performance (unaligned accesses are permitted on x86-64, but are
slower than aligned accesses) unless SSE (which *does* have hard
alignment requirements) is used. Since I note that you are disabling
the use of assembler modules, SSE will probably *not* be used in your
executable.

In short, try it---if it works for you, great! If GPG crashes with
SIGBUS, try rebuilding it with GCC before reporting a bug in GPG. If it
works when built with GCC, you have found a bug (a missing feature that
Clang claims to have) in Clang. Clang typically defines __GNUC__, thus
claiming to support GNU extensions, so this is a bug in Clang if your
Clang-compiled GPG does not work.


-- Jacob


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Strange message seen on FreeBSD 14.0 amd64 [ In reply to ]
On 7/11/23 21:30, Jacob Bachmeyer wrote:
> Dennis Clarke via Gnupg-users wrote:
>>
>> Dear GnuPG type folks :
>>
>>     I don't know what this means. Can we just compile with a decent C
>>  compiler such as the LLVM/Clang in FreeBSD ?
>>
>>
>> [...]
>>
>>         Libgcrypt v1.10.2 has been configured as follows:
>>
>> [...]
>>
>>    Please not that your compiler does not support the GCC style
>>    aligned attribute. Using this software may evoke bus errors.
>>
>> hydra$
>>
>>
>> So what does that mean ? I *must* use GCC to compile this source ?
>
> It means that the sources use a GNU extension that configure has
> detected that Clang does not properly implement.  The specific example
> cited ("aligned") should be non-critical for you, since you are running
> on AMD64 and that architecture does not actually require proper
> alignment.  The resultant executables should work in your case, but at
> reduced performance (unaligned accesses are permitted on x86-64, but are
> slower than aligned accesses) unless SSE (which *does* have hard
> alignment requirements) is used.  Since I note that you are disabling
> the use of assembler modules, SSE will probably *not* be used in your
> executable.
>
> In short, try it---if it works for you, great!  If GPG crashes with
> SIGBUS, try rebuilding it with GCC before reporting a bug in GPG.  If it
> works when built with GCC, you have found a bug (a missing feature that
> Clang claims to have) in Clang.  Clang typically defines __GNUC__, thus
> claiming to support GNU extensions, so this is a bug in Clang if your
> Clang-compiled GPG does not work.
>
>
> -- Jacob
>

Wonderful! Thank you for the detailed reply as well as the comfort that
this should "just work"(tm) or not. I did disable the asm goodies as I
wanted to easily ( trivially? ) be able to single step around in there
with gdb.

So then, phasers on stun and I will go forth with reckless abandon and
see what dumps core and SIGSEGBEER. Or not.



--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
Belt and suspenders suggested.


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Strange message seen on FreeBSD 14.0 amd64 [ In reply to ]
Am Mittwoch 12 Juli 2023 10:39:29 schrieb Dennis Clarke via Gnupg-users:
>  Thank you for the detailed reply as well as the comfort that
> this should "just work"(tm) or not.

On gnupg-devel, Niibe wrote that Clang 16 works for him
asking for the version of clang that may have given you issues:

https://lists.gnupg.org/pipermail/gnupg-devel/2023-July/035390.html

Bernhard

--
https://intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter