Postfix file ownership problem
Why do I get this error about files with wrong ownership? Tried reinstalling, but it did not help... # /usr/local/etc/rc.d/postfix restart postfix/postfix-script: stopping the Postfix mail system postfix/postfix-script: warning: not owned by group maildrop: /usr/local/sbin/postqueue postfix/postfix-script: warning: not owned by group maildrop: /usr/local/sbin/postdrop postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/local/sbin/postqueue postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /usr/local/sbin/postdrop postfix/postfix-script: starting the Postfix mail system $ pkg info|grep -i postfix postfix-2.11.1_4,1 Secure alternative to widely-used Sendmail postfix-base-2.12.20140709_2,4 Secure alternative to widely-used Sendmail $ uname -a FreeBSD core2.grimstveit.no 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #1 r271669: Tue Sep 16 12:23:45 CEST 2014 r...@core2.grimstveit.no:/usr/obj/usr/src/sys/CORE2 amd64 -- Vyrdsamt, Jakob Breivik Grimstveit | +47 4829 8152 http://grimstveit.no/jakob ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/dansguardian revival?
On Mon, 20 Oct 2014 17:47:19 -0700 Chris H bsd-li...@bsdforge.com wrote: Unless theirs any objection. I'll take it. I'll open a pr(1) with a shar(1) ready, in about an hour. --Chris Nice to hear that dansguardian will be back in ports. I also used it for years in combination with www/squid33 without problem. I was compiling it from ports, and the trick was to compile squid33 first, and dansguardian only after, as dansguardian would only check existence of /use/local/bin/squid, and if it was already there, no matter which version, it would happily compile, install and work. -- Marko Cupać https://www.mimar.rs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/aureal-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=aureal-kmod portname: audio/cowbell broken because: No more public distfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=cowbell portname: audio/firefly broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=firefly portname: audio/qmidinet broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=qmidinet portname: audio/raproxy broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: audio/xmms-openspc broken because: does not build on FreeBSD 10.x and later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=xmms-openspc portname: cad/cider broken because: Will not build with bmake and USES=fmake will not solve the issue build errors: http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/latest/logs/errors/cider-1.b1_7.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=cider portname: databases/freetds-devel broken because: Fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=freetds-devel portname: databases/gtksql broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gtksql portname: databases/mariadb-client broken because: Does not build under FreeBSD 10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mariadb-client portname: databases/mariadb-server broken because: Does not build under FreeBSD 10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mariadb-server portname: databases/py-fdb broken because: Does not compile on FreeBSD 9 i386 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=py-fdb portname: databases/pydbdesigner broken because: Needs an unsupported version of wxWidgets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=pydbdesigner portname: databases/tora broken because: Does not compile
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/cowbell broken because: No more public distfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=cowbell portname: audio/raproxy broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=raproxy portname: audio/wmauda broken because: Does not work with audacious 3.5 or later build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=wmauda portname: audio/x11amp broken because: hangs at start with gtk and linker errors build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=x11amp portname: cad/cider broken because: Will not build with bmake and USES=fmake will not solve the issue build errors: http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/latest/logs/errors/cider-1.b1_7.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=cider portname: databases/gtksql broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gtksql portname: databases/tora broken because: Does not compile with clang (include list) build errors: http://beefy2.isc.freebsd.org/bulk/10amd64-quarterly/latest/logs/errors/tora-2.1.3_5,1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=tora portname: devel/fsmgenerator broken because: Fails to link build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=fsmgenerator portname: emulators/linux_base-gentoo-stage3 broken because: Fails to package build errors: http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/latest/logs/errors/linux_base-gentoo-stage3-20121213.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-gentoo-stage3 portname: emulators/linux_dist-gentoo-stage3 broken because: Fails to package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_dist-gentoo-stage3 portname: ftp/rexx-curl broken because: Fails to install/package with new rexx-regina build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftpportname=rexx-curl portname: games/wmfortune broken because: No public disfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=wmfortune portname: graphics/gnash broken because: unable to link in libboost_system build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=gnash portname: graphics/xfpovray broken because: Fails to link build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=xfpovray portname: net/slirp broken because: Does not build build errors: none. overview:
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: biology/boinc-simap description:Similarity Matrix of Proteins project for BOINC maintainer: po...@freebsd.org deprecated because: Project shutting down, see http://boincsimap.org/boincsimap/forum_thread.php?id=88 expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=boinc-simap portname: deskutils/babytrans description:GTK+/GNOME front-end for Babylon Translator .dic files maintainer: po...@freebsd.org deprecated because: Abandonware, dictionaries unavailable expiration date:2014-10-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=babytrans portname: devel/creduce description:Produces small test cases maintainer: po...@freebsd.org deprecated because: Unmaintained and depends on ancient LLVM 3.2 expiration date:2014-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=creduce portname: lang/clay description:Language designed for generic programming maintainer: po...@freebsd.org deprecated because: No development since July 2013, depends on obsolete clang-3.2 expiration date:2014-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=clay portname: math/elmer-umfpack description:UMFPACK library used by ELMER FEM package maintainer: po...@freebsd.org deprecated because: Obsoleted by cad/elmerfem expiration date:2014-11-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mathportname=elmer-umfpack portname: net/slirp description:(C)SLIP/PPP emulator for users with shell accounts maintainer: po...@freebsd.org status: BROKEN deprecated because: Broken for more than 6 months expiration date:2014-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=slirp portname: science/elmer-eio description:ELMER FEM Package Data base Interface maintainer: po...@freebsd.org deprecated because: Obsoleted by cad/elmerfem expiration date:2014-11-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=scienceportname=elmer-eio portname: science/elmer-matc description:MatC language library used by ELMER FEM package maintainer: po...@freebsd.org deprecated because: Obsoleted by cad/elmerfem expiration date:2014-11-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=scienceportname=elmer-matc portname: science/elmer-meshgen2d description:Mesh Generation Utility for use with the ELMER FEM package maintainer: po...@freebsd.org deprecated because: Obsoleted by cad/elmerfem expiration date:2014-11-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=scienceportname=elmer-meshgen2d portname: science/elmergrid description:Mesh Manipulation Utility for use with the ELMER FEM package maintainer: po...@freebsd.org deprecated because: Obsoleted by cad/elmerfem expiration date:2014-11-07 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=scienceportname=elmergrid portname: textproc/sxml description:Skimpy XML parsing and grafting library for C language maintainer: po...@freebsd.org deprecated because: expiration date:2014-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textprocportname=sxml portname: www/rt38 description:RT is an industrial-grade ticketing system written in Perl maintainer: po...@freebsd.org status: BROKEN deprecated because: Has expired: End of Life March 2014 expiration date:2014-10-31
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=dante portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/cuberok description:Music player and collection manager based on Qt4 maintainer: v...@freebsd.org deprecated because: Upstream development has stalled expiration date:2014-11-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=cuberok portname: biology/boinc-simap description:Similarity Matrix of Proteins project for BOINC maintainer: po...@freebsd.org deprecated because: Project shutting down, see http://boincsimap.org/boincsimap/forum_thread.php?id=88 expiration date:2015-01-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=boinc-simap portname: databases/db48 description:The Berkeley DB package, revision 4.8 maintainer: mand...@freebsd.org deprecated because: Please migrate to db5 or db6 expiration date:2014-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=db48 portname: databases/memcachedb description:Distributed storage system designed for persistence maintainer: k...@stereochro.me deprecated because: Depends on deprecated Berkeley DB version, needs porting to DB_SITE expiration date:2014-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=memcachedb portname: deskutils/babytrans description:GTK+/GNOME front-end for Babylon Translator .dic files maintainer: po...@freebsd.org deprecated because: Abandonware, dictionaries unavailable expiration date:2014-10-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=babytrans portname: devel/creduce description:Produces small test cases maintainer: po...@freebsd.org deprecated because: Unmaintained and depends on ancient LLVM 3.2 expiration date:2014-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=creduce portname: devel/ocaml-equeue description:The Equeue library for OCaml maintainer: michip...@gmail.com deprecated because: Superseded by www/ocaml-net expiration date:2015-08-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ocaml-equeue portname: dns/bind10 description:Development version of ISC BIND 10 DNS Suite maintainer: m...@freebsd.org status: IGNORE deprecated because: Is not developed any more, use dns/bundy expiration date:2015-12-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=bind10 portname: dns/bind98 description:BIND DNS suite with updated DNSSEC and DNS64 maintainer: m...@freebsd.org deprecated because: Will be EOL as of September 2014. expiration date:2014-09-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=bind98 portname: dns/maradns1 description:DNS server with focus on security and simplicity maintainer: m...@freebsd.org deprecated because: MaraDNS 1 end-of-life: June 21, 2015, use dns/maradns expiration date:2015-06-21 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=maradns1 portname: editors/emacs23 description:GNU editing macros maintainer: ash...@freebsd.org deprecated because: Unmaintained upstream, use editors/emacs expiration date:2014-11-19 build errors: http://beefy2.isc.freebsd.org/bulk/head-amd64-default/latest/logs/errors/emacs23-23.4_4,1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=editorsportname=emacs23 portname: lang/clay description:Language designed for generic programming maintainer: po...@freebsd.org deprecated because: No development since July 2013, depends on obsolete
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/omniORB-4.1 | 4.1.7 | 4.2.0 +-+ mail/postfix210 | 2.10.5 | 2.11.0 +-+ textproc/py-jaxml | 3.02| 17.00 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
from Edward Shriver
How are you? http://conceitoeng.com.br/occasion/afternoon.php Edward Shriver ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
PORTVERSION when there is no upstream version number
Hi, what is the best practice for setting PORTVERSION, when the upstream port has no version number? Is it fine to go with the date like 20141021? I'm trying to port postscreen-stats, which is just a collection of small scripts without any version numbering. See: https://github.com/jvehent/Postscreen-Stats Regards, Manuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PORTVERSION when there is no upstream version number
On 10/21/14 14:45, Manuel Wiesinger wrote: Hi, what is the best practice for setting PORTVERSION, when the upstream port has no version number? Is it fine to go with the date like 20141021? Using the date in this sort of case is a pretty good idea, but you should prefix it by '0.0.'. The porter's handbook says: The idea is to make it easier to sort ports by looking at the version string. In particular, make sure version number components are always delimited by a period, and if the date is part of the string, use the 0.0..mm.dd format, not dd.mm. or the non-Y2K compliant yy.mm.dd format. It is important to prefix the version with 0.0. in case a release with an actual version number is made, which would be numerically less than . I'm trying to port postscreen-stats, which is just a collection of small scripts without any version numbering. See: https://github.com/jvehent/Postscreen-Stats However, since you're porting something distributed via Github see the specific instructions here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#5.4.2.1 Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: PORTVERSION when there is no upstream version number
On Tue, Oct 21, 2014 at 8:45 AM, Manuel Wiesinger man...@lungenarzt-wien.at wrote: Hi, what is the best practice for setting PORTVERSION, when the upstream port has no version number? Is it fine to go with the date like 20141021? I'm trying to port postscreen-stats, which is just a collection of small scripts without any version numbering. See: https://github.com/jvehent/Postscreen-Stats According to the Porters Handbook: https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html You can set PORTVERSION to 0.0..mm.dd or 1.0 (if original author is not going to release another version). -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PORTVERSION when there is no upstream version number
On 10/21/14 16:37, Scot Hetzel wrote: You can set PORTVERSION to 0.0..mm.dd or 1.0 (if original author is not going to release another version). I've missed exactly that part. Thanks, Manuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
compiling non-ports source: how to handle QT3?
I'm trying to compile pdfedit from github (not in ports tree).
configure gives this error:
./configure --with-t1-library=${LOCALBASE}/lib
-with-t1-includes=${LOCALBASE}/include
checking for QT qmake... configure: error: unable to find qmake for QT3
I have devel/qt4-qt3support installed on the system. I assume the problem
should be something simple like a setenv variable or creating a symlink or
entry in /etc/libmap.conf.
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/compiling-non-ports-source-how-to-handle-QT3-tp5958500.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: compiling non-ports source: how to handle QT3?
On Tue, 21 Oct 2014 11:40:29 -0700 (PDT) Beeblebrox zap...@berentweb.com
wrote:
I'm trying to compile pdfedit from github (not in ports tree).
configure gives this error:
./configure --with-t1-library=${LOCALBASE}/lib
-with-t1-includes=${LOCALBASE}/include
checking for QT qmake... configure: error: unable to find qmake for QT3
I have devel/qt4-qt3support installed on the system. I assume the problem
should be something simple like a setenv variable or creating a symlink or
entry in /etc/libmap.conf.
Install devel/qmake?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: compiling non-ports source: how to handle QT3?
Hi. Install devel/qmake? I though it went devel/qt4-qt3support - devel/qmake4 = qt4 qt3 functionality. Anyway, after installing devel/qmake, I now get: checking for QT qmake... Using QT3 with qmake=/usr/local/bin/qmake checking for QT lrelease... configure: error: unable to find lrelease localization binary for QT3 - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/compiling-non-ports-source-how-to-handle-QT3-tp5958500p5958521.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: compiling non-ports source: how to handle QT3?
OK, I got it that's NLS/localization. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/compiling-non-ports-source-how-to-handle-QT3-tp5958500p5958523.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
firefox-esr 31.2.0,1 is broken
It seems like firefox-esr 31.2.0,1 is broken: tingo@kg-core1$ firefox (process:85057): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed 1413913937178 addons.manager WARN Application shipped blocklist has an unexpected namespace (http://www.mozilla.org/newlayout/xml/parsererror.xml) Bus error (core dumped) tingo@kg-core1$ portversion -v firefox* [Reading data from pkg(8) ... - 992 packages found - done] firefox-esr-31.2.0,1 = up-to-date with port tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #1 r266590: Fri May 23 20:23:35 CEST 2014 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 My ports tree is updated today. -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/dansguardian revival?
On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać marko.cu...@mimar.rs wrote
On Mon, 20 Oct 2014 17:47:19 -0700
Chris H bsd-li...@bsdforge.com wrote:
Unless theirs any objection. I'll take it. I'll open a pr(1)
with a shar(1) ready, in about an hour.
--Chris
Nice to hear that dansguardian will be back in ports. I also used it
for years in combination with www/squid33 without problem. I was
compiling it from ports, and the trick was to compile squid33 first,
and dansguardian only after, as dansguardian would only check existence
of /use/local/bin/squid, and if it was already there, no matter which
version, it would happily compile, install and work.
Right. But there's ${STAGE} to deal with, as well. I may
make sqid34 the DEPENDS (I'm still testing).
I'm also working with the -devel version, and will likely
convert it to the (un)devel version, as there is less user
overhead involved -- RESTRICTED/COPYRIGHT/LICENSE/{...}
Should be able to post a complete version, sometime
tomorrow.
--Chris
--
Marko Cupać
https://www.mimar.rs
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
libxul is still broken
Hello, Does anybody have an idea how to compile libxul (it is marked broken).. Thanks for any help ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
question about option files + graphics/cairo
Hey folks, We are building ports via, I tried adding the build of cairo BOTH: make WITHOUT+=X11 OPTIONS_FILE_UNSET+=X11 however that doesn't seem to work and it's still pulling in X11 it seems: pkg: Missing dependency matching Origin: 'x11/libXext' Version: '1.3.2_2,1' Failed to install the following 1 package(s): cairo-1.12.16_1,2.txz Is there a way to fix this? this is ports tree pulled as of October 21. Would like to not require extra x11 libs if at all possible. -Alfred ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
