Re: py-qt4-* troubles
On Wed, 6 May 2009 23:10:03 +0300, Max E. Kuznecov wrote: Hi, While trying to build games/anki I've found that several py-qt4-* ports are unbuildable. For instance graphics/py-qt4-svg complains: === Found saved configuration for py25-qt4-svg-4.4.4,1 === Extracting for py25-qt4-svg-4.4.4,1 = MD5 Checksum OK for PyQt-x11-gpl-4.4.4.tar.gz. = SHA256 Checksum OK for PyQt-x11-gpl-4.4.4.tar.gz. === Patching for py25-qt4-svg-4.4.4,1 === Applying FreeBSD patches for py25-qt4-svg-4.4.4,1 === py25-qt4-svg-4.4.4,1 depends on package: py25-sip=4.7.9 - found === py25-qt4-svg-4.4.4,1 depends on file: /usr/local/bin/python2.5 - found === py25-qt4-svg-4.4.4,1 depends on package: qt4-svg=4.4.3 - found === py25-qt4-svg-4.4.4,1 depends on package: qt4-qmake=4.4.3 - found === py25-qt4-svg-4.4.4,1 depends on shared library: qscintilla2.5 - found === Configuring for py25-qt4-svg-4.4.4,1 cd /usr/ports/graphics/py-qt4-svg/work/PyQt-x11-gpl-4.4.4 /usr/bin/env PYQT4_COMPONENT=svg PYTHON=/usr/local/bin/python2.5 MOC=/usr/local/bin/moc-qt4 UIC=/usr/local/bin/uic-qt4 CPPFLAGS= LIBS= QMAKE=/usr/local/bin/qmake-qt4 QMAKESPEC=/usr/local/share/qt4/mkspecs/freebsd-g++ QTDIR=/usr/local SHELL=/bin/sh CONFIG_SHELL=/bin/sh /usr/local/bin/python2.5 configure.py -b /usr/local/bin -d /usr/local/lib/python2.5/site-packages -p /usr/local/lib/qt4/plugins -q /usr/local/bin/qmake-qt4 --confirm-license --enable QtSvg --qsci-api --qsci-api-destdir=/usr/local/share/qt4/qsci --sipdir /usr/local/share/py-sip Determining the layout of your Qt installation... This is the GPL version of PyQt 4.4.4 (licensed under the GNU General Public License) for Python 2.5.4 on freebsd7. Checking to see if the QtSvg module should be built... Qt v4.4.3 free edition is being used. SIP 4.7.9 is being used. The Qt header files are in /usr/local/include/qt4. The shared Qt libraries are in /usr/local/lib/qt4. The Qt binaries are in /usr/local/bin. The Qt mkspecs directory is in /usr/local/share/qt4. This PyQt module will be built: QtCore. The PyQt Python package will be installed in /usr/local/lib/python2.5/site-packages. The QScintilla API file will be installed in /usr/local/share/qt4/qsci/api/python. The PyQt .sip files will be installed in /usr/local/share/py-sip. Creating QScintilla API file... Creating top level Makefile... /usr/bin/sed -i.bak -e 's|mkspecs/freebsd-g++|share/qt4/mkspecs/freebsd-g++|' -e 's|CC = cc|CC = cc|' -e 's|CXX = c++|CXX = c++|' -e 's|LINK = c++|LINK = c++|' /usr/ports/graphics/py-qt4-svg/work/PyQt-x11-gpl-4.4.4/QtSvg/Makefile sed: /usr/ports/graphics/py-qt4-svg/work/PyQt-x11-gpl-4.4.4/QtSvg/Makefile: No such file or directory *** Error code 1 The same thing for www/py-qt4-webkit. I've reinstalled qt4 and all dependent ports but still no luck. uname -sr: FreeBSD 7.1-RELEASE-p2 and the most recent ports snapshot. I'd appreciate any hint about what to install/update in order to fix the issue. Thanks. Can't reproduce this, seems it's your local problem. Max ___ 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: orage-4.6.1
Hi Marco, Marco Alberoni writes: checking for xfce-mcs-manager = 4.4.0... not found I cannot reproduce this here. While looking through the configure script of ogre, I found out that xfce-mcs-manager is check if --enable-libxfce4mcs was specified when ogre gets configured. But this parameter is not added to the configure arguments from the ogre script. So I wonder how this could happen? Could you please send me the foll config.log from the work directory? ___ 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: orage-4.6.1
Oliver Lehmann writes: I cannot reproduce this here. While looking through the configure script of ogre, I found out that xfce-mcs-manager is check if --enable-libxfce4mcs was specified when ogre gets configured. But this parameter is not added to the configure arguments from the ogre script. So I wonder how this could happen? Could you please send me the foll config.log from the work directory? Everytime I wrote ogre I meant orage of course ;) ___ 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: orage-4.6.1
By any chance - do you still have the old libxfce4mcs installed? This would probably cause this as well. PS: sorry for spamming ;) ___ 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: orage-4.6.1
Hello, I'm not able to upgrade orage from 4.6.0 to 4.6.1... the last lines of make are: checking for xfce-mcs-manager = 4.4.0... not found *** The required package xfce-mcs-manager was not found on your system. *** Please install xfce-mcs-manager (atleast version 4.4.0) or adjust *** the PKG_CONFIG_PATH environment variable if you *** installed the package in a nonstandard prefix so that *** pkg-config is able to find it. === Script configure failed unexpectedly. The problem is xfce-mcs-manager port is, as you know very well, no more present!!! Thanks for your help and patience -- Marco Alberoni Have you read /usr/ports/UPDATING ? The answer is there. /Leslie -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: orage-4.6.1
В Thu, 7 May 2009 10:46:26 +0200 (MEST) Marco Alberoni m.alber...@cineca.it пишет: MA Hello, I'm not able to upgrade orage from 4.6.0 to 4.6.1... the MA last lines of make are: MA MA MA checking for xfce-mcs-manager = 4.4.0... not found MA *** The required package xfce-mcs-manager was not found on your MA system. *** Please install xfce-mcs-manager (atleast version 4.4.0) MA or adjust *** the PKG_CONFIG_PATH environment variable if you MA *** installed the package in a nonstandard prefix so that MA *** pkg-config is able to find it. MA === Script configure failed unexpectedly. MA MA MA The problem is xfce-mcs-manager port is, as you know very well, no MA more present!!! cause you don't read UPDATING, right ? 20090304 by oliver@ MA MA MA Thanks for your help and patience MA -- --- Sergey V Dyatko aka tiger | sergey.dya...@gmail.com /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://tiger.bsd.by X - NO Word docs in e-mail | XMPP: ti...@jabber.org.by / \ --- ___ 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
xfce4-netload-plugin doesn't compile
Hi, when I try update i got following error: build log: http://msk.bsd.by/files/netload-script.txt notebook# pkg_version -vs xfce4-netload-plugin\* fce4-netload-plugin-0.4.0_6 needs updating (port has 0.4.0_7) 1st box: FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Fri May 1 16:43:49 EEST 2009 r...@notebook.domain:/usr/obj/usr/src/sys/tiger-asus-a6m i386 2nd box: FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #25: Wed Apr 22 12:48:35 EEST 2009 r...@tiger.domain:/usr/obj/usr/src/sys/tiger-desktop i386 -- wbr, tiger ___ 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: orage-4.6.1
В Thu, 07 May 2009 11:24:22 +0200 Oliver Lehmann oli...@freebsd.org пишет: OL By any chance - do you still have the old libxfce4mcs installed? OL This would probably cause this as well. assume that this is the problem, I have 2 machines are successfully updated (both is -CURRENT) OL OL PS: sorry for spamming ;) -- wbr, tiger ___ 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: MAKE_JOBS_UNSAFE+= shells/bash, textproc/ispell
David O'Brien wrote: I was under the impression that MAKE_JOBS_UNSAFE was the default and one had to explicity put MAKE_JOBS_SAFE=yes in a port. By default, it is neither SAFE or UNSAFE. By default, its always without the -j argument. Sorry to hijack! But how can you set the ports build to use -j2 Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.325 / Virus Database: 270.12.21/2102 - Release Date: 05/07/09 05:57:00 ___ 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: MAKE_JOBS_UNSAFE+= shells/bash, textproc/ispell
On Thu, May 07, 2009 at 03:32:43PM +0200, Johan Hendriks wrote: David O'Brien wrote: I was under the impression that MAKE_JOBS_UNSAFE was the default and one had to explicity put MAKE_JOBS_SAFE=yes in a port. By default, it is neither SAFE or UNSAFE. By default, its always without the -j argument. Sorry to hijack! But how can you set the ports build to use -j2 By default it uses the number of cores in the system. If you want to change that you can use MAKE_JOBS_NUMBER. -- 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
pear v1.8.1 build issues with php v4.4.9
Hi, I've narrowed down a problem when building pear v1.8.1 with php v4.4.9. There is an XML parse error when the port tries to install Structure_Graph. NB pear v1.7.2 builds ok with php v4.4.9. It's the update to pear v1.8.1 that breaks it. Also, with php v5 pear v1.8.1 builds ok. So it just seems to be the combination of pear v1.8.x and php v4. Here's the relevant part of the build: - Installing selected packages.. Installing bootstrap package: PEAR...warning: pear/PEAR requires package pear/Archive_Tar (recommended version 1.3.3) warning: pear/PEAR requires package pear/Structures_Graph (recommended version 1.0.2) warning: pear/PEAR requires package pear/Console_Getopt (recommended version 1.2.3) install ok: channel://pear.php.net/PEAR-1.8.1 PEAR: Optional feature webinstaller available (PEAR's web-based installer) PEAR: Optional feature gtkinstaller available (PEAR's PHP-GTK-based installer) PEAR: Optional feature gtk2installer available (PEAR's PHP-GTK2-based installer) PEAR: To install optional features use pear install pear/PEAR#featurename Installing bootstrap package: Structures_Graph...downloading Structures_Graph-1.0.2.tgz ... Starting to download Structures_Graph-1.0.2.tgz (30,947 bytes) .done: 30,947 bytes XML Error: 'not well-formed (invalid token)' on line '10' Download of pear/Structures_Graph succeeded, but it is not a valid package archive Error: cannot download pear/Structures_Graph Download failed Installing local package: Archive_Tar-stable.install ok: channel://pear.php.net/Archive_Tar-1.3.3 Installing local package: Console_Getopt-stable...install ok: channel://pear.php.net/Console_Getopt-1.2.3 === Registering installation for pear-1.8.1 - Even though the install of Structures_Graph fails, the port installation succeeds. Manually attempting the install of Structures_Graph unsurprisingly gives the same error: - # pear -V PEAR Version: 1.8.1 PHP Version: 4.4.9 Zend Engine Version: 1.3.0 Running on: FreeBSD webmail0 7.1-RELEASE-p5 FreeBSD 7.1-RELEASE-p5 #0: Tue Apr 28 17:55:20 UTC 2009xxx amd64 # pear install Structures_Graph downloading Structures_Graph-1.0.2.tgz ... Starting to download Structures_Graph-1.0.2.tgz (30,947 bytes) .done: 30,947 bytes XML Error: 'not well-formed (invalid token)' on line '10' Download of pear/Structures_Graph succeeded, but it is not a valid package archive Error: cannot download pear/Structures_Graph Download failed install failed - I see they changed to packages.xml v2.0 with pear v1.8.1. However, it's supposed to also woth with php v4.4.0 of newer. Is this a pear problem, rather than ports? Many thanks for your time. -- Mark Powell - UNIX System Administrator - The University of Salford Information Learning Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 6843 Fax: +44 161 295 5888 www.pgp.com for PGP key ___ 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
generate index file which respects non default environment
Hello List, is there any possibility to generate an index file which respects environment, non default OPTIONS? I mean if for example OVERRIDE_LINUX_BASE_PORT is defined as f8, then I expect the INDEX should reflect it. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: generate index file which respects non default environment
On Thu, 07 May 2009 20:24:07 +0400 Boris Samorodov wrote: is there any possibility to generate an index file which respects environment, non default OPTIONS? I mean if for example OVERRIDE_LINUX_BASE_PORT is defined as f8, then I expect the INDEX should reflect it. Actually, make index respects the environment. There was some other error at my testing machine. Sorry for the noise. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: generate index file which respects non default environment
On Thu, May 07, 2009 at 08:24:07PM +0400, Boris Samorodov wrote: Hello List, is there any possibility to generate an index file which respects environment, non default OPTIONS? I mean if for example OVERRIDE_LINUX_BASE_PORT is defined as f8, then I expect the INDEX should reflect it. I always thought that everything put into /etc/make.conf (or include derivatives) would be accounted for during make index in /usr/ports. Is it not true for OVERRIDE_LINUX_BASE_PORT=f8? Alexey. ___ 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: generate index file which respects non default environment
On Thu, 7 May 2009 18:49:14 +0200 Alexey Shuvaev wrote: On Thu, May 07, 2009 at 08:24:07PM +0400, Boris Samorodov wrote: is there any possibility to generate an index file which respects environment, non default OPTIONS? I mean if for example OVERRIDE_LINUX_BASE_PORT is defined as f8, then I expect the INDEX should reflect it. I always thought that everything put into /etc/make.conf (or include derivatives) would be accounted for during make index in /usr/ports. Is it not true for OVERRIDE_LINUX_BASE_PORT=f8? Actually it is. I worked with ports-mgmt/tinderbox and something was wrong with my script/configuration. And when I checked up the ports tree at the host system at one console and removed /etc/make.conf at another. Too many tasks to do simultaneously. :-( WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
how -jX - [WAS Re: MAKE_JOBS_UNSAFE+= shells/bash, textproc/ispell
Johan Hendriks wrote: Sorry to hijack! But how can you set the ports build to use -j2 FORCE_MAKE_JOBS=yes|no ## defaults off MAKE_JOBS_NUMBER=X ## defaults to number of cores MAKE_JOBS_SAFE=yes ## default no MAKE_JOBS_UNSAFE=yes ## default no See Mk/bsd.port.mk for more information. -- Philip M. Gollucci (pgollu...@ridecharge.com) p: 703.549.2050x206, did: 703.579.6947 Senior System Admin - RideCharge, Inc. http://ridecharge.com 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C 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: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. -- 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: xcb-util 0.3.4 breaks awesome
On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. OK. I've known about this break for quite some time now as there have been many Linux users who had this same problem. In case of something like this in the future, should I send a message to the maintainer telling him/her about the potential break? Also, to anyone who hasn't updated their xcb-util port yet, here's what I did to prevent tools like portmaster from installing the newer version: # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME Now in portmaster, I get the following message when using -a to update all my ports: === Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 === xcb-util-0.3.3 has an +IGNOREME file === Update anyway? [n] -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ 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: An enquiry about valgrind porting to FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Churanov wrote: Hi all! I am also interested in it. I have lots of questions about valgrind: 1) Is it working at all? I always receive SIGBUS on 7x. 2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org? 3) valgrind.org lists 3.4.1 as latest release, but there is 3.52 in ports, how is it possible? That's Revision 352 and not 3.52 nor 3.5.2... As far as I am aware Peter Wemm worked on a valgrind port which is available on p4. Haven't give it a twist yet as it seems that we need more work for amd64... I am teaching people C, C++ and UNIX API using FreeBSD at university. There is a need for memory-checking tool. Does anybody know any alternatives for FreeBSD 7? Alexander Churanov - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoDY4AACgkQi+vbBBjt66BmzgCfSA8k0n6iRFwBv/t6NdzqRSWT Lo4AnRA0KiArezFOt5e429rafycoxDym =JQif -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
Re: xcb-util 0.3.4 breaks awesome
On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote: On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. OK. I've known about this break for quite some time now as there have been many Linux users who had this same problem. In case of something like this in the future, should I send a message to the maintainer telling him/her about the potential break? Sending a HEADS UP message to the maintainer if you are aware of an issue would be a good courtesy and hopefully minimize any breakage. A short delay for a maintainer to address the issue is reasonable, but that is a slippery slope. I say give a reasonable amount of time for the breakage to be addressed (where the definition of reasonable is open to interpretation). If it isn't addressed, please move forward and commit. robert. Also, to anyone who hasn't updated their xcb-util port yet, here's what I did to prevent tools like portmaster from installing the newer version: # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME Now in portmaster, I get the following message when using -a to update all my ports: === Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 === xcb-util-0.3.3 has an +IGNOREME file === Update anyway? [n] -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
Re: xcb-util 0.3.4 breaks awesome
* Robert Noland (rnol...@freebsd.org) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. Holding back X or it's sub-components is really not an option. The applications have to keep up. xcb-util doesn't fall under my umbrella, exactly, but I do update it in Xorg sweeps on occasion. Unless the damage is widespread progress must continue. Awesome needs to be patched, updated or marked BROKEN temporarily. Sure, I've just did exactly that - marked awesome BROKEN in presence of newer xcb-util. The note above was for awesome users who, regardless of ports progression and updates, will need a way to use them :) -- 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
You have just received a virtual postcard from a friend !
You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the reply to this postcard button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe ___ 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: pear v1.8.1 build issues with php v4.4.9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Powell wrote: Hi, I've narrowed down a problem when building pear v1.8.1 with php v4.4.9. There is an XML parse error when the port tries to install Structure_Graph. NB pear v1.7.2 builds ok with php v4.4.9. It's the update to pear v1.8.1 that breaks it. Also, with php v5 pear v1.8.1 builds ok. So it just seems to be the combination of pear v1.8.x and php v4. Here's the relevant part of the build: - Installing selected packages.. Installing bootstrap package: PEAR...warning: pear/PEAR requires package pear/Archive_Tar (recommended version 1.3.3) warning: pear/PEAR requires package pear/Structures_Graph (recommended version 1.0.2) warning: pear/PEAR requires package pear/Console_Getopt (recommended version 1.2.3) install ok: channel://pear.php.net/PEAR-1.8.1 PEAR: Optional feature webinstaller available (PEAR's web-based installer) PEAR: Optional feature gtkinstaller available (PEAR's PHP-GTK-based installer) PEAR: Optional feature gtk2installer available (PEAR's PHP-GTK2-based installer) PEAR: To install optional features use pear install pear/PEAR#featurename Installing bootstrap package: Structures_Graph...downloading Structures_Graph-1.0.2.tgz ... Starting to download Structures_Graph-1.0.2.tgz (30,947 bytes) .done: 30,947 bytes XML Error: 'not well-formed (invalid token)' on line '10' Download of pear/Structures_Graph succeeded, but it is not a valid package archive Error: cannot download pear/Structures_Graph Download failed Installing local package: Archive_Tar-stable.install ok: channel://pear.php.net/Archive_Tar-1.3.3 Installing local package: Console_Getopt-stable...install ok: channel://pear.php.net/Console_Getopt-1.2.3 === Registering installation for pear-1.8.1 - Even though the install of Structures_Graph fails, the port installation succeeds. Manually attempting the install of Structures_Graph unsurprisingly gives the same error: - # pear -V PEAR Version: 1.8.1 PHP Version: 4.4.9 Zend Engine Version: 1.3.0 Running on: FreeBSD webmail0 7.1-RELEASE-p5 FreeBSD 7.1-RELEASE-p5 #0: Tue Apr 28 17:55:20 UTC 2009xxx amd64 # pear install Structures_Graph downloading Structures_Graph-1.0.2.tgz ... Starting to download Structures_Graph-1.0.2.tgz (30,947 bytes) .done: 30,947 bytes XML Error: 'not well-formed (invalid token)' on line '10' Download of pear/Structures_Graph succeeded, but it is not a valid package archive Error: cannot download pear/Structures_Graph Download failed install failed - I see they changed to packages.xml v2.0 with pear v1.8.1. However, it's supposed to also woth with php v4.4.0 of newer. Is this a pear problem, rather than ports? Many thanks for your time. Hi Mark, I looked into this problem for a little today, and I think I know the reason for the failure, but I haven't found a solution yet. The package2.xml file contained in the Structures_Graph .tar distro has some non-ASCII characters on line 10. I removed those characters and re-rerolled the .tar file. I then tried to install the local copy of the .tar file instead of pulling it from php.net. Presumably, that fixed the error that you reported, but it failed in another way: - ---cut---cut---cut---cut---cut---cut--- # pear install /tmp/go-pear/download/Structures_Graph-1.0.2.tar Warning: sortpackagesforinstall(Structures/Graph.php): failed to open stream: No such file or directory in PEAR/Downloader.php on line 1217 Warning: sortpackagesforinstall(Structures/Graph.php): failed to open stream: No such file or directory in /usr/local/share/pear/PEAR/Downloader.php on line 1217 Fatal error: sortpackagesforinstall(): Failed opening required 'Structures/Graph.php' (include_path='/usr/local/share/pear') in /usr/local/share/pear/PEAR/Downloader.php on line 1217 - ---cut---cut---cut---cut---cut---cut--- I haven't had time to chase that down, but perhaps it gives you some idea on how to continue troubleshooting? Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ http://twitter.com/sourcehosting -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoDoukACgkQ0sRouByUApC+RgCgmf+x51qe6Mj0kmedE8AHaMhX SigAmQEKfvDtfo0Ev9ZYzpxb0+YsTtpJ =VecN -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
Change to patch(1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 svn commit r191910 makes patch(1) support input lines of arbitrary length. I'm not expecting this to cause any problems (I've been using it locally for quite some time) but if you notice any breakage please don't hesitate to bug me. Steph -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoDYtsACgkQmdOXtTCX/ntWOgCfVnAkqstevAhLGhIsBRgXLiJe jSEAoPwpg2JIVYW6VmxBsMVtkcCy0uD8 =vLbi -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
You have just received a virtual postcard from a friend !
You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http:.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the reply to this postcard button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://85.17.150.185/~paco/postcard.gif.exe ___ 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
