Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to compile tor 0.3.5.3-alpha #10

Closed
wants to merge 1 commit into from
Closed

Changes to compile tor 0.3.5.3-alpha #10

wants to merge 1 commit into from

Conversation

dballard
Copy link

@dballard dballard commented Nov 2, 2018

Addressing issue #9 this is a proposal, the changes needed to make 0.3.5.3-alpha be supported

Granted support for an alpha version may not be desired at this moment, but this work should carry forward and be relevant to when 0.3.5.* stabilizes so I'm PRing this now so it can go quickly at your discretion.

Thanks!

@n8fr8
Copy link
Member

n8fr8 commented Nov 2, 2018

Fantastic! No reason not to support alpha builds, since we need to be able to test some of the improvements in memory use and other mobile optimizations coming in newer releases. Will test this out in the coming days.

@@ -253,6 +253,7 @@ tor/configure:

tor/Makefile: tor/configure
cp config.sub tor
sed -i '14i #include <errno.h>' tor/src/lib/fs/freespace.c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is merely a workaround for a bug in tor we should maybe report this and remove it once it has been fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a fix on its way (see the ticket) so I think we should wait for the next alpha and remove this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good to me

@goapunk
Copy link
Contributor

goapunk commented Feb 5, 2019

As @n8fr8 applied the necessary changes (afaik) I think we can close this MR and the related issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants