I am now creating new DansGuardian and Squid3 binaries.

aaronouthier

JimP,

I can try that, but as I was using the FreeBSD "ports" repo for testing, there is no ./configure file until after running make. In this scenario, "make install" is the only command needed, and that creates the "configure" program, adds the build options, configures, compiles, and links the program and all requisite libraries. This makes it easy and convenient to build, but not so easy to pass configure options to somebody else. I guess I'll try to build from official Squid source, but keep in mind, that that source doesn't have all of the FreeBSD 10 specific patches and compatibility testing which is included in the Ports repo.

Stay tuned.

jimp

The build options in the xml are the build options from freebsd ports, not configure. You can also see them in /var/db/ports/<portname>/options, where portname is xxx_yyy, xxx = the ports category, yyy being the port name, such as www_squid</portname>

aaronouthier

Interesting. Good to know! I'll check that in the morning.

aaronouthier

Sorry for the silence this weekend. My computer was having video issues on Friday. On Saturday, I made some new VMs, based on FreeBSD 10.2 RC1, instead of Beta 3 as before. Build process is erroring-out on glib20, while running "make" in "/usr/ports/ports-mgmt/". I am unable to compile and install the updated "pkg" binary, which is required by the rest of the ports repo. This is occurring in both amd64 and i386 versions. I'll update "ports" tomorrow and try again, to see if this is fixed.

Thank you for your continued patience.

jimp

pkg can be a little odd to upgrade sometimes, but it usually prints instructions about it when it fails.

try this:

pkg delete -f pkg; cd /usr/ports/ports-mgmt/pkg; env UPGRADEPKG=1 make clean install clean

aaronouthier

@Jimp: No, I don't think that's it. I am having no end of headaches with ports on RC1. Things that worked without issues. Squid, Avahi, pkg, and more are constantly getting stuck while building dependencies. It is not happening during install phase. Also, the same errors are occurring in the same places on both i386 and amd64 builds. Everything from "aclocal 1.13 missing", to missing dependencies during configure, because they are supposed to be compiled ahead of time, but aren't. None of this was happening with beta 3. The fix has always been to look at the logs and figure out where the process is breaking down and cd to that location and "make clean && make install". Compiling squid alone took more than 3 hours, and I had to manually build about 20 different dependencies. Every time I'd fix one thing, something else further down the line would fail.

I then spend just under 4 hours on Avahi before calling it a night. Going to try to finish up in a few minutes.

All of this was with a fresh, clean install of freebsd 10.1 - not an upgrade or install over-the-top of the existing.

jimp

Strange, I haven't used an RC yet myself, my workstation is on a late beta, but there were a ton of updates to ports over the last couple weeks.

When all else fails, pkg delete -fa, and start over with a fresh ports tree (portsnap fetch extract)

aaronouthier

I've been trying to resolve them manually. That said, I just did a portsnap fetch and portsnap update, followed closely behind by a few _make distclean_s. Portsnap fetch grabbed over 200 patches to my existing tree. Crossing my fingers…

aaronouthier

Yeah, going to start with a new ports install. Running rm -rf /usr/ports now. Just ran pkg delete -fa a moment ago. Thanks for that, by the way. I didn't previously know I could force remove all pkgs! I'm assuming that's what is meant by -fa (force all).

aaronouthier

I'm back on the case.

FreeBSD was updated to RC2 on Friday. I had some things going over the weekend. It's now about midnight Monday morning. GTG.

dooldeniya

Aaron - Thanks for working on this. Any update on progress. I am looking to install and would appreciate any guidance you can provide.
-Chanaka

aaronouthier

Actually, I've stopped working on this, as the original maintainer of squid and DansGuardian, namely user MarcelloC, managed to find the time to update them about a month ago. I assume you're having trouble? If so, you're in the right place… (Pfsense forums).

rjcrowder

@aaronouthier:

Actually, I've stopped working on this, as the original maintainer of squid and DansGuardian, namely user MarcelloC, managed to find the time to update them about a month ago. I assume you're having trouble? If so, you're in the right place… (Pfsense forums).

That's awesome news… so now the normal Squid3 and DG packages should work under 2.2?

Cino

Do you know where he updated them too?

I checked github for php/inc file changes: squid3 hasn't been updated in 2 months, Dansguardian 5 months.

binary changes:
Checked http://files.pfsense.org/packages/8/All/
dansguardian-2.12.0.3_2-i386.pbi 23-Jun-2014 13:57 19952423
squid-3.3.10-i386.pbi 26-Nov-2013 20:06 17598644

Checked http://files.pfsense.org/packages/10/All/
dansguardian-2.12.0.3_2-i386.pbi 27-Jun-2014 03:42 16177170
squid-3.3.11-i386.pbi 22-Apr-2014 12:12 17568448
squid-3.3.11_1-i386.pbi 17-Jul-2014 22:26 17702572

amd64 pbi have the same dates

aaronouthier

Ok. I did some more checking, and, now I'm not sure who updated it, or when. I just know that around October 15 or so, I reinstalled my box, and everything worked, whereas a fresh install previously didn't work right without some modifications.

Also, note that I am using squid3-dev, not regular squid3, and I am running it on the 2.2 beta, not the 2.1.x stable.

jbc

I have a fresh install of 2.2-BETA (amd64) built on Mon Oct 27 15:31:41 CDT 2014 FreeBSD 10.1-RC3
If I install squid3-dev beta 3.3.11_1 pkg 2.2.7 platform: 2.2 - I've never managed to start it.

On the previous install, I tried installing libraries it complained were missing ect. to see if I could get it up,
but eventually I gave up, and reinstalled from scratch.

Would you mind sharing which versions you're running?

Thanks in advanced.

Escorpiom

More or less the same situation here, I'm running 2.2 beta snapshot and tried to install Squid 3.3.11_1 pkg 2.2.7, it wouldn't start.
I used the workaround described elsewhere on this forum, and now it runs.
Downside is that the "workaround" (console commandos) have to be entered again after each update.

So it's either "do not update" or "workaround".

For my purposes, Squid proxy (and if possible with ad blocking) is really a must-have.
I'm not a programmer, but can test packages if needed.
Please keep up the effort.

Cheers.

aaronouthier

Hmm. Not sure what happened. I just did a fresh reinstall myself. Squid now segfaults upon launch with core dump. This is with the official versions of everything. Nothing was custom-compiled or copied from another box. Amd64 build. I don't know what to say.

Escorpiom

Exactly.
It did that on my box also, but it turned out to be the cache filesystem.
If you set it to "aufs", Squid will complain.
Leaving it at "ufs" (default) and it runs.

I have found a way to block ads with the help of a regex list added to Squid, and that works fine.
So for now, all is dandy. No updates though.

Cheers.

aaronouthier

Well, I am having some frustrating issues. I have gotten squid to compile just fine, but when I do amake install, it hangs with a series of```
lstat: file not found