Menu
▾
▴
[privoxy-users] [ ijbswa-Support Requests-1073265 ] Compiled with FORCE?
|
From: SourceForge.net <no...@so...> - 2004-11-30 09:39:57
|
Support Requests item #1073265, was opened at 2004-11-25 08:11 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=1073265&group_id=11118 Category: blocking Group: 3.0.x Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Compiled with FORCE? Initial Comment: Hiya, I've downloaded the Win32 version 3.0.3 of Privoxy and have noticed that it allows clients to proceed to blocked content regardless, simplying by clicking on "go there anyway" on the blocked page. As this is apparently a compile option, is there any way to disable this after installation? A filter that allows users to bypass it is not a lot of use, all said and done :( Many thanks, Paul ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-30 01:39 Message: Logged In: NO Brian, Many thanks for your reply - I appreciate you taking the time to write back. I also appreciate the whole thing about "microSuck" and I haven't enable it in my config files - I just took it as a guide to how the Privoxy team look upon Microsoft and their users... As far as your instructions go, again my thanks for your time and efforts, but I'm no better informed than I was before, I'm afraid. I have installed CygWin and ended up with a bash shell I can run under Windows - all well and good, but what do you mean by "make sure you include autoconf, automake, make, gcc, and gcc-mingw in addition to the base packages" I can see the list of packegs to be included in the CygWin installation, but these don't include any of the packges you mention. I can download the packages you mention from their various sites, but how do I then include them into CygWin? My experience with Unix is limited to say the least and I think compiling an executable from source is going to be the very limit of my ability with it, so any help you can give me will be very much appreciated. Many thanks, Paul ---------------------------------------------------------------------- Comment By: Brian (dessent) Date: 2004-11-29 21:26 Message: Logged In: YES user_id=585719 cygwin.COM not cygwin.org, sorry. ---------------------------------------------------------------------- Comment By: Brian (dessent) Date: 2004-11-29 21:25 Message: Logged In: YES user_id=585719 Re: the "microsuck" thing, that is in a filter that is never enabled unless you change the config and explicitly enable it (or enable the "adventuresome" action which is described as "risky") so the people that bitch about it need to stop fiddling with things they don't understand. Re: compiling win32, here are the steps - Install cygwin using setup.exe from cygwin.org. Make sure you include autoconf, automake, make, gcc, and gcc-mingw in addition to the base packages. - Download the source tarball, follow the instruction in section 2.2 "building from source". You can skip the part about "su". You must include "--enable-mingw32" if you want the win32 GUI version. Otherwise you get the cygwin version which is a console mode daemon just like *nix. Include whatever additional configure options you desire. $ autoheader && autoconf && ./configure --enable-mingw32 --disable-force && make You should then have a privoxy.exe after all that churns for a while. You probably want to run strip on it, and then copy it over the .exe that the installer placed under program files. ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2004-11-29 14:30 Message: Logged In: YES user_id=322640 Sorry this is a problem. I think the reasons are mostly that we have many more Linux/Unix users than MS, and those respective platforms have significantly different methodologies for installing software. For instance, custom compiling is not commonly done on MS, and is on *nix platforms. Therefore I doubt we have many MS users trying out these type of options, and consequently not much of a knowledge base to draw upon. If I knew the answer, I'd certainly give it out. I've used Privoxy on Win, but never tried building from source, unfortunately. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-29 06:28 Message: Logged In: NO Hello again, Having hunted through this archive of posts, I see that I'm not the first "Microsuck" user to come up against this problem. I guess that's why there's been no reply to this posting... Fair enough, I can see where you're coming from releasing the W32 version of Privoxy so that it's pretty much useless to Windows users, but could I ask that you go into a little more detail regarding the methodology of recompiling Privoxy from source without the FORCE flag set? I've finally managed to download, install, configure or otherwise set up the various packages you say are vital (gnuMake, autoconf and gcc) but your instructions are pretty vague beyond that... Any help you feel you can give will be much appreciated - this looks like a very good product and I would love to use it, but am being hampered by this apparent hostility towards Windows users... Regards, Paul ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=1073265&group_id=11118 |