Bug 259383 - security/openssl: 1.0.1h fails to build: error: use of undeclared identifier 'CRIOGET' on FreeBSD 13 (Non-ports build)
Summary: security/openssl: 1.0.1h fails to build: error: use of undeclared identifier ...
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Kubilay Kocak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-23 14:57 UTC by bycn82
Modified: 2021-10-24 01:23 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bycn82 2021-10-23 14:57:11 UTC
# Failed to compile the openssl from the source code failed on FreeBSD 13

This is not about the ports since i am downloading the source code directly from the openssl.org, and it works on FreeBSD 12, but failed on FreeBSD 13. below are the steps.


# uname -a
FreeBSD web 13.0-RELEASE FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr  9 04:24:09 UTC 2021     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

# below are the steps
## download the source code
https://www.openssl.org/source/old/1.0.1/openssl-1.0.1h.tar.gz

## configure and compile
./config BSD-x86_64/cc
make

## rrror message
eng_cryptodev.c:202:16: error: use of undeclared identifier 'CRIOGET'
        if (ioctl(fd, CRIOGET, &retfd) == -1)
                      ^
eng_cryptodev.c:973:9: error: assigning to 'u_int8_t' (aka 'unsigned char') from incompatible type 'void'
                pd[i] = crp->crp_p[bytes - i - 1];
                      ^ ~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors generated.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-10-24 01:23:04 UTC
Thank you for your report. For upstream (direct) builds, please report any issues upstream. FreeBSD can only provide support for software packages provided by, or in FreeBSD base versions and ports or packages.

If 1.0.1h is provided with any supported (not End-of-Life) versions of FreeBSD and the issue is reproducible in that version, please don't hesitate to re-open this issue with additional information, reproduction environment and steps to reproduce.