tor-0.3.4.5-rc: fails to build when configured with `./configure --disable-unittests`

When configuring tor-0.3.4.5-rc with --disable-unittests the build fails with

make all-am make[1]: Entering directory '/var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc' CCLD src/test/test-bt-cl src/test/src_test_test_bt_cl-test_bt_cl.o: In function `crash': /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:43: undefined reference to `tor_assertion_failed_' src/test/src_test_test_bt_cl-test_bt_cl.o: In function `main': /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:107: undefined reference to `init_logging' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:108: undefined reference to `set_log_severity_config' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:109: undefined reference to `add_stream_log' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:110: undefined reference to `tor_log_update_sigsafe_err_fds' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:112: undefined reference to `configure_backtrace_handler' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:116: undefined reference to `clean_up_backtrace_handler' /var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc/src/test/test_bt_cl.c:117: undefined reference to `logs_free_all' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:5219: src/test/test-bt-cl] Error 1 make[1]: Leaving directory '/var/tmp/portage/net-vpn/tor-0.3.4.5_rc/work/tor-0.3.4.5-rc' make: *** [Makefile:3468: all] Error 2

This regression was introduced after 0.3.4.2_alpha.

changed milestone to %Tor: 0.3.4.x-final

added 034-must component::core tor/tor milestone::Tor: 0.3.4.x-final owner::rl1987 parent::26789 priority::medium regression resolution::duplicate severity::normal status::closed type::defect labels

Trac:
Keywords: N/A deleted, 034-must regression added
Component: - Select a component to Core Tor/Tor
Milestone: N/A to Tor: 0.3.4.x-final

commit b7fae0f48 was bisected to be the first bad commit between 0.3.4.2-alpha and 0.3.4.3-alpha which caused this issue.

Possible duplicate of #26789 (moved)?

Sorry, I must have missed #26789 (moved). It does indeed look like a duplicate.

Trac:
Status: new to accepted
Owner: N/A to rl1987

Duplicate of #26789 (moved)

Trac:
Parent: N/A to #26789 (moved)
Resolution: N/A to duplicate
Status: accepted to closed

closed

moved to tpo/core/tor#26792 (closed)