Search results

Then the answer is simple: use RELENG_8_1 (8.1-RELEASE + security patches).

Are you sure you want to run -STABLE. Stable here means "stable in terms of ABI stability", and doesn't describe how stable it actually is. You might want to run -RELEASE if that's what you are after. re original question: -STABLE (RELENG_8 in this case) is a moving target, from which releases...

Opens instantly in FF 3.6.11 (machine has 16Gb of RAM though) :)

ports/www/chromium/Makefile: USE_GNOME= glib20 gtk20 gconf2 You could try removing gconf2 from that line and see how badly it will be broken without it :)

Check if you are keeping needed environment variables in your sudoers (it should contain examples of such variables, by default).

You should use RAW_VALUE for Temperature_Celsius, which is pretty low. JFYI.

Can't see anything about extracting in your paste. Could you try running make clean and then make and paste the result if it errors?

You can avoid installing xorg and nvidia-driver in chroot, you only need libs from nvidia-driver tarball.

fs version is v3, pool version is v14 in HEAD and there are patches for v16 posted by Martin Matuška on current@.

Are you sure you don't have proxy settings configured somewhere? Still worth a check... Check /usr/bin/env output for any proxy related settings.

http://lists.freebsd.org/pipermail/freebsd-gnome/2010-July/024566.html

You could create 32bit chroot environment as described in http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d and try building it there.

Post your problem with your current findings to gnome@ mailing list, you should get a quicker and more correct replies there.

You could try searching http://bugzilla.gnome.org for similar problem reports. Doesn't look like library issue at all.

/var/log/Xorg.0.log would be useful here.

Check this thread as well: http://lists.freebsd.org/pipermail/freebsd-hackers/2010-June/032210.html

Yes, http://lists.freebsd.org/pipermail/freebsd-stable/2010-July/057552.html

getloadavg

Why - different ports need different versions of automake to build. devel/automake* ports are mostly build-time only dependencies. You should use pkg_info -R to check which ports depend on the port you specify.

You'll need to set HTTP_USER_AGENT for /usr/bin/fetch to report something useful. From fetch: HTTP_USER_AGENT Specifies the User-Agent string to use for HTTP requests. This can be useful when working with HTTP origin or proxy servers...