Re: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src', GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
Am 23.02.2012 22:35 (UTC+1) schrieb O. Hartmann: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Deinstalling x11-toolkits/qt33, upgrading graphics/poppler-qt4 and after that reinstalling x11-toolkits/qt33 works for me. Hope this helps, Rainer Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXXlibpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXXparseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXpoppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXXpoppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 ===Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GENpoppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 ___ 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: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src', GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
The same problem here, on FreeBSD 8.2 and legacy GCC. The problem arises on poppler-optcontent.moc. Best regards, Luca gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/poppler' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/poppler' Making all in test gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/test' CXXperf-test.o CXXperf-test-preview-dummy.o CXXLD perf-test CXXpdf-fullrewrite.o CXXLD pdf-fullrewrite gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/test' Making all in qt4 gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4' Making all in src gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GENpoppler-optcontent.moc -i: not found gmake[3]: *** [poppler-optcontent.moc] Error 127 gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake: *** [all] Error 2 On 02/23/12 22:35, O. Hartmann wrote: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXXlibpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXXparseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXpoppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXXpoppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 ===Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GENpoppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 ___ 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: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
Hi Reiner, unfortunately no x11-toolkits/qt33 here! And there's something strange: I cannot build poppler-qt4 1.18.4. but Oliver built it, the problem occurs during the install phase. And I cannot see any 0.18.4_1 version, as Oliver reports... Where am I wrong? any ideas? thanks Regards, Luca On 02/24/12 12:05, Rainer Hurling wrote: Am 23.02.2012 22:35 (UTC+1) schrieb O. Hartmann: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Deinstalling x11-toolkits/qt33, upgrading graphics/poppler-qt4 and after that reinstalling x11-toolkits/qt33 works for me. Hope this helps, Rainer Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXX libpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXX parseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXX poppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXX poppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 === Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 ___ 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
how do you specify a minimum lib version?
in LIB_DEPENDS it won't take anything like: = boost_serialization=.4 what if you needed a minimum version of the library? -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: Fix nvidia-like ports, help needed
On Thu, Feb 23, 2012 at 04:18:25PM -0800, Ade Lovett wrote:
On 2/23/2012 13:14, Baptiste Daroussin wrote:
Another solution could be to add an entry (and drop it in deinstallation to
libmap.conf) when installing the nvidia driver, in that case installing it
ad
libGL-nvidia.so.1 and adding:
libGL.so.1 libGL-nvidia.so.1
or something like that.
Going that route is likely to be messy given the current monolithic
/etc/libmap{,32}.conf
You'd most likely want ${LOCALBASE}/etc/libmap.conf.d/* (in a similar
manner to etc/periodic, etc/rc.d and so on). Whether the code that
currently handles libmap.conf is itself extended to use this directory
structure is open for discussion. An alternate method could perhaps be
a 'genlibmap' command which takes /etc/libmap.conf and this directory
structure to create a /var/run/libmap.conf which is actually used by rtld.
Having potentially multiple ports dinking _directly_ with
/etc/libmap.conf will result in considerable foot shooting.
-aDe
I agree with that, currently we can have LIBMAP env variable to append antoher
libmap.conf file to the /etc/libmap.conf,
So we have two option, convert the LIBMAP variable to a PATH-like variable,
(don't like this very much) or add an includedir keyword to libmap.conf then
the code will go thought the includedir and parse all the .conf files available
in that directory.
the second seems pretty easy, I'll write a PoC for it as soon as I can
regards,
Bapt
pgpoog99I2jIh.pgp
Description: PGP signature
nevermind.Re: how do you specify a minimum lib version?
On 2/24/12 6:57 AM, Michael Scheidell wrote: in LIB_DEPENDS it won't take anything like: = boost_serialization=.4 I googled. all other _DEPENDS uses = LIB_DEPENDS uses .[4-9] (i assume .(1[0-9]|[4-9])) -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: how do you specify a minimum lib version?
On Fri, Feb 24, 2012 at 06:57:39AM -0500, Michael Scheidell wrote:
in LIB_DEPENDS
it won't take anything like:
= boost_serialization=.4
what if you needed a minimum version of the library?
I think it should be like this:
LIB_DEPENDS=cairo.2:${PORTSDIR}/graphics/cairo
--
Denny Lin
___
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: how do you specify a minimum lib version?
On 2/24/12 7:36 AM, Denny Lin wrote:
I think it should be like this:
LIB_DEPENDS=cairo.2:${PORTSDIR}/graphics/cairo
thanks, tried that, if lib(x) is .3, still fails. =2 gets 'redirect error'
found answer by google, needs
LIB_DEPENDS=cairo.[2-9]:${PORTSDIR}/graphics/cairo
--
Michael Scheidell, CTO
*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell
___
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: how do you specify a minimum lib version?
Hi! On 24.02.2012 15:57, Michael Scheidell wrote: in LIB_DEPENDS it won't take anything like: = boost_serialization=.4 what if you needed a minimum version of the library? Seems you need this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-depend.html#AEN2138 -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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
Newbie maintainer, question regarding patches
Hi, I recently took over maintainership of the devel/ice port and trying to get familiar with the dos and don'ts of porting. In the past I contributed only by sending PRs, which would have been approved by the maintainer. Since I'm the maintainer now, will I still open normal PRs, which will then be taken by the committer? The Porter's Handbook seems a little bit thin on this (or I'm unable to distill . Also I have an additional question regarding how to patch - as far as I understand, usually there should be one patch per patched file. I have the following situation changing the port: a) I created a massive patch that enables the port to compile using modern compilers (gcc = 4.7 and clang = 3.0). Since this patch touches many files I was wondering if it wouldn't be better to keep this in one patch file instead of creating 20+ patch files which then have very little coherence (this patch fixes the same things in all files, as devel/ice violates the C++ standard in many places) b) I also have another massive patch which touches another 20 files which enables some new security features in ice (the history of this patch is that I developed it at first and submitted it to the vendor, who refined it and sent it back to me). I might want to make this patch optional as well (using a dialog style menu to enable it). In this case it also seems like it would be better not to split the patch up to all that many sources, but keep it as one feature that's contained in one patch. Especially when combining a) and b) (which both touch some of the same files and therefore will get more or less interleaved) it seems problematic (yet possible) to split them into many separate files. So the general question is: Is one patch per file a golden rule or are there exceptions in cases where one logical patch touches dozens of files? Thanks, Michael ___ 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: nevermind.Re: how do you specify a minimum lib version?
On 24/02/2012 12:54, Michael Scheidell wrote:
On 2/24/12 6:57 AM, Michael Scheidell wrote:
in LIB_DEPENDS
it won't take anything like:
= boost_serialization=.4
I googled.
all other _DEPENDS uses =
LIB_DEPENDS uses .[4-9]
(i assume .(1[0-9]|[4-9]))
Saying 'all other _DEPENDS' is slightly misleading. LIB_DEPENDS is
itself conceptually different to all the other
{FETCH,EXTRACT,PATCH,BUILD,RUN,TEST,PKG}_DEPENDS in that it doesn't list
dependencies that are required at a specific stage of building a port
(LIB_DEPENDS is added to both BUILD_DEPENDS and RUN_DEPENDS), and it
also implies a different way of testing that a dependency is fulfilled.
So, there are four different styles for dependency lines:
1) ${LOCALBASE}/bin/foo:${PORTSDIR}/bar/baz
Says 'unless the file ${LOCALBASE}/bin/foo exists, install the bar/baz
port' (All dependency variables except LIB_DEPENDS)
2) foo:${PORTSDIR}/bar/baz
Says 'unless there is an executable program foo on $PATH, install the
bar/baz port' *for anything except LIB_DEPENDS* where it means 'unless
there is a shared library -lfoo listed in the output of 'ldconfig -r',
install the bar/baz port'
3) foo=1.0:${PORTSDIR}/bar/baz
Says 'unless a package foo-1.0 (or any higher version) is installed,
install the bar/baz port' (All dependency variables except LIB_DEPENDS)
4) foo.[1-3]:${PORTSDIR}/bar/baz
Says 'unless foo.[1-3] is matched in the output of 'ldconfig -r',
install the bar/baz port' (Only for LIB_DEPENDS)
ie. do: ldconfig -r | grep '-lfoo.[1-3]'
This somewhat irritates my inner pedant, who would prefer it if _DEPENDS
variables referred strictly to the different phases of building and
installing ports, and there was some other syntax to indicate what test
should be done to decide if a dependency had been fulfilled. Maybe
something like:
@exists(${LOCALBASE}/bin/foo)
@package(foo=1.0)
@shlib(foo) or @shlib(foo=1)
which implies the possibility of adding other sorts of tests, say:
@perlmod(Foo-Bar1.0)
equivalent to testing that
perl -M'Foo::Bar 1.0' -e ''
exits successfully. (Meaning you could install modules from CPAN and
have them fulfil versioned dependencies in the ports.)
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: Newbie maintainer, question regarding patches
First, welcome! Thank you for stepping up to the plate and taking on ownership of a port. It is greatly appreciated. As for pr's, yes, keep sending them. Your patches still need to be committed to the ports tree by a committer. When you send in a maintenance patch, subject should/could be something like [MAINTAINER PATCH] devel/ice, class of maintainer-update, sent from your maintainers email address. owner will be auto set to freebsd-ports-bugs, with state of 'open'. A committer, looking through the gnats database will look for freebsd-ports-bugs/state of open, and maybe maintainer-update. The committer will take a quick look at your pr, does it describe why/what/where? is the patch a nice clean patch? Then, they will take the pr, set responsible to themselves, and you will get an email from GNATS. Committer will apply your patch, run something like portlint -abt, run it in a tinderbox, and if it looks good, commit your patch, or something similar, and close pr. If they have questions, they will reply back to gnats, set state to followup, and wait for your answer. Maybe they will ask to submit a radically different patch, or will change something to make pkg-plist better, or clean up lingering portlint issues. if someone else submits a pr, you will get a GNATS email, with a link to pr, and pr will be set to state of 'feedback', waiting for you to look over the pr, and/or reply back to GNATS that you approve, you don't approve, you need more information, or want the pr to be closed because you won't fix whatever it is. Look at the patch submitted, does it follow FreeBSD ports/maintainers best practices? does it fix a real problem, or only a 'local' issue? Test patch, does it fix the problem? is it upward compatible, run your port with new patch, make sure it doesn't break anything. Do you have/or need a tinderbox to test in? this way you won't mess up your environment while doing the initial testing. Look to redports for a public tinderbox. as for big/vs lots of little patches, usually your choice. as a committer, I look for a good patch, if your patch is one big patch, fine. and the 'extra-patch' can follow 'extra-patch' guidelines, and use a knob, the default is up to you, but unless 95% of the people need the extra patch, consider the upward compatibility issues. And, always, ask questions in ports@. Many of us would rather answer questions here, than need to fix a broken update later. Thanks again. (not officially speaking for anyone, since no one officially speaks for FreeBSD, keep that in mind, all answers and suggestions, YMMV, and are as trustworthy as any other answer you get on the internet) -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ 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: Newbie maintainer, question regarding patches
On Fri, Feb 24, 2012 at 7:39 AM, Michael Gmelin free...@grem.de wrote: b) I also have another massive patch which touches another 20 files which enables some new security features in ice (the history of this patch is that I developed it at first and submitted it to the vendor, who refined it and sent it back to me). I might want to make this patch optional as well (using a dialog style menu to enable it). In this case it also seems like it would be better not to split the patch up to all that many sources, but keep it as one feature that's contained in one patch. Just replying to this question: The ports tree is not meant for software development. I would much rather you try to get the patch into the upstream source than keep it as an optional patch in the ports tree. -- Eitan Adler ___ 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: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
On 24.02.2012 12:56 (UTC+1), Luca Pizzamiglio wrote: Hi Reiner, unfortunately no x11-toolkits/qt33 here! Did you also looked for qt-copy-3.3.8_13? It was only a guess because it helped me. And there's something strange: I cannot build poppler-qt4 1.18.4. but Oliver built it, the problem occurs during the install phase. And I cannot see any 0.18.4_1 version, as Oliver reports... My upgraded version is now poppler-qt4-0.18.4. I don't know about a portrevision 1. Seems that Oliver has to explain this. Where am I wrong? any ideas? thanks Regards, Luca On 02/24/12 12:05, Rainer Hurling wrote: Am 23.02.2012 22:35 (UTC+1) schrieb O. Hartmann: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Deinstalling x11-toolkits/qt33, upgrading graphics/poppler-qt4 and after that reinstalling x11-toolkits/qt33 works for me. Hope this helps, Rainer Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXX libpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXX parseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXX poppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXX poppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 === Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 ___ 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
New ports - Bullet Cache
Hello, I've submitted a couple of new ports, and I'd like to ask someone to take a look at them and commit them: http://www.freebsd.org/cgi/query-pr.cgi?pr=164872 I'm not sure how to handle the shared library installation issue (lines 36,37 in mdcached/Makefile). signature.asc Description: OpenPGP digital signature
Re: Newbie maintainer, question regarding patches
On Feb 24, 2012, at 14:55, Eitan Adler wrote: On Fri, Feb 24, 2012 at 7:39 AM, Michael Gmelin free...@grem.de wrote: b) I also have another massive patch which touches another 20 files which enables some new security features in ice (the history of this patch is that I developed it at first and submitted it to the vendor, who refined it and sent it back to me). I might want to make this patch optional as well (using a dialog style menu to enable it). In this case it also seems like it would be better not to split the patch up to all that many sources, but keep it as one feature that's contained in one patch. Just replying to this question: The ports tree is not meant for software development. I would much rather you try to get the patch into the upstream source than keep it as an optional patch in the ports tree. In general I agree with your reasoning. The feature I'm talking about has been approved and will be in the next version (this happened almost half a year ago). Unfortunately Ice has a slow release cycle, as it is dual licensed (GPLv2+commercial). The next release of Ice is quite a while away and will probably a major release, as they only create releases that are also commercially supported. The vendor doesn't provide any source repository access or anything else that could be used to track new features or patches, they only get announced in the forums. So as a heavy user of this software package I would like to have access to these vendor approved and backwards compatible optional features without working outside of the ports tree. To a certain degree this is comparable to other ports that pull in optional features through patches (djbdns, qmail, nginx, php, etc.). Alternatively an devel/ice-devel port could be created, that brings in more of these new features, but that would of course create more overhead - I could also host these feature patches outside of ports (as PATCHFILES) or create a forked project to track them, but all of this seems a little bit like over engineering, given the fact that the changes are fairly minimal (even though they're touching many files). Michael -- Eitan Adler ___ 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: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
Problem fixed! thanks to solve ports/165438! It was caused by qt3 conflict OR freebsd 9.0. I had no qt3 package installed, qt4 only. Compiled and updated. Thanks. Best regards, Luca On 02/24/12 15:04, Rainer Hurling wrote: On 24.02.2012 12:56 (UTC+1), Luca Pizzamiglio wrote: Hi Reiner, unfortunately no x11-toolkits/qt33 here! Did you also looked for qt-copy-3.3.8_13? It was only a guess because it helped me. And there's something strange: I cannot build poppler-qt4 1.18.4. but Oliver built it, the problem occurs during the install phase. And I cannot see any 0.18.4_1 version, as Oliver reports... My upgraded version is now poppler-qt4-0.18.4. I don't know about a portrevision 1. Seems that Oliver has to explain this. Where am I wrong? any ideas? thanks Regards, Luca On 02/24/12 12:05, Rainer Hurling wrote: Am 23.02.2012 22:35 (UTC+1) schrieb O. Hartmann: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Deinstalling x11-toolkits/qt33, upgrading graphics/poppler-qt4 and after that reinstalling x11-toolkits/qt33 works for me. Hope this helps, Rainer Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXX libpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXX parseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXX poppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXX poppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 === Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 ___ 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: how do you specify a minimum lib version?
On -10.01.-28163 14:59, Michael Scheidell wrote: in LIB_DEPENDS it won't take anything like: = boost_serialization=.4 what if you needed a minimum version of the library? For years now the shared-library's major number is treated as a regular expression by bsd.port.mk. So you could use something like: LIB_DEPENDS=boost_serialization.[456789]:... this should be enough for a while -- until there appears boost_serialization.10, necessitating a hairier regexp. ImageMagick port uses this to depend on the fixed version of libfpx, for example. You may also be able to insist on the version of the boost port being above a certain string, but I don't know the syntax... Yours, -mi ___ 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
updating mksh, portmaster -a, pkg_version strangeness
Hello, It looks like 'portmaster -a' was not picking up mksh update since mksh-r40 here, it piqued my curiosity when pkg_version reported I had newer mksh installed than available in ports tree, but the version I had installed was ripe old mksh-r40. Now, after 'portmaster mksh' and apparently 'Upgrade of mksh-r40 to mksh-r40.d completed' could somebody explain that? best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/updating-mksh-portmaster-a-pkg-version-strangeness-tp5513504p5513504.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: graphics/poppler-qt4: Installation error: /poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc, not: not found, gmake[1]: *** [poppler-optcontent.moc] Error 127
On 02/24/12 15:04, Rainer Hurling wrote: On 24.02.2012 12:56 (UTC+1), Luca Pizzamiglio wrote: Hi Reiner, unfortunately no x11-toolkits/qt33 here! Did you also looked for qt-copy-3.3.8_13? It was only a guess because it helped me. qt-copy-3.3.8_13 is indeed installed and used by this installed clients I use frequently: luma-2.3_7 pdfedit-0.4.5 qscintilla-1.7.1_7 orsa-0.7.0_21 py27-qt-3.18.2,2 And there's something strange: I cannot build poppler-qt4 1.18.4. but Oliver built it, the problem occurs during the install phase. And I cannot see any 0.18.4_1 version, as Oliver reports... This is a fault of mine. I have this confused with ktorrent-4.1.3_1, which is resilient to be updated as some other ports now ... By the way, deleting the qt-copy-3 port helps. Thanks. I guess I have had in the past similar problems with exactly this port. My upgraded version is now poppler-qt4-0.18.4. I don't know about a portrevision 1. Seems that Oliver has to explain this. Where am I wrong? any ideas? thanks Regards, Luca Regards, Oliver On 02/24/12 12:05, Rainer Hurling wrote: Am 23.02.2012 22:35 (UTC+1) schrieb O. Hartmann: I found myself confronted with this error today. I happens on a FreeBSD 10.0/amd64 box, most recently built-world. The error is persistent with CLANG and legacy GCC 4.2.1. The port is a denepndency for several client applications I've installed on that box and after the update today (poppler-qt4 seems to be installed before as version 0.18.4 and got updated today to version 0.18.4_1), the port isn't installed anymore! The portmaintainersoftware is portmaster. Error follows below. Any ideas? Deinstalling x11-toolkits/qt33, upgrading graphics/poppler-qt4 and after that reinstalling x11-toolkits/qt33 works for me. Hope this helps, Rainer Regards, Oliver clang++: warning: argument unused during compilation: '-fno-check-new' CXX libpoppler_cpp_la-poppler-version.lo clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD libpoppler-cpp.la clang++: warning: argument unused during compilation: '-pthread' clang++: warning: argument unused during compilation: '-pthread' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' Making all in tests gmake[3]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' CXX parseargs.o clang++: warning: argument unused during compilation: '-fno-check-new' CXX poppler-dump.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-dump clang++: warning: argument unused during compilation: '-ansi' CXX poppler-render.o clang++: warning: argument unused during compilation: '-fno-check-new' CXXLD poppler-render clang++: warning: argument unused during compilation: '-ansi' gmake[3]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp/tests' gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/cpp' gmake[2]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[2]: Nothing to be done for `all-am'. gmake[2]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4' === Installing for poppler-qt4-0.18.4 === Generating temporary packing list Making install in src gmake[1]: Entering directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' GEN poppler-optcontent.moc not: not found gmake[1]: *** [poppler-optcontent.moc] Error 127 gmake[1]: Leaving directory `/usr/ports/graphics/poppler-qt4/work/poppler-0.18.4/qt4/src' gmake: *** [install-recursive] Error 1 *** [do-install] Error code 2 Stop in /usr/ports/graphics/poppler-qt4. === Installation of poppler-qt4-0.18.4 (graphics/poppler-qt4) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmasterflags graphics/poppler-qt4 signature.asc Description: OpenPGP digital signature
dl library and fdatasync(2)
i am trying to build nodejs on freebsd9, and get a warning:
Checking for library dl : not found
Checking for fdatasync(2) with c++ : no
could someone point me where these libraries are?
thanks norman
--
% .join( [ {'*':'@','^':'.'}.get(c,None) or
chr(97+(ord(c)-83)%26) for c in ,adym,*)uzq^zqf ] )
___
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: dl library and fdatasync(2)
On Feb 24, 2012, at 10:40 AM, Norman Khine wrote: i am trying to build nodejs on freebsd9, and get a warning: Checking for library dl : not found Checking for fdatasync(2) with c++ : no could someone point me where these libraries are? FreeBSD's libc provides dlopen(), dlclose(), etc-- there's no need for a separate libdl to do dynamic loading. fdatasync(2) is a cheaper version of fsync(2) which does not try to update filesystem metadata; using soft updates with FreeBSD's UFS2 filesystem already provides most of the benefits. So you don't need that either, just call fsync() instead. Regards, -- -Chuck ___ 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
Minor changes to bsd.port.mk and bsd.pkgng.mk
Hello,
what do you think about the following minor changes to bsd.port.mk
and bsd.pkgng.mk? The motivation is that it is currently relatively
hard to detect, which options of a port are locally changed by user,
or by gradual port upgrades with OPTIONS changed by port maintainer.
(With consequence that when upgrading ports using packages and there
is some non-default options value in a port, direct port compilation
should be forced instead of use of a package.)
Some port maintainers do not use on/off, but they use values ON/On/OFF/Off.
I think that curent default value detection in make showconfig is useless
and confusing, and it should be better to detect real value difference
among OPTIONS in Makefile and options is /var/db/ports.
Furthermore, it is possible to define WITH_* and WITHOUT_* variables
in environment, so maybe there could be even bigger checks for on/off.
--- bsd.port.mk.orig2012-02-24 20:03:39.0 +0100
+++ bsd.port.mk 2012-02-24 20:17:01.0 +0100
@@ -5981,7 +5981,7 @@
set -- ${OPTIONS} XXX; \
while [ $$# -gt 3 ]; do \
OPTIONSLIST=$${OPTIONSLIST} $$1; \
- defaultval=$$3; \
+ defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
withvar=WITH_$$1; \
withoutvar=WITHOUT_$$1; \
withval=$$(eval ${ECHO_CMD} $$\{$${withvar}\}); \
@@ -6086,7 +6086,7 @@
fi; \
set -- ${OPTIONS} XXX; \
while [ $$# -gt 3 ]; do \
- defaultval=$$3; \
+ defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
withvar=WITH_$$1; \
withoutvar=WITHOUT_$$1; \
withval=$$(eval ${ECHO_CMD} $$\{$${withvar}\}); \
@@ -6096,7 +6096,10 @@
elif [ ! -z $${withoutval} ]; then \
val=off; \
else \
- val=$${defaultval} (default); \
+ val=$${defaultval}; \
+ fi; \
+ if [ $${val} = $${defaultval} ]; then \
+ val=$$val (default); \
fi; \
${ECHO_MSG} $$1=$${val} \$$2\; \
shift 3; \
--- bsd.pkgng.mk.orig 2012-02-24 20:08:33.0 +0100
+++ bsd.pkgng.mk2012-02-24 20:14:50.0 +0100
@@ -85,7 +85,7 @@
fi; \
set -- ${OPTIONS} XXX; \
while [ $$# -gt 3 ]; do \
- defaultval=$$3 \
+ defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
withvar=WITH_$$1; \
withoutvar=WITHOUT_$$1; \
withval=$$(eval ${ECHO_CMD} $$\{$${withvar}\}); \
--
Rudolf Cejka cejkar at fit.vutbr.cz http://www.fit.vutbr.cz/~cejkar
Brno University of Technology, Faculty of Information Technology
Bozetechova 2, 612 66 Brno, Czech Republic
___
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: Minor changes to bsd.port.mk and bsd.pkgng.mk
Cejka Rudolf wrote (2012/02/24):
+ defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
I'm sorry - all three lines with ${TR} have to be changed to
+ defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
so that one letter files in ports directories
do not break functionality.
--
Rudolf Cejka cejkar at fit.vutbr.cz http://www.fit.vutbr.cz/~cejkar
Brno University of Technology, Faculty of Information Technology
Bozetechova 2, 612 66 Brno, Czech Republic
___
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: Minor changes to bsd.port.mk and bsd.pkgng.mk
On Feb 24, 2012, at 2:35 PM, Cejka Rudolf wrote:
I'm sorry - all three lines with ${TR} have to be changed to
+defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
so that one letter files in ports directories
do not break functionality.
For your next update, please use [:upper:] and [:lower:] character classes.
This works with languages with diacritical marks and so forth...
Regards,
--
-Chuck
___
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: updating mksh, portmaster -a, pkg_version strangeness
On 02/24/2012 09:56, Jakub Lach wrote: Hello, It looks like 'portmaster -a' was not picking up mksh update since mksh-r40 here, it piqued my curiosity when pkg_version reported I had newer mksh installed than available in ports tree, but the version I had installed was ripe old mksh-r40. Now, after 'portmaster mksh' and apparently 'Upgrade of mksh-r40 to mksh-r40.d completed' could somebody explain that? The DISTVERSION is incorrectly specified: pkg_version -t R40 R40d -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: Newbie maintainer, question regarding patches
On 02/24/2012 06:18, Michael Gmelin wrote: In general I agree with your reasoning. The feature I'm talking about has been approved and will be in the next version (this happened almost half a year ago). Unfortunately Ice has a slow release cycle, as it is dual licensed (GPLv2+commercial). The next release of Ice is quite a while away and will probably a major release, as they only create releases that are also commercially supported. The vendor doesn't provide any source repository access or anything else that could be used to track new features or patches, they only get announced in the forums. So as a heavy user of this software package I would like to have access to these vendor approved and backwards compatible optional features without working outside of the ports tree. To a certain degree this is comparable to other ports that pull in optional features through patches (djbdns, qmail, nginx, php, etc.). For whatever it's worth, this sounds reasonable to me, and I've done similar in the past with some of my ports. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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
