Re: ports/*/jpeg "Thanks a lot guys"
On Sunday 02 August 2009 06:52:03 Matthew Seaman wrote:
> Similarly, programs that declare 'USE_MYSQL=NN' will have a LIB_DEPENDS
> on libmysqlclient.so.X added to their dependency mix even if they contain
> no compiled ELF binaries [See net-mgmt/cacti databases/phpmyadmin]
That's because you use USE_MYSQL when you really want to include
bsd.databases.mk and throw and error on specific mysql versions.
This could be addressed as below and for similar Mk/* files, should
it be needed:
Index: Mk/bsd.database.mk
===
RCS file: /home/ncvs/ports/Mk/bsd.database.mk,v
retrieving revision 1.37
diff -u -r1.37 bsd.database.mk
--- Mk/bsd.database.mk 21 Jul 2009 08:02:18 - 1.37
+++ Mk/bsd.database.mk 4 Aug 2009 06:59:12 -
@@ -158,7 +158,7 @@
.if (${USE_MYSQL} == "embedded")
BUILD_DEPENDS+=
${LOCALBASE}/lib/mysql/libmysqld.a:${PORTSDIR}/databases/mysql${MYSQL_VER}-server
.endif
-.else
+.elif (${USE_MYSQL} != "vcheck")
LIB_DEPENDS+=
mysqlclient.${MYSQL${MYSQL_VER}_LIBVER}:${PORTSDIR}/databases/mysql${MYSQL_VER}-client
.endif
.else
Index: databases/phpmyadmin/Makefile
===
RCS file: /home/ncvs/ports/databases/phpmyadmin/Makefile,v
retrieving revision 1.108
diff -u -r1.108 Makefile
--- databases/phpmyadmin/Makefile 30 Jun 2009 19:10:53 - 1.108
+++ databases/phpmyadmin/Makefile 4 Aug 2009 07:00:04 -
@@ -14,7 +14,7 @@
MAINTAINER=m.sea...@infracaninophile.co.uk
COMMENT= A set of PHP-scripts to manage MySQL over the web
-USE_MYSQL= yes
+USE_MYSQL= vcheck
IGNORE_WITH_PHP= 4
IGNORE_WITH_MYSQL= 323 40 41
USE_BZIP2= yes
--
Mel
___
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: freebsd-update & userland sources
Colin Percival wrote: > > On Sunday 02 August 2009 16:10:37 Tom Mende wrote: > >> Is there a way to get freebsd-update to keep userland sources > >> up to date? > Yes. If you have source code installed (for the right version of > FreeBSD) in /usr/src, then freebsd-update will keep it updated. > > (Slight complication: Because freebsd-update builds are normally > done before patches are committed to SVN, you won't get the > updated SVN revision numbers ... For someone using the source primarily for reference or to build the occasional port that needs it -- the OP's case, and likely typical of binary-update users -- this seems harmless enough. > ... or the new entries in UPDATING ... This seems not so good. The archives are overflowing with problems arising from failure to read UPDATING :( I'd think it desirable to find a way to keep it current. > ... via freebsd-update -- but you will get all of the > security/errata fixes.) ___ 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: recent update causes perl5.10 build failure
On Mon, 03 Aug 2009 12:24:10 -0700 Doug Barton
wrote:
>Scott Bennett wrote:
>> An update yesterday or today results in perl5.10's build aborting. When
>> it failed under portmaster, the messages from several processes were too
>> jumbled for me to see easily what had happened, so I tried portinstall
>> instead.
>
>If you get a non-obvious port build failure in portmaster your next
>step should be to try just building the port itself without any tools
>(i.e., cd /usr/ports/foo/bar ; make clean ; make). That will give you
>the idea of whether or not the error is related to the tool, or the
>port itself.
Okay. I'll keep that in mind for the future. However, in this case,
I recognized some symptoms of a port that is not safe for a parallel make:
errors complaining about missing directories and other files, etc.
>
>> At least on a first look, it seems that perl5.10 has "MAKE_JOBS_SAFE=
>> yes"
>> in its Makefile, but that it should not. I changed that to
>> "MAKE_JOBS_SAFE= no"
>
>The ports infrastructure does not care what the value of the define
>is, it just cares if it is defined. You need to do this:
>
>cd /usr/ports/lang/perl5.10
>vi Makefile (replace the MAKE_JOBS_SAFE with MAKE_JOBS_UNSAFE)
>make clean
>make config
>make
That's interesting, but in this case, I changed it as I noted before,
after which it built fine under the control of a tool. It is conceivable,
of course, that the timing of the processes involved varied enough from
the first failure to the time it finally worked that it just happened to
have everything already created by the time it was needed. My recollection,
though, is that it appeared to be doing a serial make after I made the change
from "yes" to "no". But I will know not to expect that in the future and
will use MAKE_JOBS_UNSAFE. That having been said, the port still needs to be
fixed either by a) making the variable replacement you suggest or b) changing
the port to make sure things happen in the proper order even when a parallel
make is used.
Keep in mind that this experience did appear to reveal a portmaster bug.
After the "portmaster -w -v -a" had already asked whether to rebuild perl5.8
even though it had a +IGNOREME file and had gotten an enter key in response,
which should have selected the "n" shown as the default ("[n]"), it later
went ahead and built perl5.8 anyway. From what you and the documentation
have told me, that should never happen.
>
>Then report your results.
>
Yes. Again, in this particular case, that report was both possible and
made without resort to the procedure you outlined.
Thanks for the information and suggestions, Doug.
Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet: bennett at cs.niu.edu *
**
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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"
Your email requires verification verify#flUSD8XOPFhDjlG9bwkoKZ9KTOnYxfc1
The message you sent requires that you verify that you are a real live human being and not a spam source. To complete this verification, simply reply to this message and leave the subject line intact. The headers of the message sent from your address are shown below: >From -freebsd-po...@freebsd.org Tue Aug 04 19:05:35 2009 Received: from [121.181.58.247] (port=3423) by sv1.nzhost.net.nz with esmtp (Exim 4.69) (envelope-from <-freebsd-po...@freebsd.org>) id 1MYE5R-0002CQ-3P for helpd...@nzservers.com; Tue, 04 Aug 2009 19:05:34 +1200 Received: from 121.181.58.247 by mx1.freebsd.org; Tue, 4 Aug 2009 16:05:29 +0900 From: "Grover Baird" <-freebsd-po...@freebsd.org> To: Subject: Part time job Date: Tue, 4 Aug 2009 16:05:29 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aca6Q0H8V5M2MFHV0Q5LZU5TF1F2E7== X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Message-ID: <01ca151d$62d79190$f73ab...@-freebsd-ports> X-Spam-Status: No, score=4.4 X-Spam-Score: 44 X-Spam-Bar: X-Spam-Flag: NO ___ 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: [kde-freebsd] devel/boost: new patch for testing update to 1.39
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 03, 2009 at 01:53:55PM -0800, Mel Flynn wrote:
> On Friday 31 July 2009 04:29:06 Alexander Churanov wrote:
>
> > Now It's clear. Thank you for explanation.
> > The WITH_PYSTE was not in the options framework, that's why I've
> > missed this part of work.
> >
> > I see two possible solutions:
> >
> > 1) Put the WITH_PYSTE variable back.
> > 2) Create a separate port like devel/boost-pyste.
> >
> > The first is easy, however leads to dependeny issues like 'let's
> > verify that boost-python-libs is installed with PYSTE support'.
> > Provided that Pyste is actually used by someone, this may re-introduce
> > bug ports/123927 (see
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123927).
> >
> > The second is much more robust, but requires more work. This is also
> > harder because I am not a user of Boost.Pyste. Thus, correctness
> > verification would be expensive.
>
> I think for the time being PySTE support should be off by default, because it
> pulls in a second libc and databases/akonadi plus kdeedu[34] use boost-python
> and because gccxml looks like a dead project.
>
> I've attached a patch that does exactly this and also fixes WITH_DEBUG
> building. There's one issue commented in the Makefile that I'm unable to
> relate to anything I did, but am assuming it's from WITH_DEBUG as well.
>
> ports/123927 could be solved/prevented by using a WANT_BOOST_PYSTE in
> dependent ports that rely on boost having PYSTE and using PKGNAMESUFFIX plus
> pkg_info to verify if boost-python-libs is boost-python-pyste-libs - as a
> stop-gap.
+1
>
> --
> Mel
> --- Makefile.orig 2009-07-28 03:44:50.0 -0800
> +++ Makefile 2009-08-03 00:55:34.0 -0800
> @@ -25,9 +25,23 @@
> PYTHON_INCLUDES="${PYTHON_INCLUDEDIR}"\
> PYTHON_LIB_PATH="${PYTHON_LIBDIR}"
>
> -RUN_DEPENDS+=
> ${PREFIX}/lib/libboost_thread.so.${BOOST_SHARED_LIB_VER}:${PORTSDIR}/devel/boost-libs
> -RUN_DEPENDS+=gccxml:${PORTSDIR}/devel/gccxml \
> -
> ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree
> +RUN_DEPENDS+=
> ${LOCALBASE}/lib/libboost_thread.so.${BOOST_SHARED_LIB_VER}:${PORTSDIR}/devel/boost-libs
> +RUN_DEPENDS+=
> ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree
> +.if defined(WITH_PYSTE)
> +RUN_DEPENDS+=gccxml:${PORTSDIR}/devel/gccxml
> +PLIST_SUB+= PYSTE=
> +.else
> +PLIST_SUB+= PYSTE="@comment "
> +.endif
> +
> +.if defined(WITH_DEBUG)
> +BOOST_BUILD= debug
> +# No idea how this gets enabled, but I'm getting it
> +OPTIM_SPEED= optimization-speed/
> +.else
> +OPTIM_SPEED= /
> +BOOST_BUILD= release
> +.endif
>
> BUILD_DEPENDS+= ${BJAM}:${PORTSDIR}/devel/boost-jam
> BUILD_DEPENDS+=
> ${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree
> @@ -39,12 +53,13 @@
>
> post-patch: customize-boost-build
>
> -
> +.if defined(WITH_PYSTE)
> post-configure:
> # Configure pyste, the Boost.Python code generator
> @cd ${BUILD_WRKSRC}/libs/python/pyste/install && \
> ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \
> config ${PYDISTUTILS_CONFIGUREARGS}
> +.endif
>
> do-build:
> # build the library
> @@ -52,19 +67,20 @@
> ${SETENV} ${MAKE_ENV} ${BJAM} ${BJAM_OPTIONS}
> --prefix=${PREFIX}\
> --toolset=${BOOST_TOOLS} --with-python
>
> +.if defined(WITH_PYSTE)
> # Build pyste, the Boost.Python code generator
> cd ${BUILD_WRKSRC}/libs/python/pyste/install && \
> ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \
> build ${PYDISTUTILS_BUILDARGS}
> -
> +.endif
> # Remove non-python headers
> cd ${WRKSRC} && \
> ${FIND} boost -not -path '*python*' -delete
>
> do-install:
> # Install libraries
> - ${INSTALL_DATA}
> ${WRKSRC}/bin.v2/libs/python/build/gcc-4.2.1/release/link-static/threading-multi/libboost_python.a
> ${PREFIX}/lib
> - ${INSTALL_DATA}
> ${WRKSRC}/bin.v2/libs/python/build/gcc-4.2.1/release/threading-multi/libboost_python.so.${PORTVERSION}
> ${PREFIX}/lib/libboost_python.so.${BOOST_SHARED_LIB_VER}
> + ${INSTALL_DATA}
> ${WRKSRC}/bin.v2/libs/python/build/gcc-4.2.1/${BOOST_BUILD}/link-static/${OPTIM_SPEED}threading-multi/libboost_python.a
> ${PREFIX}/lib
> + ${INSTALL_DATA}
> ${WRKSRC}/bin.v2/libs/python/build/gcc-4.2.1/${BOOST_BUILD}/${OPTIM_SPEED}threading-multi/libboost_python.so.${PORTVERSION}
> ${PREFIX}/lib/libboost_python.so.${BOOST_SHARED_LIB_VER}
>
> # Create symlink for shared library
> cd ${PREFIX}/lib/ && \
> @@ -79,10 +95,12 @@
> ${FIND} boost -type f -a \! -name "*.orig"\
> -exec ${INSTALL_DATA} \{\} ${PREFIX}/include/\{\} \;
>
> +.if defined(WITH_PYSTE)
> # Install pyste, the Boost.Python code generator
> cd ${WRKSRC}/libs/python/pyste/install && \
> ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} \
>
Re: Compile error mail/alpine
> FYI, In the future you're likely to get faster results if you send > your problem report to the port's maintainer as well as the > freebsd-ports@ list. Thanks Doug see below for replies > > David Southwell wrote: > > FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64- > > builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > on intel quad core > > > > > > cc -std=gnu99 -g -D_THREAD_SAFE -O2 -fno-strict-aliasing -pipe - > > DLDAP_DEPRECATED -rpath=/usr/local/lib -o alpine addrbook.o adrbkcmd.o > > after.o alpine.o arg.o busy.o colorconf.o confscroll.o context.o > > dispfilt.o flagmaint.o folder.o help.o imap.o init.o kblock.o keymenu.o > > ldapconf.o listsel.o mailcmd.o mailindx.o mailpart.o mailview.o newuser.o > > pattern.o pipe.o print.o radio.o remote.o reply.o roleconf.o send.o > > setup.o signal.o status.o takeaddr.o titlebar.o smime.o date.o -lcrypt > > -lpam -L/usr/lib - L/usr/local/openssl/lib -L/usr/local/lib > > ../pico/libpico.a > > ../pico/osdep/libpicoosd.a ../pith/libpith.a ../pith/osdep/libpithosd.a > > ../pith/charconv/libpithcc.a osdep/libpineosd.a ../c-client/c-client.a > > /usr/local/lib/libldap.so -lcrypto -ltinfo /usr/local/lib/liblber.so > > -lssl - Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib > > ../c-client/c-client.a(osdep.o)(.text+0x68a1): In function > > `ssl_onceonlyinit': > > /usr/ports/mail/alpine/work/alpine-2.00/imap/c-client/osdep.c:335: > > warning: warning: tmpnam() possibly used unsafely; consider using > > mkstemp() after.o(.text+0x36d): In function `start_after': > > /usr/ports/mail/alpine/work/alpine-2.00/alpine/after.c:77: undefined > > reference to `pthread_create' > > *** Error code 1 > > I just tried building it on a 7.2-STABLE amd64 from June 13th > (r194101) and didn't have any problems. Can you please post the > contents of /var/db/ports/alpine/options? Also, do you have any > options related to thread libraries in /etc/make.conf, and are you > using openssl from the ports, or in the base? > > > Doug /var/db/ports/alpine/options: I have tried with: # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for alpine-2.00_1 _OPTIONS_READ=alpine-2.00_1 WITH_THREADS=true WITH_MOUSE=true WITHOUT_NLS=true WITHOUT_ISPELL=true WITHOUT_NOSPELL=true WITH_PICO=true WITH_IPV6=true WITH_LDAP=true WITHOUT_PASSFILE=true WITH_CONS25=true WITHOUT_QUOTA=true WITH_MAILDIR=true AND # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for alpine-2.00_1 _OPTIONS_READ=alpine-2.00_1 WITH_THREADS=true WITH_MOUSE=true WITHOUT_NLS=true WITHOUT_ISPELL=true WITHOUT_NOSPELL=true WITH_PICO=true WITHOUT_IPV6=true WITH_LDAP=true WITHOUT_PASSFILE=true WITH_CONS25=true WITHOUT_QUOTA=true WITH_MAILDIR=true With the same results openssl: dns1# pkg_info |grep openssl openssl-0.9.8k_2SSL and crypto library php5-openssl-5.2.10 The openssl shared extension for php py26-openssl-0.8_1 Python interface to the OpenSSL library I also recompiled openssl to make sure all was well. make.conf: dns1# cat /etc/make.conf # added by use.perl 2009-07-30 10:53:48 PERL_VERSION=5.8.9 latest error messages: cc -std=gnu99 -g -D_THREAD_SAFE -O2 -fno-strict-aliasing -pipe - DLDAP_DEPRECATED -rpath=/usr/local/lib -o alpine addrbook.o adrbkcmd.o after.o alpine.o arg.o busy.o colorconf.o confscroll.o context.o dispfilt.o flagmaint.o folder.o help.o imap.o init.o kblock.o keymenu.o ldapconf.o listsel.o mailcmd.o mailindx.o mailpart.o mailview.o newuser.o pattern.o pipe.o print.o radio.o remote.o reply.o roleconf.o send.o setup.o signal.o status.o takeaddr.o titlebar.o smime.o date.o -lcrypt -lpam -L/usr/lib - L/usr/local/openssl/lib -L/usr/local/lib ../pico/libpico.a ../pico/osdep/libpicoosd.a ../pith/libpith.a ../pith/osdep/libpithosd.a ../pith/charconv/libpithcc.a osdep/libpineosd.a ../c-client/c-client.a /usr/local/lib/libldap.so -lcrypto -ltinfo /usr/local/lib/liblber.so -lssl - Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib ../c-client/c-client.a(osdep.o)(.text+0x68a1): In function `ssl_onceonlyinit': /usr/ports/mail/alpine/work/alpine-2.00/imap/c-client/osdep.c:335: warning: warning: tmpnam() possibly used unsafely; consider using mkstemp() after.o(.text+0x36d): In function `start_after': /usr/ports/mail/alpine/work/alpine-2.00/alpine/after.c:77: undefined reference to `pthread_create' *** Error code 1 Stop in /usr/ports/mail/alpine/work/alpine-2.00/alpine. *** Error code 1 Stop in /usr/ports/mail/alpine/work/alpine-2.00/alpine. *** Error code 1 Stop in /usr/ports/mail/alpine/work/alpine-2.00/alpine. *** Error code 1 Stop in /usr/ports/mail/alpine/work
Re: Your email requires verification verify#flUSD8XOPFhDjlG9bwkoKZ9KTOnYxfc1
> The message you sent requires that you verify that you > are a real live human being and not a spam source. > > To complete this verification, simply reply to this message and leave > the subject line intact. > > The headers of the message sent from your address are shown below: > > From -freebsd-po...@freebsd.org Tue Aug 04 19:05:35 2009 > Received: from [121.181.58.247] (port=3423) > by sv1.nzhost.net.nz with esmtp (Exim 4.69) > (envelope-from <-freebsd-po...@freebsd.org>) > id 1MYE5R-0002CQ-3P > for helpd...@nzservers.com; Tue, 04 Aug 2009 19:05:34 +1200 > Received: from 121.181.58.247 by mx1.freebsd.org; Tue, 4 Aug 2009 16:05:29 > +0900 From: "Grover Baird" <-freebsd-po...@freebsd.org> > To: > Subject: Part time job > Date: Tue, 4 Aug 2009 16:05:29 +0900 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-2" > Content-Transfer-Encoding: 7bit > X-Mailer: Microsoft Office Outlook, Build 11.0.5510 > Thread-Index: Aca6Q0H8V5M2MFHV0Q5LZU5TF1F2E7== > X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 > Message-ID: <01ca151d$62d79190$f73ab...@-freebsd-ports> > X-Spam-Status: No, score=4.4 > X-Spam-Score: 44 > X-Spam-Bar: > X-Spam-Flag: NO > > ___ > 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"
Re: devel/boost: new patch for testing update to 1.39
2009/8/4 Mel Flynn : > > I think for the time being PySTE support should be off by default, because it > pulls in a second libc and databases/akonadi plus kdeedu[34] use boost-python > and because gccxml looks like a dead project. Agree. > > I've attached a patch that does exactly this and also fixes WITH_DEBUG > building. There's one issue commented in the Makefile that I'm unable to > relate to anything I did, but am assuming it's from WITH_DEBUG as well. The issue was I've accidently hardcoded path which built python libraries are copied from. As a result, installation success was depending not only on DEBUG setting, but also on the version of gcc and, probably, other things. This is already fixed and checked-in to CVS. > > ports/123927 could be solved/prevented by using a WANT_BOOST_PYSTE in > dependent ports that rely on boost having PYSTE and using PKGNAMESUFFIX plus > pkg_info to verify if boost-python-libs is boost-python-pyste-libs - as a > stop-gap. Well, if the user installs some port that depends on boost-python-libs, the user gets boost-python-libs installed. Then the user wants to install another port that depends on boost-python-pyste-libs. Would this succeed? Sincerely, Alexander Churanov, maintainer of devel/boost-* ___ 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"
Python extensions problem on compiling www/epiphany & (related??) devel/boost-python-libs
FreeBSD dns1.vizion2000.net 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun
24 00:14:35 UTC 2009 r...@amd64-
builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
Unable to find python extensions in epiphany:
checking for X11/XF86keysym.h... yes
checking whether Python support is requested... yes
checking whether /usr/local/bin/python2.6 version >= 2.3... yes
checking for /usr/local/bin/python2.6 version... 2.6
checking for /usr/local/bin/python2.6 platform... freebsd7
checking for /usr/local/bin/python2.6 script directory...
${prefix}/lib/python2.6/site-packages
checking for /usr/local/bin/python2.6 extension module directory...
${exec_prefix}/lib/python2.6/site-packages
checking for headers required to compile python extensions... not found
configure: error: Python not found
===> Script "configure" failed unexpectedly.
I do not how the headers are meant to get there or know what headers to look
for but here is a listing from:
dns1# pwd
/usr/local/lib/python2.6/site-packages
dns1# ls -l
total 4744
drwxr-xr-x 2 root wheel 512 Aug 2 18:49 Alacarte
-r--r--r-- 1 root wheel1002 Aug 2 18:59 CORBA.py
-rw-r--r-- 1 root wheel 161 Aug 3 23:36 CORBA.pyc
-rw-r--r-- 1 root wheel 161 Aug 3 23:36 CORBA.pyo
drwxr-xr-x 7 root wheel 512 Aug 3 13:02 Crypto
drwxr-xr-x 6 root wheel1024 Aug 2 09:36 Numeric
-rw-r--r-- 1 root wheel 8 Aug 2 09:36 Numeric.pth
-rwxr-xr-x 1 root wheel1123 Aug 2 18:59 ORBit.la
-rwxr-xr-x 1 root wheel 108971 Aug 2 18:59 ORBit.so
drwxr-xr-x 3 root wheel 512 Aug 3 13:02 OpenSSL
-r--r--r-- 1 root wheel1026 Aug 2 18:59 PortableServer.py
-rw-r--r-- 1 root wheel 170 Aug 3 23:36 PortableServer.pyc
-rw-r--r-- 1 root wheel 170 Aug 3 23:36 PortableServer.pyo
-rw-r--r-- 1 root wheel 319 Aug 2 16:22 PyXML-0.8.4-py2.6.egg-info
-r--r--r-- 1 root wheel 119 Aug 3 23:36 README
-rw-r--r-- 1 root wheel 265394 Aug 2 18:51 _dbus_bindings.a
-rwxr-xr-x 1 root wheel 910 Aug 2 18:51 _dbus_bindings.la
-rwxr-xr-x 1 root wheel 161924 Aug 2 18:51 _dbus_bindings.so
-rw-r--r-- 1 root wheel6840 Aug 2 18:51 _dbus_glib_bindings.a
-rwxr-xr-x 1 root wheel1147 Aug 2 18:51 _dbus_glib_bindings.la
-rwxr-xr-x 1 root wheel 10001 Aug 2 18:51 _dbus_glib_bindings.so
-rwxr-xr-x 1 root wheel 92782 Aug 2 16:21 _sqlite3.so
drwxr-xr-x 10 root wheel 512 Aug 2 16:22 _xmlplus
drwxr-xr-x 2 root wheel1024 Aug 2 14:21 atom
drwxr-xr-x 4 root wheel1024 Aug 3 23:38 butterfly
drwxr-xr-x 2 root wheel 512 Aug 2 09:16 cairo
drwxr-xr-x 3 root wheel1536 Aug 2 18:51 dbus
-rw-r--r-- 1 root wheel 33 Aug 2 18:51 dbus_bindings.py
-rw-r--r-- 1 root wheel 191 Aug 3 23:36 dbus_bindings.pyc
-rw-r--r-- 1 root wheel 191 Aug 3 23:36 dbus_bindings.pyo
drwxr-xr-x 7 root wheel 512 Aug 2 21:40 deskbar
-r--r--r-- 1 root wheel 15061 Aug 2 10:20 drv_libxml2.py
-rw-r--r-- 1 root wheel 11409 Aug 3 23:36 drv_libxml2.pyc
-rw-r--r-- 1 root wheel 11409 Aug 3 23:36 drv_libxml2.pyo
-rw-r--r-- 1 root wheel 272 Aug 2 21:40 easy-install.pth
drwxr-xr-x 2 root wheel1024 Aug 3 10:38 elementtree
-rw-r--r-- 1 root wheel 749 Aug 3 10:38 elementtree-1.2.6_20050316-
py2.6.egg-info
-rw-r--r-- 1 root wheel 122792 Aug 3 09:00 empathy.a
-rwxr-xr-x 1 root wheel2489 Aug 3 09:00 empathy.la
-rwxr-xr-x 1 root wheel 118000 Aug 3 09:00 empathy.so
-rw-r--r-- 1 root wheel 95322 Aug 3 09:00 empathygtk.a
-rwxr-xr-x 1 root wheel3272 Aug 3 09:00 empathygtk.la
-rwxr-xr-x 1 root wheel 91516 Aug 3 09:00 empathygtk.so
-rw-r--r-- 1 root wheel 191924 Aug 3 16:16 farsight.a
-rwxr-xr-x 1 root wheel1353 Aug 3 16:16 farsight.la
-rwxr-xr-x 1 root wheel 128317 Aug 3 16:16 farsight.so
drwxr-xr-x 24 root wheel1536 Aug 2 14:21 gdata
-rw-r--r-- 1 root wheel1471 Aug 2 14:21 gdata-2.0.0-py2.6.egg-info
drwxr-xr-x 7 root wheel1024 Aug 3 09:26 glchess
drwxr-xr-x 3 root wheel1536 Aug 3 09:27 gnome_sudoku
drwxr-xr-x 3 root wheel 512 Aug 2 14:14 gst-0.
Re: java broken on recent -current?
* Mel Flynn (mel.flynn+fbsd.po...@mailing.thruhere.net) wrote: > Thou shall search the archives before posting. The short and curlies: Indeed. Thanks! -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: status of FreeBSD ports you maintain as of 20090705
2009/8/1 Mark Linimon : > On Thu, Jul 23, 2009 at 07:37:27PM +0200, Martin Tournoij wrote: >> I now know more than ever why I switched to OpenBSD. >> FreeBSD people no longer seem to care about broken ports, or making people >> who submit broken patches maintainers, or even replying to my messages. [snip] > To summarize: my own view is that we don't want bad patches or bad updates > to be committed; but our committers are human, too. It's worth repeating > that we rely on our committers to be responsible for verifying that the > changes that they're committing are correct and useful; but, they're > volunteers as well, so we have to rely on a combination of constructive > criticism and encouragement to try to improve things. There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports - increase the number of volunteers/committers/testers... - switch to a multi-level solution (e.g. Archlinux). Regards -- Diego Depaoli ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
It seems this may be related to AMD64 kernel? Still getting the following error while trying to compile. checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether system uses EBCDIC... no performing libtool configuration... ./configure: 9753: Syntax error: word unexpected (expecting ")") *** Error code 2 Stop in /usr/ports/devel/apr. *** Error code 1 Stop in /usr/ports/devel/apr. Whats in your /etc/make.conf and related? $ make -V PYTHON -V PYTHON_VER 2.5 What do the symlinks look like in /usr/local/bin/py* ? No symlinks there: -r-xr-xr-x 2 root wheel 84 Jul 18 00:06 pydoc* -r-xr-xr-x 1 root wheel 84 Jul 18 00:16 pydoc2.4* -r-xr-xr-x 2 root wheel 84 Jul 18 00:06 pydoc2.5* -rwxr-xr-x 1 root wheel 262 Jul 31 06:09 pyste.py* -r-xr-xr-x 2 root wheel 1189960 Jul 18 00:05 python* -r-xr-xr-x 2 root wheel 1424 Jul 18 00:06 python-config* -r-xr-xr-x 2 root wheel 4976 Jul 18 00:06 python-shared* -r-xr-xr-x 2 root wheel 1431 Jul 18 00:06 python-shared-config* -r-xr-xr-x 1 root wheel 5040 Jul 18 00:16 python-shared2.4* -r-xr-xr-x 2 root wheel 4976 Jul 18 00:06 python-shared2.5* -r-xr-xr-x 2 root wheel 1431 Jul 18 00:06 python-shared2.5-config* -r-xr-xr-x 1 root wheel 1024424 Jul 18 00:16 python2.4* -r-xr-xr-x 2 root wheel 1189960 Jul 18 00:05 python2.5* -r-xr-xr-x 2 root wheel 1424 Jul 18 00:06 python2.5-config* ___ 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: Python extensions problem on compiling www/epiphany & (related??) devel/boost-python-libs
David, This really looks like you have a broken python installation. Sincerely, Alexander Churanov ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
> It seems this may be related to AMD64 kernel? > > Still getting the following error while trying to compile. > > checking whether it is safe to define __EXTENSIONS__... yes > checking for library containing strerror... none required > checking whether system uses EBCDIC... no > performing libtool configuration... > ./configure: 9753: Syntax error: word unexpected (expecting ")") > *** Error code 2 > > Stop in /usr/ports/devel/apr. > *** Error code 1 > > Stop in /usr/ports/devel/apr. > > > Whats in your /etc/make.conf and related? > > > > $ make -V PYTHON -V PYTHON_VER > > 2.5 > > > What do the symlinks look like in /usr/local/bin/py* ? > > No symlinks there: > > -r-xr-xr-x 2 root wheel 84 Jul 18 00:06 pydoc* > -r-xr-xr-x 1 root wheel 84 Jul 18 00:16 pydoc2.4* > -r-xr-xr-x 2 root wheel 84 Jul 18 00:06 pydoc2.5* > -rwxr-xr-x 1 root wheel 262 Jul 31 06:09 pyste.py* > -r-xr-xr-x 2 root wheel 1189960 Jul 18 00:05 python* > -r-xr-xr-x 2 root wheel 1424 Jul 18 00:06 python-config* > -r-xr-xr-x 2 root wheel 4976 Jul 18 00:06 python-shared* > -r-xr-xr-x 2 root wheel 1431 Jul 18 00:06 python-shared-config* > -r-xr-xr-x 1 root wheel 5040 Jul 18 00:16 python-shared2.4* > -r-xr-xr-x 2 root wheel 4976 Jul 18 00:06 python-shared2.5* > -r-xr-xr-x 2 root wheel 1431 Jul 18 00:06 python-shared2.5-config* > -r-xr-xr-x 1 root wheel 1024424 Jul 18 00:16 python2.4* > -r-xr-xr-x 2 root wheel 1189960 Jul 18 00:05 python2.5* > -r-xr-xr-x 2 root wheel 1424 Jul 18 00:06 python2.5-config* may be I have a clue but am not certain which step was responsible for finally getting apr to compile so I am going through what I did in the hope it may help I cannot guarantee I have remembered everything because it was spread over many hours whilst doing many other tasks!! 1. I revisited UPDATING and found I had skipped: 20090802: AFFECTS: users of devel/libtool15 and devel/libltdl15 AUTHOR: m...@freebsd.org The devel/libtool15 and devel/libltdl15 ports have been moved to libtool22 and libltdl22 respectively then updated to 2.2.6a. You will need to run portmaster or portupgrade to properly perform the upgrade: and followed the instructions there. 2. I did portupgrade -af 3. I then deinstalled devel/apr. 4. I deinstalled and recompiled python2.6 5. I then recompiled devel/apr and voila!! david ___ 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: Getting a lot of - pkg_version: corrupted record (pkgdep line without argument), ignoring
Quoting Doug Barton : eculp wrote: I'm getting a lot of the following messages and have no idea how to find which package is causing the problem. This is one of those times that opening up the files and having a look for yourself might be a good way to start. :) pkg_version: corrupted record (pkgdep line without argument), ignoring egrep '(pkgdep$|pkgdep $)' /var/db/pkg/*/+CONTENTS However, you indicate below that you are using 'portmaster --check-depends' which should be fixing those for you. So try this: cd /var/db/ cp -Rp pkg pkg-before portmaster --check-depends diff -ur pkg-before pkg > ~/pkg-dir.diff1 cp -Rp pkg pkg-after portmaster --check-depends diff -ur pkg-after pkg > ~/pkg-dir.diff2 cd pkg egrep -l '(pkgdep$|pkgdep $)' */+CONTENTS > ~/pkg-dir.egrep Doug, thanks for taking the time to answer and write the scripts. I've been both hesitant and probably lazy to look under the hood especially in /var/db/* ports stuff but the script worked as expected and got me looking at the files, something I should have done years ago but THANKS to PORTMASTER I hadn't needed to. In this case I was trying to remove everything in kde3 and simultaneously try to not affect kde4 with pkg_deinstall -r and that really turned to shit. I started seeing this after that failed attempt. I rebuilt the packages and all is well. Thanks again for the explanation, the script and especially for Postmaster that I have been using almost exclusively since the first version and has been improving .with each subsequent release. ed Ideally pkg-dir.diff2 pkg-dir.egrep should both be empty there. If not, you will need to rebuild all of the ports listed in the egrep file. One easy way to do that would be to use vi to strip everything but the directory name out of that file then do this: portmaster `cat ~/pkg-dir.egrep` While I'm bothering you, could someone give me some tips on the best ways to find corrupted files in /var/db/pkgs, /var/db/ports and any other places that they might be hiding. I run portmaster --check-depends portmaster --check-port-dbdir Those are both good examples from my perspective. :) One thing though, --check-port-dbdir won't find anything that is corrupt, it will only find things that don't apply to your currently installed ports. hth, Doug -- This .signature sanitized for your protection -- ¿Cuentas con empleados o colaboradores? ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
David Southwell wrote: may be I have a clue but am not certain which step was responsible for finally getting apr to compile so I am going through what I did in the hope it may help I cannot guarantee I have remembered everything because it was spread over many hours whilst doing many other tasks!! 1. I revisited UPDATING and found I had skipped: 20090802: AFFECTS: users of devel/libtool15 and devel/libltdl15 AUTHOR: m...@freebsd.org The devel/libtool15 and devel/libltdl15 ports have been moved to libtool22 and libltdl22 respectively then updated to 2.2.6a. You will need to run portmaster or portupgrade to properly perform the upgrade: and followed the instructions there. 2. I did portupgrade -af 3. I then deinstalled devel/apr. 4. I deinstalled and recompiled python2.6 5. I then recompiled devel/apr and voila!! david This makes 100% sense. I'm still betting that troy is having libtool issues too. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc.http://p6m7g8.net Senior Sys Admin- RideCharge, Inc. http://ridecharge.com ASF Member - Apache Software Foundation http://apache.org FreeBSD Committer - FreeBSD Foundation http://freebsd.org Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: FreeBSD Port: dovecot-1.2.x
On Mon, Aug 03, 2009 at 04:47:18PM -0400, Yarema wrote: > Frank Leonhardt wrote: > > Hi, > > > > I'm trying to track down a very weird issue with Dovecot and MS Outlook > > 2003, and it'd be good to be using 1.2.x in the tests. Any idea when it > > might be coming? If it's going to be a while I might have a go myself (or > > use Linux!); if not I'll wait. > > > > Is there anything I should know about before I try it myself? > > > > Thanks, Frank. > > I'm working on the update to 1.2.x Hopefully in the next day or two I > should have something ready to commit.. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137261 - In case you missed the automated mail to the maintainer. :) -- WXS ___ 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"
is upgrade of devel/lib{tool, tldl}15 to devel/lib{tool, tldl}22 worth it?
I see that /usr/ports/UPDATING describes an upgrade of devel/libtool15 and devel/libtldl15 to devel/libtool22 and devel/libtldl22, respectively. Is this a good enough thing to do to justify the probable misery and risk of disaster that would be necessary to get through it? If so, I'll give it a shot. OTOH, I dread going through a trial like the perl5.8 to perl5.10 upgrade, which was really a pretty awful experience. Has anyone done this new upgrade and survived yet? Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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"
pth.h errors while compiling portupgrade -rf python26-2.6.2_1
problems with pth.h In file included from extensions/pyexpat.c:5: /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or directory error: command 'cc' failed with exit status 1 *** Error code 1 sr/local/include -IModules/_sqlite -I/usr/local/include/python2.6 -c _sqlite/cache.c -o build/temp.freebsd-7.2-RELEASE-p2-amd64-2.6/_sqlite/cache.o In file included from _sqlite/cache.h:26, from _sqlite/cache.c:24: /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or directory error: command 'cc' failed with exit status 1 *** Error code 1 cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t - DTHREAD_STACK_SIZE=0x10 -O2 -fno-strict-aliasing -pipe -fPIC - DMODULE_NAME="sqlite3" -I/usr/local/include -IModules/_sqlite - I/usr/local/include/python2.6 -c _sqlite/cache.c -o build/temp.freebsd-7.2- RELEASE-p2-amd64-2.6/_sqlite/cache.o In file included from _sqlite/cache.h:26, from _sqlite/cache.c:24: /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or directory error: command 'cc' failed with exit status 1 *** Error code 1 Stop in /usr/ports/databases/py-sqlite3. *** Error code 1 I tried compiling /usr/ports/devel/pth but that failed with the same error!!! David ___ 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: pth.h errors while compiling portupgrade -rf python26-2.6.2_1 -RESOLVED
> problems with pth.h > > In file included from extensions/pyexpat.c:5: > /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or > directory > error: command 'cc' failed with exit status 1 > *** Error code 1 > > sr/local/include -IModules/_sqlite -I/usr/local/include/python2.6 -c > _sqlite/cache.c -o > build/temp.freebsd-7.2-RELEASE-p2-amd64-2.6/_sqlite/cache.o In file > included from _sqlite/cache.h:26, > from _sqlite/cache.c:24: > /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or > directory > error: command 'cc' failed with exit status 1 > *** Error code 1 > > cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t - > DTHREAD_STACK_SIZE=0x10 -O2 -fno-strict-aliasing -pipe -fPIC - > DMODULE_NAME="sqlite3" -I/usr/local/include -IModules/_sqlite - > I/usr/local/include/python2.6 -c _sqlite/cache.c -o build/temp.freebsd-7.2- > RELEASE-p2-amd64-2.6/_sqlite/cache.o > In file included from _sqlite/cache.h:26, > from _sqlite/cache.c:24: > /usr/local/include/python2.6/Python.h:168:17: error: pth.h: No such file or > directory > error: command 'cc' failed with exit status 1 > *** Error code 1 > > Stop in /usr/ports/databases/py-sqlite3. > *** Error code 1 > > I tried compiling /usr/ports/devel/pth but that failed with the same > error!!! > > David I finally resolved this problem set with: dns1# ln -s /usr/local/include/pth/pth.h /usr/local/include/python2.6/ dns1# ln -s /usr/local/include/pth/pthread.h /usr/local/include/python2.6/ david ___ 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: is upgrade of devel/lib{tool, tldl}15 to devel/lib{tool, tldl}22 worth it?
2009/8/4 Scott Bennett : > I see that /usr/ports/UPDATING describes an upgrade of devel/libtool15 > and devel/libtldl15 to devel/libtool22 and devel/libtldl22, respectively. > Is this a good enough thing to do to justify the probable misery and risk > of disaster that would be necessary to get through it? If so, I'll give it > a shot. OTOH, I dread going through a trial like the perl5.8 to perl5.10 > upgrade, which was really a pretty awful experience. > Has anyone done this new upgrade and survived yet? Don't know for the upgrade, I preferred deinstalling and reinstalling manually all of my 400 (well I reinstalled only 20 of them, 380 are RUN or LIB dependencis) ports because of : - libjpeg upgrade - some 8-CURRENT libraries version bump (I could make delete-old-libs after deleting ports) - libtool and libltdl upgrade - KDE 4.3.0 just released from area51 That was enough for me to prefer the less risky way... works great so far :) > > Scott Bennett, Comm. ASMELG, CFIAG > ** > * Internet: bennett at cs.niu.edu * > ** > * "A well regulated and disciplined militia, is at all times a good * > * objection to the introduction of that bane of all free governments * > * -- a standing army." * > * -- Gov. John Hancock, New York Journal, 28 January 1790 * > ** > ___ > 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" > -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: is upgrade of devel/lib{tool, tldl}15 to devel/lib{tool, tldl}22 worth it?
* Scott Bennett (benn...@cs.niu.edu) wrote: > Has anyone done this new upgrade and survived yet? I had no problems. There are not really many ports which depend on libltdl anyway. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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"
compile error www/epiphany ? libtool error???
pixman-1.so /usr/local/lib/libglitz.so -lpng /usr/local/lib/libxcb-render- util.so /usr/local/lib/libxcb-render.so /usr/local/lib/libXrender.so /usr/local/lib/libX11.so /usr/local/lib/libxcb.so /usr/local/lib/libXau.so /usr/local/lib/libXdmcp.so -lrpcsvc /usr/local/lib/libpango-1.0.so -lm /usr/local/lib/libfontconfig.so /usr/local/lib/libfreetype.so -lz /usr/local/lib/libexpat.so /usr/local/lib/libgmodule-2.0.so /usr/local/lib/libdbus-1.so -L/usr/local/lib/python2.6/config -lpython2.6 - lpth -lutil /usr/local/lib/libgobject-2.0.so /usr/local/lib/libglib-2.0.so - licui18n /usr/local/lib/libintl.so /usr/local/lib/libiconv.so /usr/local/lib/libpcre.so -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath - Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib/firefox /usr/bin/ld: cannot find -lpth libtool: link: rm -f ".libs/epiphanyS.o" gmake[4]: *** [epiphany] Error 1 gmake[4]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.26.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/www/epiphany. *** Error code 1 Stop in /usr/ports/www/epiphany. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20090804-97698-1r4y0tv-0 env make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/epiphany (unknown build error) Command failed [exit code 1]: /usr/local/sbin/portinstall www/epiphany ___ 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: is upgrade of devel/lib{tool, tldl}15 to devel/lib{tool, tldl}22 worth it?
Scott Bennett wrote: > I see that /usr/ports/UPDATING describes an upgrade of devel/libtool15 > and devel/libtldl15 to devel/libtool22 and devel/libtldl22, respectively. > Is this a good enough thing to do to justify the probable misery and risk > of disaster that would be necessary to get through it? Excessive dramatics aside, the short answer is yes. The longer answer is that the process described in UPDATING (using either portupgrade or portmaster) is painless. Also, if you don't do the update now the next time you try to build a port that requires libtool you _will_ have pain. hope this helps, Doug -- This .signature sanitized for your protection ___ 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: status of FreeBSD ports you maintain as of 20090705
Diego Depaoli wrote: > There are too many ports and too few people who care them. > IMHO the options are: > - decrease the number of ports We trim dead/useless ports all the time. > - increase the number of volunteers/committers/testers... This is the only valid answer for FreeBSD. > - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Doug -- This .signature sanitized for your protection ___ 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: compile error www/epiphany ? libtool error ???
> pixman-1.so /usr/local/lib/libglitz.so -lpng /usr/local/lib/libxcb-render- > util.so /usr/local/lib/libxcb-render.so /usr/local/lib/libXrender.so > /usr/local/lib/libX11.so /usr/local/lib/libxcb.so /usr/local/lib/libXau.so > /usr/local/lib/libXdmcp.so -lrpcsvc /usr/local/lib/libpango-1.0.so -lm > /usr/local/lib/libfontconfig.so /usr/local/lib/libfreetype.so -lz > /usr/local/lib/libexpat.so /usr/local/lib/libgmodule-2.0.so > /usr/local/lib/libdbus-1.so -L/usr/local/lib/python2.6/config -lpython2.6 - > lpth -lutil /usr/local/lib/libgobject-2.0.so /usr/local/lib/libglib-2.0.so > - licui18n /usr/local/lib/libintl.so /usr/local/lib/libiconv.so > /usr/local/lib/libpcre.so -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath > - Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib/firefox > /usr/bin/ld: cannot find -lpth > libtool: link: rm -f ".libs/epiphanyS.o" > gmake[4]: *** [epiphany] Error 1 > gmake[4]: Leaving directory > `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[3]: *** > [all-recursive] Error 1 > gmake[3]: Leaving directory > `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[2]: *** [all] > Error 2 > gmake[2]: Leaving directory > `/usr/ports/www/epiphany/work/epiphany-2.26.3/src' gmake[1]: *** > [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.26.3' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/www/epiphany. > *** Error code 1 > > Stop in /usr/ports/www/epiphany. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portinstall20090804-97698-1r4y0tv-0 env make > ** Fix the problem and try again. > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > ! www/epiphany (unknown build error) > Command failed [exit code 1]: /usr/local/sbin/portinstall www/epiphany Just thought I would add the following info (but as I am probing in the dark the info in probably useless!!: dns1# pwd /usr/ports/www/epiphany/work/epiphany-2.26.3/src dns1# fgrep epiphany ./* | grep rm ./Makefile: @rm -f epiphany$(EXEEXT) ./Makefile.in: @rm -f epiphany$(EXEEXT) ./Makefile.in.bak: @rm -f epiphany$(EXEEXT) ./Makefile.in.bak.bak: @rm -f epiphany$(EXEEXT) ./epiphany.c:"epiphany.PermissionInfo", /* tp_name */ ./epiphany.c:"epiphany.PermissionManager", /* tp_name */ dns1# ___ 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: recent update causes perl5.10 build failure
Scott Bennett wrote:
> Keep in mind that this experience did appear to reveal a portmaster bug.
> After the "portmaster -w -v -a" had already asked whether to rebuild perl5.8
> even though it had a +IGNOREME file and had gotten an enter key in response,
> which should have selected the "n" shown as the default ("[n]"), it later
> went ahead and built perl5.8 anyway. From what you and the documentation
> have told me, that should never happen.
I don't think it can happen if the build of all the dependencies is
under portmaster's control. However there are edge cases when
dependencies don't show up when portmaster polls the port for the list
but the ports infrastructure builds them anyway. I'd have to look at a
log of the whole session to be sure.
Having both perl5.8 and perl5.10 installed at the same time is kind of
an odd configuration, and could very well produce the kind of edge
case I described above.
hope this helps,
Doug
--
This .signature sanitized for your protection
___
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: Compile error mail/alpine
David Southwell wrote: > I have tried with: > WITH_THREADS=true > WITH_MOUSE=true > WITHOUT_NLS=true > WITHOUT_ISPELL=true > WITHOUT_NOSPELL=true > WITH_PICO=true > WITH_IPV6=true > WITH_LDAP=true > WITHOUT_PASSFILE=true > WITH_CONS25=true > WITHOUT_QUOTA=true > WITH_MAILDIR=true > > AND > WITHOUT_IPV6=true This isn't going to make a difference. > With the same results > > openssl: > dns1# pkg_info |grep openssl > openssl-0.9.8k_2SSL and crypto library > php5-openssl-5.2.10 The openssl shared extension for php > py26-openssl-0.8_1 Python interface to the OpenSSL library > > I also recompiled openssl to make sure all was well. Do you still have the openssl stuff in the base? This might cause a conflict such as the one you're seeing. Also, try disabling threads in OPTIONS and see if it builds for you then. Doug -- This .signature sanitized for your protection ___ 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: Getting a lot of - pkg_version: corrupted record (pkgdep line without argument), ignoring
eculp wrote: > I rebuilt the packages and all is well. Glad to hear that it worked out for you. :) > Thanks again for the explanation, the script and especially for > Postmaster that I have been using almost exclusively since the first > version and has been improving .with each subsequent release. Thank you for the kind words, they are appreciated. Doug -- This .signature sanitized for your protection ___ 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: status of FreeBSD ports you maintain as of 20090705
,--- You/Doug (Tue, 04 Aug 2009 08:26:08 -0700) * | > - increase the number of volunteers/committers/testers... | This is the only valid answer for FreeBSD. `---* Take a look at the PR submission and update dates in http://www.freebsd.org/cgi/query-pr.cgi?pr=137046 (the port I maintain). Doesn't it seem excessive to you, for an update as simple as that? Wouldn't it be better for everybody if more people could commit the changes in their ports themselves? (Subject to a commit-privilege revocation on a substantial breakage anyplace). How could I, for example, turn from a volunteer to a committer? Take also a look at the history of an attempt to volunteer elsewhere in http://www.freebsd.org/cgi/query-pr.cgi?pr=136263. Something doesn't feel right about the way ports are handled in FreeBSD these days. Of course, the easiest is to dismiss the voices of discontent. -- Alex -- alex-goncha...@comcast.net -- ___ 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: is upgrade of devel/lib{tool, tldl}15 to devel/lib{tool, tldl}22 worth it?
On Tue, Aug 04, 2009 at 06:56:06PM +0400, Dmitry Marakasov wrote:
> * Scott Bennett (benn...@cs.niu.edu) wrote:
> > Has anyone done this new upgrade and survived yet?
>
> I had no problems. There are not really many ports which depend on
> libltdl anyway.
I've just done it ('portupgrade -o devel/libtool22 libtool-1.5\*')
without any problems -- but it was on a machine with only a small
number ( <100 ) ports installed.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
___
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: devel/boost: new patch for testing update to 1.39
On Tue, 4 Aug 2009 14:28:02 +0400, Alexander Churanov wrote: > 2009/8/4 Mel Flynn : > > I think for the time being PySTE support should be off by default, > > because it pulls in a second libc and databases/akonadi plus kdeedu[34] > > use boost-python and because gccxml looks like a dead project. > > Agree. PySTE was disabled before boost split, would be nice to have it disabled for now also. > > ports/123927 could be solved/prevented by using a WANT_BOOST_PYSTE in > > dependent ports that rely on boost having PYSTE and using PKGNAMESUFFIX > > plus pkg_info to verify if boost-python-libs is boost-python-pyste-libs - > > as a stop-gap. > > Well, if the user installs some port that depends on > boost-python-libs, the user gets boost-python-libs installed. Then the > user wants to install another port that depends on > boost-python-pyste-libs. Would this succeed? there is no any port depending on pyste and I doubt there will be one in near future. Pulling gcc3 for newer systems because of hardly potential inconvenience seems to be excessive for me. Regards, Max signature.asc Description: This is a digitally signed message part.
Which JDK port to use?
I see diablo-jdk-1.5.0.07.01_15 and jdk-1.5.0.16p9_2,1 Which should I use? ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
In message <20090803155055.ga31...@titania.njm.me.uk>, N.J. Mann (n...@njm.me.uk) wrote: > In message <20090803125519.ga60...@twisted.net>, > Troy (t...@twisted.net) wrote: > > I was trying to upgrade apr-gdbm-db42-1.3.6.1.3.8 to 1.3.7.1.3.8 and ran > > into the following error. My libtool was just upgraded to libtool-2.2.6a > > so there may be a conflict there. Anyone have ideas? > > > > > > checking minix/config.h usability... no > > checking minix/config.h presence... no > > checking for minix/config.h... no > > checking whether it is safe to define __EXTENSIONS__... yes > > checking for library containing strerror... none required > > checking whether system uses EBCDIC... no > > performing libtool configuration... > > ./configure: 9753: Syntax error: word unexpected (expecting ")") > > *** Error code 2 > > > > Stop in /usr/ports/devel/apr. > > *** Error code 1 > > > > Stop in /usr/ports/devel/apr. > > I am also having problems updating devel/apr. In my case it gets past > the configure stage and fails during the compile stage: > > % > > ===> Building for apr-gdbm-db43-1.3.7.1.3.8 > cd /usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7; /usr/bin/env > TMPDIR="/home/njm/tmp" TMPDIR="/home/njm/tmp" SHELL=/bin/sh NO_LINT=YES > ACLOCAL=/usr/local/bin/aclocal-1.9 AUTOMAKE=/usr/local/bin/automake-1.9 > AUTOMAKE_VERSION=19 AUTOCONF=/usr/local/bin/autoconf-2.62 > AUTOHEADER=/usr/local/bin/autoheader-2.62 > AUTOIFNAMES=/usr/local/bin/ifnames-2.62 AUTOM4TE=/usr/local/bin/autom4te-2.62 > AUTORECONF=/usr/local/bin/autoreconf-2.62 > AUTOSCAN=/usr/local/bin/autoscan-2.62 > AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262 > LIBTOOL=/usr/local/bin/libtool LIBTOOLIZE=/usr/local/bin/libtoolize > LIBTOOL_M4=/usr/local/share/aclocal/libtool.m4 PREFIX=/usr/local > LOCALBASE=/usr/local X11BASE=/usr/local MOTIFLIB="-L/usr/local/lib -lXm > -lXp" LIBDIR="/usr/lib" CC="cc" CFLAGS="-O2 -fno-strict-aliasing -pipe" > CXX="c++" CXXFLAGS="-O2 -fno-strict-aliasing -pipe" MANPREFIX="/usr/local" > BSD_INSTALL_PROGRAM="install -s -m 555" BSD_INSTALL_SCRIPT="install -m > 555" BSD_INSTALL_DATA="install -m 444" BSD_INSTALL_ > MAN="install -m 444" /usr/bin/make > /bin/sh /libtool --silent --mode=compile cc -O2 -fno-strict-aliasing -pipe > -DHAVE_CONFIG_H-I./include > -I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include/arch/unix > -I./include/arch/unix > -I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include/arch/unix > -I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include -o > passwd/apr_getpass.lo -c passwd/apr_getpass.c && touch passwd/apr_getpass.lo ^ | This is the why it fails. In the relevant makefile this is actually: ./build/apr_rules.mk:38:LIBTOOL=$(SHELL) $(top_builddir)/libtool but top_buildir is not defined anywhere in the makefiles. If I set it then everything works. If I change the line above to use top_blddir instead of top_builddir it works. So, why isn't it defined? I looked through the config files - I know nothing about autoconf, automake, &c., and found: ./config.log:17410:LIBTOOL='$(SHELL) $(top_builddir)/libtool' ./config.log:17611:top_builddir='/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7' but I do not know whether the syntax of the second line is correct (the path is for my setup). Anyway, I tried compiling after making the above change and it worked until it changed directory into apr/work/apr-util-1.3.8 whereapon the same problem manifested. This time though I had to change the line in build/rules.mk to be LIBTOOL=$(SHELL) $(apr_builddir)/libtool and that did the trick: I now have an updated devel/apr. I really would like to get to the bottom of why this is failing for me, even if it is not failing for anyone else. Any and all suggetions accepted. Cheers, Nick. -- ___ 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: status of FreeBSD ports you maintain as of 20090705
2009/8/4 Doug Barton : > Diego Depaoli wrote: >> There are too many ports and too few people who care them. >> IMHO the options are: >> - decrease the number of ports > We trim dead/useless ports all the time. >> - increase the number of volunteers/committers/testers... > This is the only valid answer for FreeBSD. How? I think your following comment (even smiled) isn't the right starting point. >> - switch to a multi-level solution (e.g. Archlinux). > In DiegoBSD you should feel free to use any solution you think is > useful. :) Please look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 Ok, I agree, is an useless port, but 3 months without further notices are enough to demotivate any volunteer. Cheers -- Diego Depaoli ___ 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: devel/boost: new patch for testing update to 1.39
2009/8/4 Max Brazhnikov : > there is no any port depending on pyste and I doubt there will be one in near > future. Pulling gcc3 for newer systems because of hardly potential > inconvenience seems to be excessive for me. OK, if there are really no ports depending on it, then I'll implement the proposed WITH_PYSTE switch, without mangling it in the package name. Users who specifycally need Pyste will have to build their custom version of boost-python-libs and deinstall/reinstall. Sincerely, Alexander Churanov, maintainer of devel/boost-* ___ 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: Compile error mail/alpine
On Tuesday 04 August 2009 01:15:04 David Southwell wrote:
> latest error messages:
>
> cc -std=gnu99 -g -D_THREAD_SAFE -O2 -fno-strict-aliasing -pipe -
> DLDAP_DEPRECATED -rpath=/usr/local/lib -o alpine addrbook.o adrbkcmd.o
> after.o alpine.o arg.o busy.o colorconf.o confscroll.o context.o dispfilt.o
> flagmaint.o folder.o help.o imap.o init.o kblock.o keymenu.o ldapconf.o
> listsel.o mailcmd.o mailindx.o mailpart.o mailview.o newuser.o pattern.o
> pipe.o print.o radio.o remote.o reply.o roleconf.o send.o setup.o signal.o
> status.o takeaddr.o titlebar.o smime.o date.o -lcrypt -lpam -L/usr/lib -
> L/usr/local/openssl/lib -L/usr/local/lib ../pico/libpico.a
> ../pico/osdep/libpicoosd.a ../pith/libpith.a ../pith/osdep/libpithosd.a
> ../pith/charconv/libpithcc.a osdep/libpineosd.a ../c-client/c-client.a
> /usr/local/lib/libldap.so -lcrypto -ltinfo /usr/local/lib/liblber.so -lssl
> - Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib
> ../c-client/c-client.a(osdep.o)(.text+0x68a1): In function
> `ssl_onceonlyinit':
> /usr/ports/mail/alpine/work/alpine-2.00/imap/c-client/osdep.c:335: warning:
> warning: tmpnam() possibly used unsafely; consider using mkstemp()
> after.o(.text+0x36d): In function `start_after':
> /usr/ports/mail/alpine/work/alpine-2.00/alpine/after.c:77: undefined
> reference to `pthread_create'
David, given that all your errors posted in the last 24 hours point to a
messed up pth/pthread installation I suggest you look into that before trying
to build more ports.
The shell archive attached should compile and run cleanly, by typing "make
run" once extracted. If it does not, then even the base compiler/linker cannot
find pthread, which is not a good thing, but at least you know where to start
(reinstall world and possibly kernel).
--
Mel
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file". Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# threadtest/BSDmakefile
# threadtest/thrtest.c
#
echo x - threadtest/BSDmakefile
sed 's/^X//' >threadtest/BSDmakefile << 'd68d3d39019a946b87b33afe0474b0cc'
XPROG=thrtest
XNO_MAN=yes
XLDFLAGS+=-pthread
X
Xrun: ${PROG}
X ${.OBJDIR}/${PROG}
X
X.include
d68d3d39019a946b87b33afe0474b0cc
echo x - threadtest/thrtest.c
sed 's/^X//' >threadtest/thrtest.c << '22cb4804387108296f45df39552f86e9'
X#include
X#include
X#include
X#include
X
Xvoid *thr_main(void *priv);
X
Xint main(int argc, char **argv)
X{
X pthread_t tid[5];
X int i, res;
X
X printf("main\n");
X
X for(i=0; i<5; i++)
X {
X res = pthread_create(&tid[i], NULL, thr_main, NULL);
X if( res )
X errc(EXIT_FAILURE, res, "pthread_create");
X }
X for(i=0; i<5; i++)
X {
X int *ex;
X
X ex = malloc(sizeof(int));
X if( !ex )
X err(EXIT_FAILURE, "malloc: %zu bytes", sizeof(int));
X res = pthread_join(tid[i], (void*)&ex);
X if( res )
X errc(EXIT_FAILURE, res, "pthread_join");
X }
X
X return (0);
X}
X
Xvoid *thr_main(void *priv)
X{
X printf("Thread tid %u\n", (unsigned int)pthread_self());
X
X return (priv);
X}
22cb4804387108296f45df39552f86e9
exit
___
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: Which JDK port to use?
On Tue, Aug 4, 2009 at 8:39 AM, Steven Friedrich wrote: > I see > diablo-jdk-1.5.0.07.01_15 > and > jdk-1.5.0.16p9_2,1 > > Which should I use? > The diablo-* ports are the binary, pre-compiled versions of the JDK, and require a download from the FreeBSD Foundation website. The non-diablo-* ports are the source ports, and require a working JDK to be installed, in order to compile the port. Go with the diablo version first. If you need a more current version, then that can be used to compile the newer (non-diablo) port. -- Freddie Cash fjwc...@gmail.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: recent update causes perl5.10 build failure
On Tuesday 04 August 2009 08:33:08 am Doug Barton wrote:
> Scott Bennett wrote:
> > Keep in mind that this experience did appear to reveal a portmaster
> > bug. After the "portmaster -w -v -a" had already asked whether to rebuild
> > perl5.8 even though it had a +IGNOREME file and had gotten an enter key
> > in response, which should have selected the "n" shown as the default
> > ("[n]"), it later went ahead and built perl5.8 anyway. From what you and
> > the documentation have told me, that should never happen.
>
> I don't think it can happen if the build of all the dependencies is
> under portmaster's control. However there are edge cases when
> dependencies don't show up when portmaster polls the port for the list
> but the ports infrastructure builds them anyway. I'd have to look at a
> log of the whole session to be sure.
>
> Having both perl5.8 and perl5.10 installed at the same time is kind of
> an odd configuration, and could very well produce the kind of edge
> case I described above.
I had recently had problems moving packages from one fast computer to a slower
one for installs. When I did the forced, recursive update of perl-5.10 using
packages, there were ports only on the second computer that caused
portupgrade to force load perl-5.8.*. Portupgrade, when it is forced, didn't
pay attention to the registered conflicts. I had to delete the old version of
perl and reinstall 5.10. IIRC, portmanager -s would show me the ports that
were still linked to the old version of perl and could be compiled to upgrade
on the slower computer. There were numerous "pkdgb -L" runs to re-establish
the lost dependencies. Many were ports left behind by an incomplete removal
of kde4 and simply deleting them got rid of most of the problems.
I eventually got to where I could "portupgrade -Prf perl" and not have it
compile anything or install an older version of perl.
Tidy caused something similar and never was able to upgrade it and the
programs that use it with portupgrade.
Kent
>
>
> hope this helps,
>
> Doug
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
___
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: status of FreeBSD ports you maintain as of 20090705
On Tue 04 Aug 2009 at 09:21:07 PDT Diego Depaoli wrote: 2009/8/4 Doug Barton : Diego Depaoli wrote: There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports We trim dead/useless ports all the time. - increase the number of volunteers/committers/testers... This is the only valid answer for FreeBSD. How? I think your following comment (even smiled) isn't the right starting point. - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Please look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 Ok, I agree, is an useless port, but 3 months without further notices are enough to demotivate any volunteer. I've been a maintainer since the beginning of this year, and I've yet to have any of my updates go unnoticed for that long. I suspect that your PR is the exception rather than the rule. But it does suggest the need for more guidance on how maintainers can work effectively with the committers. What can we do to help streamline the process? What sort of things create extra, unnecessary work for committers? If a PR doesn't get picked up within a week, it doesn't seem to be showing up on the committers' scans when they're looking for something to do. Perhaps they should fix their scans, but perhaps the maintainer should post a message here, asking for someone to look at the PR? I've seen messages like that in the past, and the response has always been that one of the committers volunteers to take care of it. ___ 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: status of FreeBSD ports you maintain as of 20090705
On Tue, Aug 04, 2009 at 11:52:03AM -0700, Charlie Kester wrote: > On Tue 04 Aug 2009 at 09:21:07 PDT Diego Depaoli wrote: > >2009/8/4 Doug Barton : > >> Diego Depaoli wrote: > >>> There are too many ports and too few people who care them. > >>> IMHO the options are: > >>> - decrease the number of ports > >> We trim dead/useless ports all the time. > >>> - increase the number of ?volunteers/committers/testers... > >> This is the only valid answer for FreeBSD. > >How? I think your following comment (even smiled) isn't the right > >starting point. > > > >>> - switch to a multi-level solution (e.g. Archlinux). > >> In DiegoBSD you should feel free to use any solution you think is > >> useful. :) > >Please look at > >http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 > >Ok, I agree, is an useless port, but 3 months without further notices > >are enough to demotivate any volunteer. I've gone ahead and grabbed this PR. I will get to it when time permits (I've currently got a lot on my plate so please be patient). > I've been a maintainer since the beginning of this year, and I've yet to > have any of my updates go unnoticed for that long. I suspect that your > PR is the exception rather than the rule. I don't know if it's true or not but I certainly agree with you here. > But it does suggest the need for more guidance on how maintainers can > work effectively with the committers. What can we do to help streamline > the process? What sort of things create extra, unnecessary work for > committers? Submitting PRs in the proper format and that need no extra work is the best. Unfortunately knowing when an update is done is not something that one intuitively knows; it comes with practice. Paying attention to what you submitted compared to what got committed is a good way to find out if you made any mistakes. Talking to the committers (we don't bite, I promise) also helps. The IRC channels are documented on the wiki and are a great source of getting help with things. Another great resource on how to submit good PRs is the porter's handbook[1]. It covers a lot of things in detail that can help your PR handled get handled quickly and easily. > If a PR doesn't get picked up within a week, it doesn't seem to be > showing up on the committers' scans when they're looking for something > to do. Perhaps they should fix their scans, but perhaps the maintainer > should post a message here, asking for someone to look at the PR? I've > seen messages like that in the past, and the response has always been > that one of the committers volunteers to take care of it. Yes, if a PR goes unclaimed for some period of time please feel free to ask here for someone to take a look at it. -- WXS [1]: http://www.freebsd.org/doc/en/books/porters-handbook/ ___ 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: Compile error mail/alpine
> On Tuesday 04 August 2009 01:15:04 David Southwell wrote: > > latest error messages: > > > > cc -std=gnu99 -g -D_THREAD_SAFE -O2 -fno-strict-aliasing -pipe - > > DLDAP_DEPRECATED -rpath=/usr/local/lib -o alpine addrbook.o adrbkcmd.o > > after.o alpine.o arg.o busy.o colorconf.o confscroll.o context.o > > dispfilt.o flagmaint.o folder.o help.o imap.o init.o kblock.o keymenu.o > > ldapconf.o listsel.o mailcmd.o mailindx.o mailpart.o mailview.o newuser.o > > pattern.o pipe.o print.o radio.o remote.o reply.o roleconf.o send.o > > setup.o signal.o status.o takeaddr.o titlebar.o smime.o date.o -lcrypt > > -lpam -L/usr/lib - L/usr/local/openssl/lib -L/usr/local/lib > > ../pico/libpico.a > > ../pico/osdep/libpicoosd.a ../pith/libpith.a ../pith/osdep/libpithosd.a > > ../pith/charconv/libpithcc.a osdep/libpineosd.a ../c-client/c-client.a > > /usr/local/lib/libldap.so -lcrypto -ltinfo /usr/local/lib/liblber.so > > -lssl - Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib > > ../c-client/c-client.a(osdep.o)(.text+0x68a1): In function > > `ssl_onceonlyinit': > > /usr/ports/mail/alpine/work/alpine-2.00/imap/c-client/osdep.c:335: > > warning: warning: tmpnam() possibly used unsafely; consider using > > mkstemp() after.o(.text+0x36d): In function `start_after': > > /usr/ports/mail/alpine/work/alpine-2.00/alpine/after.c:77: undefined > > reference to `pthread_create' > > David, given that all your errors posted in the last 24 hours point to a > messed up pth/pthread installation I suggest you look into that before > trying to build more ports. > > The shell archive attached should compile and run cleanly, by typing "make > run" once extracted. If it does not, then even the base compiler/linker > cannot find pthread, which is not a good thing, but at least you know where > to start (reinstall world and possibly kernel). The thing that puzzled me was the following lines in the report (see above) /usr/bin/ld: cannot find -lpth libtool: link: rm -f ".libs/epiphanyS.o" ^^ David ___ 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: status of FreeBSD ports you maintain as of 20090705
On Tue, Aug 04, 2009 at 11:55:19AM -0400, Alex Goncharov wrote: > Wouldn't it be better for everybody if more people could commit the > changes in their ports themselves? (Subject to a commit-privilege > revocation on a substantial breakage anyplace). IMHO: no. Too many people automatically update their ports on a regular basis, and rely on us to not introduce brokenness. Having updates filtered through people that have shown themselves to having had a good track record seems prudent to me. Those folks who submit a number of good-quality PRs over a period of months tend to get noticed and nominated as committers. In the past year, we have added 10 ports committers. On occasion we turn someone down for an insufficient track record but it's rare, and most often they reapply once they have established one. (For the record, we have 157 ports comitters, of whom 131 have been active in the last 3 months.) > How could I, for example, turn from a volunteer to a committer? Please see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ for a good starting point. Its last section has cross-references to other sources of information. > Take also a look at the history of an attempt to volunteer elsewhere > in http://www.freebsd.org/cgi/query-pr.cgi?pr=136263. I understand your frustration, but the mysql ports are key ports that have been handled for a long time by their current maintainer. (He has 234 commits over the past 12 months, with only one maintainer-timeout during that time, which suggests to me that he's doing a good job.) I can see why a committer would be reluctant to commit that upgrade because of that. As for your other question: my own personal opinion is that we do have too many ports, but who decides when a port is "useful" enough? Other projects have a "process" to vote or otherwise decide on that. Several of our committers have voiced reluctance to add more "process" in the past, when the same subject has been brought up. Frankly, I wouldn't want to serve on the committee that decides :-) > Of course, the easiest is to dismiss the voices of discontent. Well, you have a right to your opinion ... I'm not saying that our process is perfect, far from it. (As an insider, especially as one of the people who wrangles the package-building machines, I have a front-row seat to many of our problems.) But IMHO it works better than it appears. mcl ___ 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: Which JDK port to use?
Steven Friedrich pisze: I see diablo-jdk-1.5.0.07.01_15 and jdk-1.5.0.16p9_2,1 Which should I use? Diablo can't do all the mumbo jumbo JDK can do. So, if you or your developers require more they can get out of Diablo go ahead and try JDK. Still, current JDK--or Diablo--installation is required to compile JDK. -- Cezary Morga "Have you ever observed that we pay much more attention to a wise passage when it is quoted than when we read it in the original author?" (Philip G. Hamerton) ___ 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"
What does py25 mean?
What does py25 mean? I can't seem to upgrade about 40 ports (the old versions of which now seem to be broken) evidently because the build of py25-gtk-2.13.1 fails with the message py25-cairo-1.8.6 needs Python 2.6 at least. But you specified 2.5. Well, of *I* did not specify 2.5. But howcome something called py25-cairo needs Python 2.6? What does that py25 on the front mean? Doesn't it mean python 2.5? If it doesn't mean that, what does it mean? If it does mean that, then howcome it needs python 2.6? -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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"
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. Warning: Duplicate INDEX entry: qt4-qmake-4.5.2 Warning: Duplicate INDEX entry: qt4-imageformats-4.5.2 Committers on the hook: miwi wxs Most recent CVS update was: ports/Mk/bsd.qt.mk ports/accessibility/qt4-accessible/Makefile ports/accessibility/qt4-accessible/distinfo ports/chinese/qt4-codecs-cn/Makefile ports/chinese/qt4-codecs-cn/distinfo ports/chinese/qt4-codecs-tw/Makefile ports/chinese/qt4-codecs-tw/distinfo ports/databases/py-qt4-sql/Makefile ports/databases/py-qt4-sql/distinfo ports/databases/qt4-ibase-plugin/Makefile ports/databases/qt4-ibase-plugin/distinfo ports/databases/qt4-ibase-plugin/files/Makefile.bsd ports/databases/qt4-mysql-plugin/Makefile ports/databases/qt4-mysql-plugin/distinfo ports/databases/qt4-mysql-plugin/files/Makefile.bsd ports/databases/qt4-odbc-plugin/Makefile ports/databases/qt4-odbc-plugin/distinfo ports/databases/qt4-odbc-plugin/files/Makefile.bsd ports/databases/qt4-pgsql-plugin/Makefile ports/databases/qt4-pgsql-plugin/distinfo ports/databases/qt4-pgsql-plugin/files/Makefile.bsd ports/databases/qt4-sql/Makefile ports/databases/qt4-sql/distinfo ports/databases/qt4-sql/pkg-plist ports/databases/qt4-sqlite-plugin/Makefile ports/databases/qt4-sqlite-plugin/distinfo ports/databases/qt4-sqlite-plugin/files/Makefile.bsd ports/databases/qt4-sqlite3-plugin/Makefile ports/databases/qt4-sqlite3-plugin/distinfo ports/databases/qt4-sqlite3-plugin/files/Makefile.bsd ports/devel/Makefile ports/devel/cmake/Makefile ports/devel/cmake/distinfo ports/devel/cmake/files/patch-Modules_FindQt4.cmake ports/devel/cmake/pkg-plist ports/devel/dbus-qt4/Makefile ports/devel/dbus-qt4/distinfo ports/devel/dbus-qt4/pkg-plist ports/devel/py-qt4-assistant/Makefile ports/devel/py-qt4-assistant/distinfo ports/devel/py-qt4-core/Makefile ports/devel/py-qt4-core/distinfo ports/devel/py-qt4-core/files/patch-configure.py ports/devel/py-qt4-core/pkg-plist ports/devel/py-qt4-dbus/Makefile ports/devel/py-qt4-dbus/distinfo ports/devel/py-qt4-designer/Makefile ports/devel/py-qt4-designer/distinfo ports/devel/py-qt4-designerplugin/Makefile ports/devel/py-qt4-designerplugin/distinfo ports/devel/py-qt4-help/Makefile ports/devel/py-qt4-help/distinfo ports/devel/py-qt4-qscintilla2/Makefile ports/devel/py-qt4-qscintilla2/distinfo ports/devel/py-qt4-qscintilla2/pkg-plist ports/devel/py-qt4-script/Makefile ports/devel/py-qt4-script/distinfo ports/devel/py-qt4-test/Makefile ports/devel/py-qt4-test/distinfo ports/devel/py-sip/Makefile ports/devel/py-sip/distinfo ports/devel/py-sip/files/bsd.pyqt.mk ports/devel/py-sip/pkg-plist ports/devel/qmake/Makefile ports/devel/qmake/distinfo ports/devel/qmake/files/Makefile.bsd ports/devel/qmake/files/qconfig.cpp ports/devel/qmake/pkg-descr ports/devel/qmake/pkg-plist ports/devel/qscintilla2/Makefile ports/devel/qscintilla2/distinfo ports/devel/qscintilla2/pkg-plist ports/devel/qscintilla2-designerplugin/Makefile ports/devel/qscintilla2-designerplugin/distinfo ports/devel/qt4/Makefile ports/devel/qt4/files/configure ports/devel/qt4/files/extrapatch-configure ports/devel/qt4/pkg-plist ports/devel/qt4-assistant/Makefile ports/devel/qt4-assistant/distinfo ports/devel/qt4-assistant-adp/Makefile ports/devel/qt4-assistant-adp/distinfo ports/devel/qt4-corelib/Makefile ports/devel/qt4-corelib/distinfo ports/devel/qt4-corelib/pkg-plist ports/devel/qt4-designer/Makefile ports/devel/qt4-designer/distinfo ports/devel/qt4-designer/pkg-plist ports/devel/qt4-help/Makefile ports/devel/qt4-help/distinfo ports/devel/qt4-help/pkg-plist ports/devel/qt4-help-tools/Makefile ports/devel/qt4-help-tools/distinfo ports/devel/qt4-libqtassistantclient/Makefile ports/devel/qt4-libqtassistantclient/distinfo ports/devel/qt4-libqtassistantclient/pkg-plist ports/devel/qt4-linguist/Makefile ports/devel/qt4-linguist/distinfo ports/devel/qt4-linguist/pkg-plist ports/devel/qt4-makeqpf/Makefile ports/devel/qt4-makeqpf/distinfo ports/devel/qt4-moc/Makefile ports/devel/qt4-moc/distinfo ports/devel/qt4-porting/Makefile ports/devel/qt4-porting/distinfo ports/devel/qt4-qdbusviewer/Makefile ports/devel/qt4-qdbusviewer/distinfo ports/devel/qt4-qt3support/Makefile ports/devel/qt4-qt3support/distinfo ports/devel/qt4-qt3support/pkg-plist ports/devel/qt4-qtestlib/Makefile ports/devel/qt4-qtestlib/distinfo ports/devel/qt4-qtestlib/pkg-plist ports/devel/qt4-qvfb/Makefile ports/devel/qt4-qvfb/distinfo ports/devel/qt4-rcc/Makefile ports/devel/qt4-rcc/distinfo ports/devel/qt4-script/Makefile ports/devel/qt4-script/distinfo ports/devel/qt4-script/pkg-plist ports/devel/qt4-uic/Makefile ports/devel/qt4-uic/distinfo ports/devel/qt4-uic3/Makefile ports/devel/qt4-uic3/distinfo ports/dns/bind9-sdb-postgresql/Makefile ports/dns/bind9-sdb-postgresql/distinfo ports/graphics/py-qt4-svg/Makefile ports/graphics/py-qt4-svg/distinfo ports/graphics/qt4-iconengines/Makefile ports/graphics/qt4-iconengin
Re: kdeedu-4.2.4 to 4.2.4_1 facile.cmxa compile error
On Sunday 02 August 2009 12:39:55 Martin Wilke wrote: >On Sunday 02 August 2009 05:06:19 Troy wrote: >>[ 12%] Generating solver.o >>File "_none_", line 1, characters 0-1: >>Error: Files /usr/local/lib/ocaml/facile/facile.cmxa >> and /usr/local/lib/ocaml/stdlib.cmxa >> make inconsistent assumptions over implementation Printf >*** Error code 2 > try to rebuild ocaml, after that rerun kdeedu4 For the archives: it's upgrading ocaml that creates the error and rebuilding facile that fixes it. Long story is available here: http://mail.kde.org/pipermail/kde-freebsd/2009-July/005914.html -- Mel ___ 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"
Thanks for KDE 4.3.0 and Qt 4.5 !
Big thanks to the FreeBSD KDE team for such a reactive update after the official release ! I've been testing it for few hours, using area51. It works great. Are there any differences between area51 and what have been committed to the ports repository ? The "s/MAKE_JOBS_SAVE/MAKE_JOBS_SAFE" fix should also be applied for "devel/qt4-qvfb/Makefile", "textproc/qt4-xmlpatterns/Makefile" and "databases/qt4-sql/Makefile". Cheers, Olivier -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: status of FreeBSD ports you maintain as of 20090705
,--- You/Mark (Tue, 4 Aug 2009 14:54:42 -0500) * | On Tue, Aug 04, 2009 at 11:55:19AM -0400, Alex Goncharov wrote: | > Wouldn't it be better for everybody if more people could commit the | > changes in their ports themselves? (Subject to a commit-privilege | > revocation on a substantial breakage anyplace). | | IMHO: no. Too many people automatically update their ports on a regular | basis, and rely on us to not introduce brokenness. Having updates | filtered through people that have shown themselves to having had a good | track record seems prudent to me. Agree on "prudent" -- but there is also a danger that new people are not coming into the play at the rate that will support FreeBSD's future needs. This may be not prudent, either. I personally do not use the port I maintain -- I grabbed it to learn the port building process, and enhance my experience with FreeBSD in general, to be of, perhaps, more use in the future (but the port is not completely unrelated to my other activities, which makes the maintainership meaningful). Could do more for the project -- but looks like nobody needs it. Oh, well, I am not insisting. (I do official builds and support CMUCL on FreeBSD, and that keeps my hands busy and spirits high already :-). | > Take also a look at the history of an attempt to volunteer elsewhere | > in http://www.freebsd.org/cgi/query-pr.cgi?pr=136263. | | I understand your frustration, but the mysql ports are key ports that have | been handled for a long time by their current maintainer. (He has 234 | commits over the past 12 months, with only one maintainer-timeout during | that time, which suggests to me that he's doing a good job.) I can see | why a committer would be reluctant to commit that upgrade because of that. How a new port would have broken the existing ones? (5.4 is not an upgrade -- it's a separate port not touching 5.0, 5.1 or 6.0.) Mind you, I have no regrets about not getting the ownership of that new port -- makes life easier for me. But the person who took it (and more power to him!), seems to be overbooked (judging by his responsiveness and the lag of MySQL ports behind the core distributions.) So, here was the port team's chance to add somebody who had learned the ropes already, could grow more and relieve the pressure on the current players. Not a big loss to miss the chance, but then the words "we need more volunteers, committers etc." sound insincere. Grow them rather than let people hoard ports that they don't actively maintain. -- Alex -- alex-goncha...@comcast.net -- ___ 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: [kde-freebsd] Thanks for KDE 4.3.0 and Qt 4.5 !
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Aug 04, 2009 at 11:44:53PM +0200, Olivier Smedts wrote: > Big thanks to the FreeBSD KDE team for such a reactive update after > the official release ! > > I've been testing it for few hours, using area51. It works great. > > Are there any differences between area51 and what have been committed > to the ports repository ? > nope > The "s/MAKE_JOBS_SAVE/MAKE_JOBS_SAFE" fix should also be applied for > "devel/qt4-qvfb/Makefile", "textproc/qt4-xmlpatterns/Makefile" and > "databases/qt4-sql/Makefile". Fixed thanks. > > Cheers, > Olivier > > -- > Olivier Smedts _ > ASCII ribbon campaign ( ) > e-mail: oliv...@gid0.org- against HTML email & vCards X > www: http://www.gid0.org- against proprietary attachments / \ > > "Il y a seulement 10 sortes de gens dans le monde : > ceux qui comprennent le binaire, > et ceux qui ne le comprennent pas." > ___ > kde-freebsd mailing list > kde-free...@kde.org > https://mail.kde.org/mailman/listinfo/kde-freebsd > See also http://freebsd.kde.org/ for latest information > - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkp4rn8ACgkQdLJIhLHm/OnhuACgiIyQ50v2W6IDW8cDG1Ww2IX7 qPgAn0jxWAzjLZv+vjuhP7Zb+qTlTnZT =Alzd -END PGP SIGNATURE- ___ 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"
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: kdepim-4.3.0: no entry for /usr/ports/deskutils/kdepim4-runtime make_index: kdepim-4.3.0: no entry for /usr/ports/deskutils/kdepim4-runtime Committers on the hook: anders miwi nivit Most recent CVS update was: ports/Mk/bsd.kde4.mk ports/accessibility/kdeaccessibility4/Makefile ports/accessibility/kdeaccessibility4/distinfo ports/accessibility/kdeaccessibility4/pkg-plist ports/arabic/kde4-l10n/Makefile ports/arabic/kde4-l10n/distinfo ports/arabic/kde4-l10n/pkg-plist ports/astro/merkaartor/Makefile ports/audio/HVSC-Update/Makefile ports/audio/mumble/Makefile ports/audio/xmp/Makefile ports/chinese/kde4-l10n-zh_CN/Makefile ports/chinese/kde4-l10n-zh_CN/distinfo ports/chinese/kde4-l10n-zh_CN/pkg-plist ports/chinese/kde4-l10n-zh_TW/Makefile ports/chinese/kde4-l10n-zh_TW/distinfo ports/chinese/kde4-l10n-zh_TW/pkg-plist ports/databases/akonadi/Makefile ports/databases/akonadi/distinfo ports/databases/akonadi/pkg-plist ports/databases/qt4-sql/Makefile ports/deskutils/kdepim4/Makefile ports/deskutils/kdepim4/distinfo ports/deskutils/kdepim4/pkg-plist ports/deskutils/kdepimlibs4/Makefile ports/deskutils/kdepimlibs4/distinfo ports/deskutils/kdepimlibs4/pkg-plist ports/deskutils/kdeplasma-addons/Makefile ports/deskutils/kdeplasma-addons/distinfo ports/deskutils/kdeplasma-addons/pkg-plist ports/devel/automoc4/Makefile ports/devel/kdebindings4/Makefile ports/devel/kdebindings4/files/Makefile.kdebindings ports/devel/kdebindings4-python/Makefile ports/devel/kdebindings4-python-krosspython/Makefile ports/devel/kdebindings4-python-krosspython/distinfo ports/devel/kdebindings4-python-pykde4/Makefile ports/devel/kdebindings4-python-pykde4/distinfo ports/devel/kdebindings4-python-pykde4/pkg-plist ports/devel/kdesdk4/Makefile ports/devel/kdesdk4/distinfo ports/devel/kdesdk4/pkg-plist ports/devel/qmake/Makefile ports/devel/qmake/distinfo ports/devel/qmake/files/Makefile.bsd ports/devel/qmake/files/qconfig.cpp ports/devel/qmake/pkg-descr ports/devel/qmake/pkg-plist ports/devel/qmake4/Makefile ports/devel/qmake4/distinfo ports/devel/qmake4/files/Makefile.bsd ports/devel/qmake4/files/qconfig.cpp ports/devel/qmake4/pkg-plist ports/devel/qt4-qvfb/Makefile ports/french/kde4-l10n/Makefile ports/french/kde4-l10n/Makefile.man ports/french/kde4-l10n/distinfo ports/french/kde4-l10n/pkg-plist ports/games/kdegames4/Makefile ports/games/kdegames4/distinfo ports/games/kdegames4/pkg-plist ports/german/kde4-l10n/Makefile ports/german/kde4-l10n/Makefile.man ports/german/kde4-l10n/distinfo ports/german/kde4-l10n/pkg-plist ports/graphics/kcoloredit/Makefile ports/graphics/kcoloredit/distinfo ports/graphics/kdegraphics4/Makefile ports/graphics/kdegraphics4/distinfo ports/graphics/kdegraphics4/files/patch-libs__libkdcraw__CMakeLists.txt ports/graphics/kdegraphics4/pkg-plist ports/graphics/kgraphviewer/Makefile ports/graphics/kgraphviewer/distinfo ports/graphics/kgraphviewer/pkg-plist ports/graphics/kiconedit/Makefile ports/graphics/kiconedit/distinfo ports/graphics/kiconedit/pkg-plist ports/graphics/kpovmodeler/Makefile ports/graphics/kpovmodeler/distinfo ports/graphics/qt4-iconengines/Makefile ports/graphics/skanlite/Makefile ports/graphics/skanlite/distinfo ports/graphics/skanlite/pkg-plist ports/hebrew/kde4-l10n/Makefile ports/hebrew/kde4-l10n/distinfo ports/hebrew/kde4-l10n/pkg-plist ports/hungarian/kde4-l10n/Makefile ports/hungarian/kde4-l10n/distinfo ports/hungarian/kde4-l10n/pkg-plist ports/japanese/kde4-l10n/Makefile ports/japanese/kde4-l10n/distinfo ports/japanese/kde4-l10n/pkg-plist ports/korean/kde4-l10n/Makefile ports/korean/kde4-l10n/distinfo ports/korean/kde4-l10n/pkg-plist ports/math/eigen2/Makefile ports/math/eigen2/distinfo ports/math/eigen2/pkg-plist ports/misc/kde4-l10n/Makefile ports/misc/kde4-l10n/files/bsd.l10n.mk ports/misc/kde4-l10n-bg/Makefile ports/misc/kde4-l10n-bg/distinfo ports/misc/kde4-l10n-bg/pkg-plist ports/misc/kde4-l10n-bn_IN/Makefile ports/misc/kde4-l10n-bn_IN/distinfo ports/misc/kde4-l10n-bn_IN/pkg-plist ports/misc/kde4-l10n-ca/Makefile ports/misc/kde4-l10n-ca/distinfo ports/misc/kde4-l10n-ca/pkg-plist ports/misc/kde4-l10n-cs/Makefile ports/misc/kde4-l10n-cs/distinfo ports/misc/kde4-l10n-cs/pkg-plist ports/misc/kde4-l10n-csb/Makefile ports/misc/kde4-l10n-csb/distinfo ports/misc/kde4-l10n-csb/pkg-plist ports/misc/kde4-l10n-da/Makefile ports/misc/kde4-l10n-da/distinfo ports/misc/kde4-l10n-da/pkg-plist ports/misc/kde4-l10n-el/Makefile ports/misc/kde4-l10n-el/distinfo ports/misc/kde4-l10n-el/pkg-plist ports/misc/kde4-l10n-en_GB/Makefile ports/misc/kde4-l10n-en_GB/distinfo ports/misc/kde4-l10n-en_GB/pkg-plist ports/misc/kde4-l10n-eo/Makefile ports/misc/kde4-l10n-es/Makefile ports/misc/kde4-l10n-es/Makefile.man ports/misc/kde4-l10n-es/distinfo ports/misc/kde4-l10n-es/pkg-plist ports/misc/kde4-l10n-et/Makefile ports/misc/kde4-l10n-et/Makefile.man ports/misc
Re: What does py25 mean?
On Tue, Aug 4, 2009 at 4:48 PM, Lars Eighner wrote: > What does py25 mean? > > I can't seem to upgrade about 40 ports (the old versions of which now seem > to be broken) evidently because the build of > > py25-gtk-2.13.1 fails with the message > >py25-cairo-1.8.6 needs Python 2.6 at least. But you specified 2.5. > > Well, of *I* did not specify 2.5. > > But howcome something called py25-cairo needs Python 2.6? What does that > py25 on the front mean? Doesn't it mean python 2.5? If it doesn't mean > that, what does it mean? If it does mean that, then howcome it needs > python > 2.6? > > > -- > Lars Eighner > http://www.larseighner.com/index.html > 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 > > ___ > 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" > yes it means python 2.5 most likely for cairo the py25 was not bumped to py26 ___ 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: What does py25 mean?
On Tuesday 04 August 2009 17:28:59 matt donovan wrote: > On Tue, Aug 4, 2009 at 4:48 PM, Lars Eighner wrote: > > What does py25 mean? > > > > I can't seem to upgrade about 40 ports (the old versions of which now > > seem to be broken) evidently because the build of > > > > py25-gtk-2.13.1 fails with the message > > > >py25-cairo-1.8.6 needs Python 2.6 at least. But you specified 2.5. > > > > Well, of *I* did not specify 2.5. > yes it means python 2.5 most likely for cairo the py25 was not bumped to > py26 No, the package name (or actually the PKGNAMEPREFIX) is dynamically created from the *detected* python version. Also graphics/py-cairo has: USE_PYTHON= 2.6+ Which signals that it cannot work with python 2.5. If you install lang/python26, it should work, tho I haven't checked. -- Mel ___ 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: x11-toolkits/xview requires COMPAT_43TTY defined to build on -CURRENT
On Tue, Aug 4, 2009 at 3:45 AM, Tom Uffner wrote: > Mel Flynn wrote: >> >> So, the real fix should come from upstream. For the time being, this >> should work, marked MAKE_JOBS_UNSAFE while I was in there. The OSVERSION >> leaves a three week hole where things won't work, but that should be >> acceptable. > > Thank you for the patch. > > I'm guessing an upstream fix is pretty unlikely. I'd be surprised if > there were even 10 people still using xview for anything other than > legacy apps. My interest is because it's a dependency for sysutils/contool. > > and unfortunately it may all be pointless anyway because contool > won't run on my system for reasons i have yet to determine. Can't xconsole do the job for you instead of contool? BTW, what problems do you have with contool? Are they the same ones discussed before in these threads? http://lists.freebsd.org/pipermail/freebsd-hackers/2008-October/026516.html http://lists.freebsd.org/pipermail/freebsd-hackers/2008-November/026722.html -- My preferred quotation of Robert Louis Stevenson is "You cannot make an omelette without breaking eggs". Not because I like the omelettes, but because I like the sound of eggs being broken. ___ 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"
INDEX now builds successfully on 6.x
___ 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"
