Support Bitrig, an OpenBSD fork

The following patch allows Tor to recognize Bitrig, an OpenBSD fork.

Trac:
Username: dhill

changed milestone to %Tor: 0.2.4.x-final

added component::core tor/tor milestone::Tor: 0.2.4.x-final priority::low reporter::dhill resolution::implemented status::closed tor-relay type::enhancement labels

Trac:
Username: dhill

tor-bitrig.diff

Bitrig patch

Trac:
Username: dhill

I wonder if it might not make just as much sense to open bugs in the Bitrig bugtracker: "Make the system headers buildable with -Wredundant-decls" and "Add a s6_addr16 to in6_addr": Doing that would solve not only the build issue with Tor, but with various other projects as well.

(I'm cool with applying that part if bitrig can't fix their problems there.)

Certainly, the libevent workaround should be unneeded: if bitrig is shipping Libevent 1.3b, that would be really weird.

Trac:
Component: - Select a component to Tor Relay
Priority: normal to minor
Milestone: N/A to Tor: 0.2.4.x-final

Trac:
Status: new to needs_review

Why does Bitrig not define __OpenBSD__?

Trac:
Keywords: N/A deleted, tor-relay added

Trac:
Component: Tor Relay to Tor

Trac:
Status: needs_review to needs_information

Replying to rransom:

Why does Bitrig not define __OpenBSD__?

It currently does, but may not in the future.

Trac:
Username: dhill

Replying to nickm:

I wonder if it might not make just as much sense to open bugs in the Bitrig bugtracker: "Make the system headers buildable with -Wredundant-decls" and "Add a s6_addr16 to in6_addr": Doing that would solve not only the build issue with Tor, but with various other projects as well.

(I'm cool with applying that part if bitrig can't fix their problems there.)

Certainly, the libevent workaround should be unneeded: if bitrig is shipping Libevent 1.3b, that would be really weird.

I have changed the tor package to build against libevent2, so the workaround is not really needed.

If you want to exclude those source changes, but just do the configure* patches, that should be sufficient for now, since currently, Bitrig does indeed define OpenBSD

Trac:
Username: dhill
Status: needs_information to new

Okay, merged the configure.ac part of the patch as d92d3f33356af002892ba5754d9d36cc4504c95f. Thanks!

Trac:
Status: new to closed
Resolution: N/A to implemented

closed

mentioned in issue #20980 (moved)

mentioned in issue #28938 (moved)

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

mentioned in issue tpo/core/tor#28938 (closed)