Hi,
I have forked repos
Changed Makefile
NAME?= myfirewall
Changed in Core
Changed Makefile
NAME?= myfirewall
Getting Error
--- relayd ---
cc -lpfctl -Wl,-rpath,/usr/local/lib -fstack-protector-strong -L/usr/local/lib -pthread -o relayd parse.o ca.o check_icmp.o check_script.o check_tcp.o check_tls.o config.o control.o hce.o log.o name2id.o pfe.o pfe_filter.o proc.o relay.o relay_http.o relay_udp.o relayd.o shuffle.o ssl.o util.o siphash.o /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin/relayd/../../lib/libevent/libevent.a /usr/obj/usr/ports/security/libressl/work-default/stage/usr/local/lib/libtls.a /usr/obj/usr/ports/security/libressl/work-default/stage/usr/local/lib/libssl.a /usr/obj/usr/ports/security/libressl/work-default/stage/usr/local/lib/libcrypto.a /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin/relayd/../../lib/libutil/libutil.a -lmd
ld: error: undefined symbol: ENGINE_get_RSA
>>> referenced by ca.c
>>> ca.o:(ca_engine_init)
ld: error: undefined symbol: ENGINE_set_RSA
>>> referenced by ca.c
>>> ca.o:(ca_engine_init)
ld: error: undefined symbol: ENGINE_set_name
>>> referenced by ca.c
>>> ca.o:(ca_engine_init)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** [relayd] Error code 1
make[3]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin/relayd
1 error
make[3]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin/relayd
===> usr.sbin/relayctl
*** [all] Error code 6
make[2]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin
1 error
make[2]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5/usr.sbin
*** [all] Error code 2
make[1]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5
1 error
make[1]: stopped in /usr/obj/usr/ports/net/relayd/work/relayd-7.3.2023.05.09-p5
[20231111141443] ===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make: stopped in /usr/ports/net/relayd
Creating repository in /usr/obj/usr/tools/config/23.7/amd64/.pkg-new/: 100%
Packing files for repository: 100%
>>> Removing packages set
>>> Creating package mirror set for ddd181f2c06239392f5d16307351f08842e9345a-amd64... done
-rw-r--r-- 1 root wheel 939M Nov 11 19:44 packages-ddd181f2c06239392f5d16307351f08842e9345a-amd64.tar
>>> WARNING: The build provided additional info.
>>> Rebuilt version 3.2.1_1 for net-mgmt/nrpe3 (nrpe3)
>>> ERROR: The build encountered fatal issues!
>>> Aborted version 7.3.2023.05.09.p5 for net/relayd (relayd)
*** Error code 1
Stop.
make: stopped in /usr/tools
Please help to resolve the same.
make info output
root@build:/usr/tools # make info
tools /usr/tools be8a5001f5d957601c1407861ac45db9c8e363e8 be8a5001f master
src /usr/src 23.7.8_3 cc48f7c15 stable/23.7
ports /usr/ports ddd181f2c06239392f5d16307351f08842e9345a ddd181f2c master
[/color]plugins /usr/plugins 23.7.8 44fc38acc stable/23.7
core /usr/core 23.7.8_1 7b7bebee4 stable/23.7
root@build:/usr/tools #
set folder package file name
packages-ddd181f2c06239392f5d16307351f08842e9345a-amd64.tar
Had a similar issue a few days ago. Just retried that portion of the build and it progressed to completion.
Try building again.
Relayd was (ironically) broken by libressl update. Both come from OpenBSD ;)
For now I've rolled back the libressl update, but the situation isn't ideal.
Cheers,
Franco
Similar problem building nut 2.8.0_24:
configure: error: could not enable GSSAPI support
[20231120123557] ===> Script "configure" failed unexpectedly.
Please report the problem to lev@FreeBSD.org [maintainer] and attach the
"/usr/obj/usr/ports/www/neon/work/neon-0.32.5/config.log" including the output
of the failure of your make command. Also, it might be a good idea to provide
an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1
You need to keep up with ports.git and tools.git...
https://github.com/opnsense/tools/commit/4c456ac83
Cheers,
Franco
Thanks. New tothis building process, I copied the 23.7 config folder to a new one labeled 24.1
Need to attention to changes to the 23.7 folder. Is there a better way to stay current?
Ron
Git pull before you start to work on anything?
24.1 folder hasn't been created yet, but will be once kernel changes have been merged to a new stable/24.1 branch. For now I'm building all from 23.7 config with manual modifications. Most notably SSL=openssl for OpenSSL 3 buils.
Why are you building "24.1"? Maybe I can clear something up :)
Cheers,
Franco
I do git pulls regularly, but the config folder under tools that i was using wasn't tracking the changes in 23.7. Maybe I'll change to local commits to 23.7.
Was just tying to track the development phase, originally had labeled the config folder "Future", but one of the build phases complained that it wasn't compliant with the MM.m format. So Just picked the next release number :-).
I see. Normally no need to make a copy unless you want to modify something? There are .local files for plugins.conf and build.conf -- one for ports.conf was never needed but could be. Everything can be passed from the make command invoke too.
Happy to make further improvements to the build tools. Discussing "integration" issues is the first step. :)
Or you could also use CONFIGDIR to point to a local copy outside of the tools.git repo if none of this works for you (which could also be "23.7" then).
Cheers,
Franco