Ticket #632 (closed enhancement: fixed)
Opened 3 years ago
Last modified 8 months ago
Add Privoxy
| Reported by: | simonsouth | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | |
| Severity: | normal | Keywords: | privoxy |
| Cc: |
Description
" Privoxy is a non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk."
These files build on work by Thomas Turney and improve upon an earlier submission by
- Building the latest stable revision, 3.0.19
- Using Haiku's own pthreads implementation rather than disabling it altogether, which degrades performance (the patch to configure.in makes this work)
- Using Haiku's PCRE implementation during the build process rather than simply disabling this step
- Specifying installation directories more precisely so all files are installed in sensible locations under /boot/common
Gentoo-Portage categorizes Privoxy under net-proxy, which doesn't exist yet in the repository.
Attachments
Change History
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.bep added
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.patch added
comment:1 Changed 3 years ago by scottmc
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.2.bep added
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.2.patch added
comment:2 Changed 3 years ago by simonsouth
Done. This new patch adds a "Haiku specific" section like you suggested, and modifies a test earlier on that detects single-user host OSes. The LDFLAGS, --with-user and --with-group options have all been removed from the call to configure and Privoxy builds as before.
Yes, I've tried building with gcc2 and compilation fails with an odd error message ( the same one Thomas saw). I can dig a bit deeper, although I'm not really sure where to start there since the code looks fine to me. Can you offer any suggestions?
comment:3 Changed 3 years ago by scottmc
For parse errors when trying to build with gcc2 check near the line that is reported as failing and it's typically someone declared a variable after setting the value of an earlier one. Try moving to variable declaration up in the code block and see if the error goes away. This is how to fix many gcc2 issues... if there's only a few of these it's usually not too bad to patch them all up. But for newer programs where the developer just did this everywhere in their program is can be a bit more annoying to try and fix.
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.3.bep added
Changed 3 years ago by simonsouth
- attachment privoxy-3.0.19.3.patch added
comment:4 Changed 3 years ago by simonsouth
Yep, that was it. After moving a handful of declarations in filters.c I now have Privoxy building with both GCC 2 and GCC 4. I haven't tested them extensively but both builds appear to work fine. Consequently I've removed the warning message from the BEP file.
Additionally I've tidied up the "Haiku specific" portion of configure.in and added comments. Please let me know what you think.
comment:5 Changed 3 years ago by simonsouth
Scott, do have any feedback for me on this? If the patch is acceptable I'd like to submit it to the Privoxy maintainers as well.
comment:6 Changed 23 months ago by disreali
This should have been added and upstreamed a year ago when we had someone interested in maintaining it. Privoxy is now at 3.0.21.
comment:7 Changed 8 months ago by scottmc
- Resolution set to fixed
- Status changed from new to closed
marking this as fixed, but it still needs a proper working .recipe file now, but that can be handled on the new site.

maybe try patching to add -lnetwork into configure.in perhaps near line 600 like was done with solaris and others...
http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/configure.in?revision=1.167&view=markup
and try building it without the LDFLAGS and see if that has any effects, seems we haven't had to use that very much recently.
Otherwise looks pretty good.
Did you try it on gcc2 and gcc4?