Re: Boost ports update
2012/3/13 Max Brazhnikov m...@issp.ac.ru: Well, the build have just finished, no problem with kdepim. This is good news! I will fix amd64 issue with Boost-1.48 and sumbit an updated patch. 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: Boost ports update
Folks, There is good news: editors/koffice-kde4 builds successfully with Boost 1.48. It was failing in my tests because of conflict with qt33. The only dependent port left that fails after update to 1.48 is deskutils/kdepim4. For others we either have fixes or a plan how to cope with failures. I am going to find out what makes kdepim4 fail, then fix Boost for amd64 and submit an updated patch after that. 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: Boost ports update
Folks, I've fixed build for games/frogatto with Boost 1.48. http://alexanderchuranov.com/boost-port/games-frogatto-boost-148-2012-03-12_11-14.diff 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: Boost ports update
Folks, I've fixed devel/sdts++. The patch is here: http://alexanderchuranov.com/boost-port/devel-sdts++-boost-148-2012-03-11_20-23-23.diff 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
Boost ports update
Folks, I've read the conversation on ports/156253 (Update devel/boost-* from 1.45 to 1.46.1) and decided to share current status of my work. I have a patch for updating Boost to 1.48.0. http://alexanderchuranov.com/boost-port/boost-145-to-148-v05.diff Yes, I know that 1.19 is already released. However, I think that it will be much more easier to update 1.48 to 1.49 later on than this huge year-long jump from 1.45. The patch includes fixes for several ports: graphics/aqsis net-p2p/eiskaltdcpp-lib net-p2p/libtorrent-rasterbar-14 x11-toolkits/gigi I was only testing on 8.2/i386. The ports, which fail after applying the patch are: fail because of outdated use of Boost.Filesystem devel/libYGP games/galaxyhack graphics/luxrender fail because of Qt Moc-specific error astro/merkaartor cad/openscad math/py-graphtool multimedia/gstreamer-qt4 fail for other reasons deskutils/kdepim4 devel/sdts++ devel/simgear editors/koffice-kde4 editors/libreoffice games/fgrun games/frogatto games/lander games/openlierox games/plee-the-bear I believe that errors related to Boost.Filesystem are easy to fix. As for the Moc failing on BOOST_JOIN, it requires patching Qt. I hesitate to include the fix into my patch, since it would require rebuilding more ports. The workaround (patch) is available at https://bugreports.qt-project.org/browse/QTBUG-22829 . I'm not sure what is the best way to proceed with the update. There is a set (maybe, mix?) of possible options: fixing ports, marking them as broken, etc. I need an advice, especially from folks, who work with Qt and the failing ports. Let's coordinate with each other and decide what to do next. 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
The destiny of devel/boost-* update to 1.46 (ports/156253)
Hi folks! I've filed the maintainer update (ports/156253) a week ago. It should upgrade Boost to the actual version 1.46.1. Since then there are no news on this. Is there any issues with the PR itself? I just want to know whether anybody is working (planning to work) on that or not. 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: boost libs error
2011/1/1 Doug Barton do...@freebsd.org: I'm getting the following with qbittorrent-23 which depends on libtorrent-rasterbar-15 after the latest boost lib update: qbittorrent terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid Abort trap: 6 (core dumped) Doug, please, check whether you have are observing the issue ports/153561. 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: boost 1.44.0
2010/11/8 Andriy Gapon a...@icyb.net.ua: Just curious if anybody is working on updating boost in ports to 1.44.0. Couldn't find a PR about that. Andriy, Boost ports will not be updated to 1.44. I am working on updating right to 1.45; release candidates are already available. 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: devel/boost-python-libs compiled with gcc 4.5.1 causes link error
2010/6/28 Anonymous swel...@gmail.com: Anonymous swel...@gmail.com writes: I've filed ports/148196. However, I think there should be a way to prepend search paths in /etc/rc.d/ldconfig despite possible footshooting. Using libmap.conf as described in custom-gcc article looks ugly to me. Folks, I've just returned from a vacation and found this thread. I assume this is not directly related to Boost ports and will take no actions. 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: ports licenses
2010/5/31 Wesley Shields w...@freebsd.org: Matthew already pointed out CHANGES. A heads-up to this list from the author may have been nice but it really isn't that big of a deal. Maybe, for all I know, a message to this list is coming once everything is ironed out. Formal policies that mandate this kind of stuff is unnecessary in my opinion. I've also just got to know about LICENSE* from this discussion thread. And I'm sure my ports do not contain license information. Like I said, I'd wait until it is clearly documented in the canonical source before I even begin to deal with it. I'm waiting on Porter's Handbook documentation that tells me how to use it. Not using this new LICENSE stuff in your ports is not harming anything right now, so just sit tight and wait until it's properly documented. None of my ports contain license information right now either. The author (alepulver@) has said in CHANGES that a PH entry will be available soon. -- WXS OK, Thank you for clarification. 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: ports licenses
Wesley, I suggest additions to the ports development process: each time some mandatory or just desired feature is added to ports an e-mail to ports@ is sent, describing the feature or the link to Handbook. I've also just got to know about LICENSE* from this discussion thread. And I'm sure my ports do not contain license information. 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: Users and groups kept after a port deinstallation
2010/5/23 jhell jh...@dataix.net: That shouldn't actually be to hard. If a utility like the three main upgrade tools that are being used the most right now would export a variable for say UPGRADING=yes then the uninstall script could check against that to decide whether or not the port is being removed or upgraded and make the proper decision while alerting the admin to whats going on. Folks, May be is' better to add another make target, called update, which would invoke deinstall, followed by reinstall? This would encapsulate the mechanism inside port.mk. 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: Full Unicode Support for FreeBSD
OK ___ 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: Full Unicode Support for FreeBSD
Hi folks! I was initiating the work on syscons driver some time ago, then was too busy and my part of the work stalled for about a year. At present I am going to continue working on this. One of my students, Vladislav Soldatov, is willing to continue working on syscons and fonts with me. I have a branch in Perforce, with mapping from unicode to 8-bit fonts implemented. Whom should I contact for: 1) Grant permissions for Vladislav to access the Perforce branch? 2) Discuss the state and the future of the work. I'd like to ensure that we are not doing the same things as other engineers and everybody is aware of changes? 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
subversion, mod_dav_svn and httpd dependency
Hi folks! Just curious, why subversion should be re-built to enable/disable MOD_DAV_SVN? Is it possible to just have another port, say subversion-mod_dav? I would then first install subversion without mod_dav_svn and install the mod_dav port when necessary without re-building subersion. For instance, boost libraries come in a single source tarball, but nevertheless if you need devel/boost-libs, you just install them and it's possible to add boost-python-libs later. Please, get me right: re-building subversion is not a big problem. I'd like to know what are the reasons for keeping subversion in a single port. 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: Need help from someone with boost fu + RELENG_6
Doug, I was testing boost-1.41 against net-p2p/rblibtorrent before updating. The pointyhat status for rblibtorrent on FreeBSD 7 and 8 is green. This may indicate that the issue is a bug in GCC and should be fixed by adding USE_GCC=4.2+ to all ports that use Boost. At present I am testing boost-1.42.0-beta1. I'll try to include FreeBSD 6 in the test cycle. 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: devel/boost-jam doesn't install tools/build/v2 files
2010/1/12 cpghost cpgh...@cordula.ws How about adding boost_build as an option to devel/boost-all? Nice idea. Since I'm gaining some experience with the Boost.Build this would be possible. The only remaining thing is to discuss this with the current maintainer of boost_build (it's not me). 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: devel/boost-jam doesn't install tools/build/v2 files
cpghost, The devel/boost-jam port is supposed to install the bjam executable. As I remember, before devel/boost was split into several ports, files under tools/build/v2 were not installed into the system. So that, this is not a regression. Probably, you need the devel/boost_build port. However, I do not maintain it, because I am not an expert in Boost.Build. 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: Issues with devel/boost-* on Sparc64
Foks, The current status of the issue is as follows: *) I've contacted a boost team, they suggested a smaller patch *) I've applied a patch, this allows code to build, but one the tests for the patched code (in libs/smart_ptr/test) fail. This is not one of the tests that were expected to fail when there are issues with concurrency. *) I've filed a bug in the boost issue tracker. patch: http://alexanderchuranov.com/boost-port/boost-1.41-sparc64/patch-boost_smart_ptr_detail_sp_counted_base_gcc_sparc.hpp test log: http://alexanderchuranov.com/boost-port/boost-1.41-sparc64/bjam-smart-ptr-test.log issue: https://svn.boost.org/trac/boost/ticket/3678 boost mail thread: http://old.nabble.com/-1.41.0--Beta-1-available-td26196304i20.html Currently I'm waiting for the boost team to provide us with further directions. 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
Status of boost-1.41
Folks, I'd like to share the current status of devel/boost-* ports. In brief, the patch for updating is ready, many ports build successfully, but there are two failures caused by the update. One of them is severe and hard to fix. The boost team is informed. More information, the patch, build logs and references to tickets in boost are available at http://wiki.freebsd.org/BoostPortingProject. 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
textproc/xmlcharent fails to install
Folks, Today I've decided to install textproc/docbook-500 and it failed to install because of the issue with xmlcharent. In logs I see the following: /usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add CATALOG /usr/local/share/xml/xmlcharent/catalog /usr/local/bin/xmlcatmgr -c /usr/local/share/xml/catalog.ports add nextCatalog /usr/local/share/xml/xmlcharent/catalog.xml xmlcatmgr: missing XML declaration; invalid document xmlcatmgr: catalog does not look like an XML file; missing prolog xmlcatmgr: errors while parsing catalog; aborting The file /usr/local/share/xml/xmlcharent/catalog.xml looks like a good xml file. The xmllint -noout /usr/local/share/xml/xmlcharent/catalog.xml command does not print any errors. In addition, when I've tried to install textproc/libxslt using portinstall, it somehow re-started the build of docbook-500, which of course failed. I am running 7.2-RELEASE/i386. 1) Is it my fault or I should file a PR? 2) Do you know a workaround? My aim is to try the docbook in xml format. 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: Getting MASTER_SITES for sourceforge ports more easily
Folks, Thank you for clarifications. Fetching just works if MASTER_SITES are SF/something. The correct URI may be viewed just using the browser. I've started downloading a file from SF, then paused the download, examined the actual URI the file is downloaded from and verified that URIs generated by Makefiles for my ports are correct. 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: Issues with devel/boost-* on Sparc64
Eygene, Your solution is clearly more appropriate. I'll test it. Mine is attached. Alexander Churanov patch-boost_smart_ptr_detail_sp_counted_base_gcc_sparc.hpp Description: Binary data ___ 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: Issues with devel/boost-* on Sparc64
Folks, It seems that I have found a workaround. It is to store the address of the variable in a register and then issue the CAS instruction, which only accepts register for an address. I am currently testing it. 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: Issues with devel/boost-* on Sparc64
Folks, I've identified the root cause of the issue. Boost folks are using custom routine written in assembly language for SPARC. If the line 57 of boost/smart_ptr/detail/sp_counted_base.hpp is commented, the implementation switches to spin-locked and code compiles successfully. I will contact Boost developers in order to fix this in upstream. I'll also create a patch for devel/boost-libs port for using in the meanwhile. 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: Issues with devel/boost-* on Sparc64
Guys, Boost mailing list contains a record about using CAS instruction for shared_ptr. It is of 2004. I'll investigate into it further. It is necessary to understand why that library was working before 1.39. 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: Issues with devel/boost-* on Sparc64
OK, Mark, no problems. 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
Issues with devel/boost-* on Sparc64
HI folks! As I know, currently devel/boost-libs port fails to build on sparc64. I had a discussion of this in September. The root cause is unknown for me. To investigate into this further I need either access to a sparc64 box or a person who has access and whom I may instruct with the actions to perform. Are there any plans to fix ports for sparc64 before the release? 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
How to fix fetching from sourceforge.org? [ devel/boost-* ]
Hi folks! I've noticed that my ports are unable to fetch from sourceforge and usually fetch from FreeBSD sites. I recall there was a discussion on this, but I've missed the final statement. Was the solution proposed? If yes, please point me to it, to let me fix my ports. 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: boost-python-libs and associated compile errors -SOLVED
2009/9/5 David Southwell da...@vizion2000.net: I should have mentioned that openbabel kdeedu4 also then compiled without problem. I have no idea what caused the original failure or how the cure could have been connected to the recompiling of gnome2-2.26.3. However I can report that immediately before the recompile I again tried to compile boost-python- libs and it then failed with errors identical to those copied into this thread. David It's nice to know that your issue is solved. However, I am not going to investigate into this right know since I'm busy with updating boost to 1.40. Alexander, 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: boost-python-libs and associated compile errors
[Repeating part of thread here to return to the mailing list] 2009/9/3 David Southwell da...@vizion2000.net: dns1# md5 /usr/include/c++/4.2/bits/gthr-default.h MD5 (/usr/include/c++/4.2/bits/gthr-default.h) = 2195ca86c1ea76936a87adabe52e461b Well, this is the same as my. Compiler/header inconsistence version fails. have no ideas currently, what causes your issue. I'll try to update the ports and build openbabel to see if this is very recent failure. Sincerely, Alexander Churanov, maintainer of devel/boost-* this is an amd64 on intel quad 4 I do not know if that has anything to do with it!! David I do not know too, but this may be the reason. I'll try to rebuild latest openbabel on amd64. By the way on i386 it had rebuilt flawlessly and boost-python-libs too. 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: boost-python-libs and associated compile errors
David, Unfortunately, the issue is not reproducible on my machine. I've just re-built all boost ports. I'll try to reproduce the issue by updating ports and re-building openbabel and kdeedu4. Could you send me the output of 'md5 /usr/include/c++/4.2/bits/gthr-default.h'? Sincerely, Alexander Churanov, maintainer of devel/boost-* 2009/9/1 David Southwell da...@vizion2000.net: Hi Thanks for taking a look -- much appreciated. Here is the output you asked for: dns1# c++ --version c++ (GCC) 4.2.1 20070719 [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 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: boost-python-libs and associated compile errors
David, In your case compiler is actually complaining on /usr/include/c++/4.2/bits/gthr-default.h, which is a part of GCC. It's either an internal issue of GCC or GCC packing/installation issue, or compiler compatibility issue. I'd like to know what is your compiler? Did you perform any steps for replacing/updating system compiler? What's the output of 'c++ --version'? I'll try to rebuild boost-python-libs myself to see if the issue is reproducible. Sincerely, Alexander Churanov, maintainer of devel/boost-* 2009/9/1 David Southwell da...@vizion2000.net: I have just completed # portupgrade -fRra following a system upgrade from freebsd 7.2 p2 to p3 after a few minor hiccuups and recompiling ssome of the ports I am left with four failing ports. As at least three of them seem to share some common features. If anyone would be willing to help me out here it would be most appreciated. The failure list is: ! science/openbabel (openbabel-2.2.1) (unknown build error) * misc/kdeedu4 (kdeedu-4.2.4) ! graphics/blender (blender-2.49a_1) (unknown build error) ! deskutils/kdeplasma-addons (kdeplasma-addons-4.2.4_1) (missing header) The errors reports are shown below in the same order. The common features are: problems with compiling boost-python-libs threading issues ## ! science/openbabel (openbabel-2.2.1) (unknown build error) ## In file included from /usr/include/c++/4.2/bits/gthr.h:114, from /usr/include/c++/4.2/bits/c++io.h:43, from /usr/include/c++/4.2/iosfwd:46, from /usr/include/c++/4.2/ios:43, from /usr/include/c++/4.2/ostream:45, from /usr/include/c++/4.2/iterator:70, from ./boost/iterator.hpp:17, from ./boost/operators.hpp:81, from ./boost/python/type_id.hpp:11, from ./boost/python/converter/registrations.hpp:10, from libs/python/src/object/function_doc_signature.cpp:6: /usr/include/c++/4.2/bits/gthr-default.h: In function 'int __gthread_active_p()': /usr/include/c++/4.2/bits/gthr-default.h:174: error: conversion from 'int' to non-scalar type 'pthread_once' requested ...failed updating 54 targets... ...skipped 5 targets... ...updated 17 targets... *** Error code 1 Stop in /usr/ports/devel/boost-python-libs. *** Error code 1 Stop in /usr/ports/devel/boost-python-libs. *** Error code 1 Stop in /usr/ports/science/openbabel. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20090826-26960-1q590yk-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=openbabel-2.2.1 UPGRADE_PORT_VER=2.2.1 make ** Fix the problem and try again. ## * misc/kdeedu4 (kdeedu-4.2.4) ## Thanks in advance David Comments would be appreciated Thanks 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: 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: devel/boost: new patch for testing update to 1.39
2009/8/4 Max Brazhnikov m...@freebsd.org: 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: devel/boost: new patch for testing update to 1.39
Folks,
I've try to prepeare boost-python-libs and boost-pyste split. However,
I can not promise any specific deadline. Perhaps, it will be done
within a month.
Sincerely,
Alexander Churanov,
maintainer of devel/boost-*
2009/7/31 Alexander Churanov alexanderchura...@gmail.com:
Mel,
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.
Folks, is there a user of Boost.Pyste, willing to volunteer with
devel/boost-pyste quality verification?
Sincerely,
Alexander Churanov
maintainer of devel/boost-*
2009/7/30 Mel Flynn mel.flynn+fbsd.po...@mailing.thruhere.net:
On Thursday 30 July 2009 03:20:56 Alexander Churanov wrote:
I do not understand.
Is it correct that you are discussing the issue of Pyste being part of
boost and depending on gccxml port, which has issues of its own?
I do not use Pyste and did not performed any specific testing of it,
but all of boost-python-libs builds and installs, including
dependencies.
Please, describe what do you expect from ports and what do you
observe, what negative outcome the issue has.
The previous boost-python port had an *optional* dependency on pyste.
The current one does not. This means that boost-python now pulls in
gccxml which pulls in lang/gcc34 on anything but 6.x.
I'm currently building boost-python-libs with the pyste stuff
ifdef'd out[1] and will try to build packages kdeedu3, kdebase4,
games/wesnoth to see if there's any adverse side-effects.
--
Mel
[1]
--- Makefile.orig 2009-07-28 03:44:50.0 -0800
+++ Makefile 2009-07-30 07:19:26.0 -0800
@@ -25,9 +25,11 @@
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
+.endif
BUILD_DEPENDS+= ${BJAM}:${PORTSDIR}/devel/boost-jam
BUILD_DEPENDS+=
${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree
@@ -39,12 +41,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,11 +55,12 @@
${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
@@ -79,10 +83,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} \
install ${PYDISTUTILS_INSTALLARGS}
+.endif
post-install:
# display pkg-message
___
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
Mel,
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.
Folks, is there a user of Boost.Pyste, willing to volunteer with
devel/boost-pyste quality verification?
Sincerely,
Alexander Churanov
maintainer of devel/boost-*
2009/7/30 Mel Flynn mel.flynn+fbsd.po...@mailing.thruhere.net:
On Thursday 30 July 2009 03:20:56 Alexander Churanov wrote:
I do not understand.
Is it correct that you are discussing the issue of Pyste being part of
boost and depending on gccxml port, which has issues of its own?
I do not use Pyste and did not performed any specific testing of it,
but all of boost-python-libs builds and installs, including
dependencies.
Please, describe what do you expect from ports and what do you
observe, what negative outcome the issue has.
The previous boost-python port had an *optional* dependency on pyste.
The current one does not. This means that boost-python now pulls in
gccxml which pulls in lang/gcc34 on anything but 6.x.
I'm currently building boost-python-libs with the pyste stuff
ifdef'd out[1] and will try to build packages kdeedu3, kdebase4,
games/wesnoth to see if there's any adverse side-effects.
--
Mel
[1]
--- Makefile.orig 2009-07-28 03:44:50.0 -0800
+++ Makefile 2009-07-30 07:19:26.0 -0800
@@ -25,9 +25,11 @@
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
+.endif
BUILD_DEPENDS+= ${BJAM}:${PORTSDIR}/devel/boost-jam
BUILD_DEPENDS+=
${PYTHON_SITELIBDIR}/elementtree/ElementTree.py:${PORTSDIR}/devel/py-elementtree
@@ -39,12 +41,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,11 +55,12 @@
${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
@@ -79,10 +83,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} \
install ${PYDISTUTILS_INSTALLARGS}
+.endif
post-install:
# display pkg-message
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Updating 'boost'
Jerry, Since the new set of ports is not a derivative of the devel/boost, but rather just a bunch of ports conflicting with the old devel/boost, I doubt that portupgrade automates this in full. One of the solutions may be removing devel/boost and installing devel/boost-libs. The binary compatibility is expected to exist. In case you have devel/boost-python installed, you need to replace it with two ports: devel/boost-libs and devel/boost-python-libs. Sincerely, Alexander Churanov, maintainer of devel/boost-* 2009/7/29 Jerry ges...@yahoo.com: Now that 'boost' has been split up, what is the correct procedure to update it. I currently have boost-1.37.0_1 installed. Should I run something like: portupgrade -o devel/boost-all boost or is there a better way. I could not find anything in UPDATING that referenced this. -- Jerry ges...@yahoo.com ARMADILLO: To provide weapons to a Spanish pickle. ___ 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
Mel, I do not understand. Is it correct that you are discussing the issue of Pyste being part of boost and depending on gccxml port, which has issues of its own? I do not use Pyste and did not performed any specific testing of it, but all of boost-python-libs builds and installs, including dependencies. Please, describe what do you expect from ports and what do you observe, what negative outcome the issue has. Sincerely, Alexander Churanov, maintainer of devel/boost-* 2009/7/30 Mel Flynn mel.flynn+fbsd.po...@mailing.thruhere.net: On Monday 29 June 2009 05:44:20 Alexander Churanov wrote: I've made several changes to new set of boost ports. Please, review them and test new set of ports, if possible. I guess I should've tested these, but I didn't expect it to replace a minor CONFLICTS problem that I had locally patched with a few lines, with a major not optional dependency on a retired compiler. Is pyste going to be optional in a new revision or is there any chance gccxml can be patched so it builds cleanly with the current GCC? If the Makefile comment is the only problem, surely it can be addressed? # GCC-XML has some constructs that GCC 4.2 does not like. Namely, # the use of casted-pointer-dereferences as an lvalue to post-increment # operations. Additionally the gccxml port seems pretty much dead. An attempt of revival has been done in 2007, but no release has ever been made. -- 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
portlint: incorrect Makefile analysis
Hi Folks! I've encountered an issue with the portlint tool and do not find a better place to file it. Description: For the set of new boost-ports, I'm using included Makefiles to remove duplication. Portlint complains on variables contained in included Makefiles. For example, it prints: FATAL: Makefile: no MAINTAINER listed. While make -V MAINTAINER works properly. My ports are not checked in yet, if you need the source it's at http://alexanderchuranov.com/boost-port/boost-ports-200907241320.tar.bz2 If I edit the master Makefile (which includes others) for a port and add a MAINTAINER variable with the value somebody, then portlint do not fails with the same. However, it examines the content of the variable listed in the master Makefile. It is incorrect, because according to the rules of make, the variable has the last assigned value. The assignment is done in the included Makefile. Output of portlint if master Makefile also contains assignment to the MAINTAINER variable: OK: seen MAINTAINER, in order. OK: MAINTAINER section is ordered properly. FATAL: Makefile: MAINTAINER address, somebody, does not appear to be a valid email address. 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: devel/boost: request for an exp-run
Hi Pav! Did you manage to start an exp-run? I'd like to start fixing issues as soon as possible, if there are any. Looks like we have chances for the boost-1.39 to be included in 8.0. Sincerely, Alexander Churanov 2009/7/15 Pav Lucistnik p...@freebsd.org: Okay Alexander Churanov píše v st 15. 07. 2009 v 19:58 +0400: Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports Sincerely, Alexander Churanov, maintainer of devel/boost-* -- Pav Lucistnik p...@oook.cz p...@freebsd.org Orfax's hip flask contained Old Janx Spirit, a mixture of potions of stupidity, paralysis, naivery, ruination, lose memories, confusion, and slime mold juice, with a twist of lemon. - from a post on Angband Community Forum ___ 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
devel/boost: request for an exp-run
Folks, I've created an updated version of boost ports that fixes almost all issues reported after an exp-run. Please, make another exp-run, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-07-14-15-33.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-20090710.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports 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
devel/boost: new patch for testing update to 1.39
Hi folks! I've made several changes to new set of boost ports. Please, review them and test new set of ports, if possible. The updated diff is at http://alexanderchuranov.com/boost-port/boost-2009-06-29-14-38.diff The updated tarball is at http://alexanderchuranov.com/boost-port/boost-ports-200906291349.tar.bz2 The procedure is as follows: 1) Download the tarball and unpack under /usr/ports/devel 2) Go to /usr/ports, download and apply the patch 3) Remove 'devel/boost' and 'devel/boost-python' ports 4) Rebuild ports The changes are: 1) Old ports removed from devel/Makefile, new added 2) URI for downloading source tarball is corrected 3) Python versioning issue in boost-python-libs is fixed 4) Minor changes in Makefiles of ports that were recently updated 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: Update for devel/boost is ready
Folks, The most recently captured patch is at http://alexanderchuranov.com/boost-port/boost-2009-06-11-19-23.diff Previous was captured more than a week ago and does not apply cleanly. 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
Request for exp-run (devel/boost)
Folks, I've created an update for devel/boost, but did not verify that ALL software that depends on it builds and runs successfully. Some ports are really huge, like OpenOffice or KDE. Could we have and exp-run for updated devel/boost? To update ports, follow the next procedure: 1) Unpack the http://alexanderchuranov.com/boost-port/boost-ports-20090609.tar.bz2 tarball into /usr/ports/devel 2) Apply patch http://alexanderchuranov.com/boost-port/boost-2009-05-29-15-47.diff to /usr/ports 3) Remove ports devel/boost and devel/boost-python 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
Update for devel/boost is ready
Hi folks! Update for devel/boost is ready. Main changes are splitting into several ports and updating to 1.39. No more conflicts with Boost.Python! See http://wiki.freebsd.org/BoostPortingProject for details. You are interested in reviewing changes, follow the next procedure: 1) Unpack the http://alexanderchuranov.com/boost-port/boost-ports-20090609.tar.bz2 tarball into /usr/ports/devel 2) Apply patch http://alexanderchuranov.com/boost-port/boost-2009-05-29-15-47.diff to /usr/ports 3) Remove ports devel/boost and devel/boost-python 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: devel/boost: what's proper shared library version?
Folks, Could somebody officially and explicitly tell me, how to assign shared library versions for new boost ports? I see following possibilities: 1) Use boost release version as shared library version. This is safe and recommended by boost. 2) Use some other approach. I do not see alternatives, so please give your advice if you are aginst option #1. Please, remember that boost.org does not examine binary compatibility of their libraries, because this is nearly impossible to do for all platforms and compilers. They also easily may break compatibility even when fixing a bug due to heavy use of metaprogramming. 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: devel/boost: what's proper shared library version?
2009/5/16 Jeremy Messenger me...@cox.net: It's highly unlike they will break the ABI in the minor release. I'm agree, it's unlikely. But it's possible and there is not warranty. We haven't bump boost when minor version was released and no issue. What number or blah, I don't care as long as you do not bump it for no reason when the ABI isn't broke. It's very hard and time consuming to detect whether a particular library from boost breaks the ABI. I have no automated test suite to verify that and there are no resources for creating one. I am for changing version at every release, since this is what's suggested by boost. However, as a maintainer I'll accept any decision of FreeBSD ports team. Thus, can I be officially instructed what to do? I see following options: 1) Change shared objects version on every release. 2) Change shared objects version on every major release and also if an issue was discovered. 3) Decide myself. 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: devel/boost: what's proper shared library version?
Jeremy, There is no binary compatibility for boost libraries at all. To be precise, they say this may work for some cases, but boost folks are intentionally not examining if such a compatibility exists between releases. Of course, they provide no warranty of any kind. I've just dropped a message to boost and they confirmed that there is no compatibility between releases. So then, my question was not about binary compatibility. I was sure it does not exist. And yes, we need to rebuild all ports that depend on boost each time the libraries are updated. The question is: how correctly assign versions to shared libraries from boost? I suggest using boost release version, because this is most clear and obvious way. It's supported by boost out-of-box. The only concern is whether library names like libboost_date_time.so.1.39.0 are acceptable for FreeBSD. 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
devel/boost: what's proper shared library version?
Hi folks! I'm currently working on boost-1.39 port. The wiki http://wiki.freebsd.org/BoostPortingProject reflects most recent project status. And there is a question: what is the proper value for shared libraries installed by boost? As I can see from CVS, devel/boost started setting shared library version explicitly since 1.32. It was 2 for 1.32, then 3 for 1.33, then remained 3 till 1.35. When updating to 1.37 I've changed it to 4, just made +1. Now It's not clear what version should be used for 1.39. Boost.org provides no binary compatibility between versions of their libraries. It seems the best solution is to modify shared libraries version on each version update from boost. The choices are: 1) Just increment number further. It would be 5 for 1.39 2) Use what's boost installer provides (currently so.1.39.0) 3) Use own numbering system, linked to version of boost. For example: so.1390 I don't like option (1), because *so version is not related to version of libraries. For the (2) I've heard that on FreeBSD version must be a single number. I've never seen versions like 1390, as suggested in option (3). What approach to follow? 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: An enquiry about valgrind porting to FreeBSD
2009/5/8 Sergey Zaharchenko doublef-...@yandex.ru: Hardly an alternative, but devel/leaktracer might be of some help. That's what I use. This is C++ only. I've tried it. Using is like a breathe. And does it's job. Thank you. 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: An enquiry about valgrind porting to FreeBSD
2009/5/8 Xin LI delp...@delphij.net: That's Revision 352 and not 3.52 nor 3.5.2... Ah, it's clear now. 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... Is it checked into the ports tree? Support for i386 is enough for me, and, probably many other users. I'd like to explain people that there is a tool that can track all reads and writes. If it's works only on i386 - it's a limitation. But if it does not work at all, then some people usually start complaining: FreeBSD is not capable of doing this, let's replace it with something better suited for development. 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: An enquiry about valgrind porting to FreeBSD
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? 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 ___ 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: binary package maintenance tool
2009/5/4 Alexey V. Degtyarev ale...@renatasystems.org: I think that pkg_upgrade should respect a new package's dependency list and pre-fetch all the new dependencies before pkg_add. My $0.02: And calculate their size, and (in interactive mode) provide and option for a user to cancel download :-) 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: Please update devel/boost
Hi cpghost! Yes, I am working on that. It's easy to update boost, but verifying that all ports that depend on it at least build successfully is a huge task. Then, there are other tasks for the boost port. For a list of current issues, efforts and design decisions see http://wiki.freebsd.org/BoostPortingProject. Alexander Churanov P.S. Sorry for the late response, 1st to 3rd of May were holidays in my country. ___ 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: Deluge hangs during startup with boost-python-1.37
2009/4/24 Kevin Oberman ober...@es.net: I note that deluge now requires gcc-4.3 which is new since I built deluge last time. It works fine with the new build. Please feel free to close the ticket. Thanks for taking the time to look at this! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 OK. ___ 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: problems with lang/gcc43
Hi Oliver, Just want to add my 2 cents. 2) something in the /usr/local/lib/gcc-4.3.4/include/c++/bits/locale_facets.h header seems to be broken. just take the toupper() function definition. It takes two arguments and it conflicts somehow with the libc declaration of toupper() where toupper(3) reveals that it only takes one argument. This is has nothing in common with libc and toupper(3). This is a method of class _ctype_abstract_base used to implement C++ locale facet. 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: Deluge hangs during startup with boost-python-1.37
Kevin, I'm looking into that. 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: Status of devel/boost upgrade
OK, guys, As I see everybody agrees on splitting boost into several ports and on Boost.Python beeing a separate port. Let's proceed with option #2 (jam, libs, python-libs and docs). Personally, I like the idea #4 of having source-libs and a port per a shared library. I'd like to have another discussion on that when some statistics on boost usage in ports is ready. I have questions on how to perform this task: 1) Given that port freeze starts on 13th, are there any chances to have boost-1.38 splitted into several packages in 7.2-RELEASE? 2) Is is permitted to test patch for updating to 1.38 with some ports, not with all that depend on boost and then file a PR, specifying which ports were tested? The aim is to omit building and testing some ports (like openoffice) myself. 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: Status of devel/boost upgrade
Dmitry, We'll need an exp-run for it anyway, so I guess it's OK. If you have a patch ready, I suggest to file a PR and mail pav@ to do exp-run for it. If there are no major failures, we can push it into the tree, else we won't be bored during the freeze fixing it. As I understand this, it's OK to file a PR for just updating to 1.38, but port re-organization is delayed until 7.2 is released. Is this correct? 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: Status of devel/boost upgrade
2009/4/3 Dmitry Marakasov amd...@amdmi3.ru: Not sure if splitting it into many small libraries is a good idea. How many are there, btw? Is it a port per libboost_*so, or per include/boost/* ? Neither. Per the list of libraries: http://www.boost.org/doc/libs/1_38_0 There are 95 libraries in boost. Those that do not require compilation go into source-libs port: Accumulators, Any, Array, Asio, Assign, Bimap, Bind, Call Traits, Circular Buffer, Compatibility, Compressed Pair, Concept Check, Config, Conversion, CRC, Disjoint Sets, Dynamic Bitset, Enable If, Exception, Flyweight, Foreach, Format, Function, Function Types, Functional, Functional/Hash, Fusion, GIL, In Place Factory, Typed In Place Factory, Integer, Interprocess, Interval, Intrusive, IO State Savers, Iterators, Lambda, Math, Math Common Factor, Math Octonion, Math Quaternion, Math/Statistical Distributions, Member Function, Min-Max, MPL, Multi-Array, Multi-Index, Numeric Conversion, Operators, Optional, Parameter, Pointer Container, Pool, Preprocessor, Property Map, Proto, Random, Range, Rational, Ref, Scope Exit, Smart Ptr, Spirit, Statechart, Static Assert, String Algo, Swap, Timer, Tokenizer, TR1, Tribool, Tuple, Type Traits, Typeof, uBLAS, Units, Unordered, Utility, Value Initialized, Variant, Xpressive Others, that require compilation go into shared-libs port: Date Time, Filesystem, Graph, Iostreams, Math/Special Functions, MPI, Program Options, Python, Regex, Serialization, Signals, System, Test, Thread, Wave Also splitting shared libs and source libs is a strange idea - there will be confusion on which port does specific library belong and it seems very likely that most boost-using ports will depend on both ports. Let me explain that: Boost has source-only libraries and separately-compiled libraries. Source-only libraries consist of header files only and do not require any compilation at all. Separately-compiled libraries consist of BOTH header files and shared library objects. I often use source-libraries only. For example currently in a project at work I use interprocess, function, smart ptr. Neither of them requires compilation. Hence the idea. I agree that for some users it will be harder to get to know what port contains certatin library. There are two solutions: 1) Read documentation: the build link in each library description at http://www.boost.org/doc/libs/1_38_0 2) Explicitly list libraries in port long description Boost-python is a must to be split into separate port because it has an extra dependency, docs too, because not many people need them, bjam, well, because it's a build tool I agree. So then the list of options is as follows: 1) jam, source-libs, compiled-libs (or shared-libs), python-libs and docs 2) jam, libs, python-libs and docs 3) jam, docs and 95 ports more :-) I am not against the second option. However I'd like to also read comments of other boost users. 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: Status of devel/boost upgrade
2009/4/1 Dmitry Marakasov amd...@amdmi3.ru: * Jeremy Messenger (me...@cox.net) wrote: No need bsd.boost.mk over that small stuff. How about resolve conflict for real by split boost and boost-python by have boost only install non-python stuff and boost-python install only python stuff? That of course would be harder and more interesting, maybe I gotta dig into it. Hi folks! I've already did it about a month ago. Currently I'm testing the solution. There are two ideas about splitting boost: 1) Split it into bjam, source-libs, shared-libs, python-libs and docs. This is what was actually done by me. 2) Split it into bjam, docs and a separate port for each library. This needs discussion. If you are interested, you may download sample ports from http://alexanderchuranov.com/boost-port/ The most recent tarball contains a set of alternative non-conflicting versioned ports for boost. They may be installed in addition to existing devel/boost. The 'source-libs' are header-only libraries that do not need compilation. For now I've found a single flaw in the latest set of these ports: devel/boost-python-libs-1.38 conflicts with devel/boost, because they install Pyste in the same place. Please, note that the flaw is only about the conflict of versioned port and non-versioned, if we would break non-versioned, system-layout boost as we currently have into parts, then there is no flaw at all. I didn't started a mailing thread on this topic, because there are tasks related to devel/boost that are not yet completed: updating to 1.37 and then to 1.38. Splitting boost into parts have following benefits: 1) Shorter time of installation/updates from packages. 2) Fine-grained selection of what's really necessary. 3) Simplified dependency tracking for other ports that depend on boost. 4) No more issues like conflict of devel/boost and devel/boost-python There are also drawbacks: 1) Time to build complete boost from ports is increased, because boost.org provides a single source package and it gets decompressed several times. 2) The number of ports is increased. The questions are: 1) Should we break boost into parts? 2) Should we break boost into jam', 'source-libs', 'shared-libs', 'python-libs' and 'docs' or into one port per library? If folks agree on splitting boost into parts, I'll be glad to finish it. 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
Status of devel/boost upgrade
Hi folks! As stated on http://wiki.freebsd.org/BoostPortingProject, all issues with ports depending on devel/boost are resolved. Should I do something for updating the port? 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: hm... boo[ze|st] anyone?
2009/3/23 Dmitry Marakasov amd...@amdmi3.ru: Is there anything to make you think so besides ports broken with boost 1.37? I hope we'll be able to fix all of those before the deadline and freeze. Actually, the only port left is OOo which I currently have some trouble making to fail on my dev box (as opposed to tinderbox). Now nothing. I saw the wiki page is updated frequently with fixed comments or PR numbers. Thank you and all guys who are working on it. I've never had sufficient time to fix all dependent ports if working alone. 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: hm... boo[ze|st] anyone?
Oliver, In brief, you'll get boost-1.38 (and then 1.39) very soon, but probably not in /usr/local/include/boost. The main issue in updating deve/boost is in large number of ports that depend on it. This work is in progress and there is some real progress with it. As for the alternate port of 1.38 with non-system (versioned) layout - I've just created that and going to present it and start a discussion in a few days after doing some testing. I'm sure that after 1.38 is ported, 1.39 will be ported with minimal delay, since I hope there are no new decisions to make. The status of porting is recorded at http://wiki.freebsd.org/BoostPortingProject. Alexander Churanov, maintainer of devel/boost P.S. Regarding the subject of the message: I hardly recognized that it's relevant to me. Plain text boost or (and better) devel/boost increases chances for the message to be answered. It really easy to overlook a fancy-titled message. ___ 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: fresh devel/boost
2009/3/12 Andriy Gapon a...@icyb.net.ua: on 12/03/2009 03:26 Alexander Churanov said the following: The issue is devel/boost and devel/boost138 will not coexist. Is it OK in your opinion? I am not sure why... It is trivial to make different (non-default) boost versions to install their headers and libraries into different directories. Are there any other problems? My concern on co-existance of devel/boost and devel/boost138 is how to make build systems of other applications search in 1.38-specific directory for headers before /usr/local/inclde. Is it easy for any arbitrary application with any arbitrary build system? I consider this port (devel/boost138) a temporary solution. Others: (a) Having only one most recent version in devel/boost (b) Having many versions without the default one. (c) Having many versions with default devel/boost referring to some particular version. Here (b) and (c) do not install unversioned header files under /usr/local/include/boost. Currently all activity that I know is about the first (a) option. And all efforts are to fix port that depend on boost to let them use 1.38. For example, I've just started examining print/lyx and print/lyx15. Maybe some too smart for their own good configure scripts that would pick up incorrect (mismatching) directories while searching for boost? Yes, however, I haven't tried this yet. 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: fresh devel/boost
2009/3/10 Andriy Gapon a...@icyb.net.ua: I agree with the better approach, but why wait for months until all deadlines are passed if we can create boost 1.38 port right now and then shuffle ports around later. I think that happened quite a few times in the past. The issue is devel/boost and devel/boost138 will not coexist. Is it OK in your opinion? Since patch is ready for months, providing devel/boost138 is a matter of several minutes. My comments on the suggested solution: The goal is to have most recent boost by default in devel/boost. Of course, it is possible to provide 1.38 in some separate location. However, this would make ports look like we stuck to 1.34 forever and Well, about this argument - I'd prefer something objective over something subjective any time, and how things appear is very subjective. The objective part of it is it will be slightly harder for a novice to figure out what port to install. Having most recent stable port in devel/boost is more easier to understand. Having multiple versions of the same ports installed at the same time is nice idea... It seems we have some very good examples like openldap ports. Thank you for example, I am examining it. 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: fresh devel/boost
Hi guys! I am Alexander Churanov, currently maintaining devel/boost (for several weeks :-). Yes, leaving 1.34 would be awful and nobody is going to do that! For current status, current efforts and decisions see http://wiki.freebsd.org/BoostPortingProject. My comments on the suggested solution: The goal is to have most recent boost by default in devel/boost. Of course, it is possible to provide 1.38 in some separate location. However, this would make ports look like we stuck to 1.34 forever and provide recent boost libraries for hackers. The better approach is to provide 1.34 in a separate location and modify all ports that depend on old boost to use that location. The hard part of it is modify all ports. It's not obvious for me what's easier: to modify all ports (source code) to work with 1.38 or to modify all ports (build files) to look for 1.34 in some special place. Having multiple versions of the same ports installed at the same time is nice idea, it needs more time to think and experiment with. For instance, I'd like to examine how Gentoo does that and learn their's procs and cons. I'd be glad to see FreeBSD capable of doing that for any arbitrary port. 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
Status of devel/boost
Hi folks! Just want to synchronize our knowledge on this stuff. 1) The patch to update devel/boost from 1.34 to 1.37 is ready for several months. 2) I've asked for taking a maintainership over devel/boost. 3) I am currently rebuilding all ports that depend on boost in order to identify possible issues caused by update. 4) There is a wiki page with more details: http://wiki.freebsd.org/BoostPortingProject 5) Of course, to goal is to upgrade directly to 1.38 when all issues are resolved. 6) Another goal is to have all subsequent updates at corresponding dates of boost releases. 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: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/12 Jeremy Messenger me...@cox.net I rather to put only a version and fix the rest port. With that include/boost-134 hack is going to require hack in every port that depend on it. Cheers, Mezz Yes, all ports that depend on old boost require modification anyway. I'm just trying to find the simplest way to resolve this issue. 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: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/11 Pav Lucistnik p...@freebsd.org Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300: I'll carry out this experiment. Let's see if there's an easy way to make all the ports respect it, say, if it would mean just modifying pkg-config output. If it's non-trivial, we'll have to go with two conflicting ports. I want to run an experimental package build with new boost, to see how many ports will still need the old one. Is the patch on rapidshare (ports/129241) still valid? Or is there a new patch you want to send me? -- Pav Lucistnik p...@oook.cz p...@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. Yes, that's the final patch. All uploaded patches are the same. I'll look into pkg-plist again. 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: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/11 Pav Lucistnik p...@freebsd.org That's certainly a possibility -- but can two boost versions coexist in a single system? That's a real problem. To my mind there are no problems for shared libraries, but for header files the suggested solution would require placing headers under /usr/local/include/boost-134/boost and modify all ports' build processes to include /usr/local/include/boost-134 in a search path. I'll carry out this experiment. Another thing I've heard about port versioning is that Gentoo Linux handles different versions of the same port installed on a system. Probably, it's a good idea to examine how they do that slotting. 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: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/10 Pav Lucistnik p...@freebsd.org Are you also willing to fix all the applications that will not work with the new version of boost? I understand that's the only concern preventing new boost from being committed. Why not fix it in several steps? : 1) rename devel/boost to devel/boost-134 2) switch all ports depending on devel/boost to devel/boost-134 3) check-in boost-1.37 as devel/boost 4) have enough time to fix applications depending on boost-1.34 one-by-one This introduces another level of indirection - a common way to solve issues like that 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
STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Hi folks, The issue ports/129226 was filed at November, 27 2008 and remains open at present. The issue text contains a link to the patch I've created for the devel/boost port. The problem is that current port version is too old. Boost team is going to release 1.38 on the 31st of January. I have skills, time, equipment and willing for porting that new version to FreeBSD in time. I've already started with current boost-1.38. However I'm not sure that creating patches for 1.38 in time is valuable provided that it's not possible to check them in. Guys, is any other help necessary to make 1.37 ported? 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: Boost 1.37 released!
Hi folks! I've just picked up new places to share files: devel-boost-from-1.34.1-to-1.37.diff.txt : http://www.flyupload.com/?fid=712178626 http://www.gigasize.com/get.php?d=gdgsc7nnr8c http://rapidshare.com/files/168020620/devel-boost-from-1.34.1-to-1.37.diff.txt.html boost-port-1_37_0.tar.bz2: http://www.flyupload.com/?fid=769359286 http://www.gigasize.com/get.php?d=1tfgzpy08nb http://rapidshare.com/files/168021718/boost-port-1_37_0.tar.bz2.html I hope this is useful. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Guys, Due to problem with driveway.com I've filed another PR, specified previous PR id (named update devel/boost) and new file locations. I hope this will help to resolve the issue. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Hi folks! This is a status update on porting boost-1.37. It is finished. Port builds, installs and deinstalls correctly. Currently I have a patch and port tarball. Files can be downloaded from: boost-port-1_37_0.tar.bz2 - http://www.driveway.com/w1d2c5l7t4 devel-boost-from-1.34.1-to-1.37.diff.txt - http://www.driveway.com/m0a2x8z0v9 Unfortunately, I was unable to send a PR, because diff is about 1Mb - devel/boost has too many files :-) Does anybody know how to request an update like this? How patch was tested: 1) verified that port builds, installs and cleanly deinstalls. 2) verified that port builds, installs and cleanly deinstalls with WITH_PYTHON=yes and WITH_PYSTE=yes flags. 3) verified that some applications (my own works in progress) using 1.34 compile if 1.37 is installed. Applications use Boost.Assign, Boost.Bind, Boost.Operators, Boost.PointerContainer, Boost.ProgramOptions, Boost.Range, and Boost.Test libraries. This can be viewed as a very basic test for boost libraries. What was not verified: 1) That devel/boost-build is usable. 2) That any application (from ports collection) that depend on devel/boost can be built with 1.37 version. 3) That boost regression suite executes successfully. Actually, at present it's not clear how to perform this, I have problems with running boost regression testing suite. Probably, it is possible to discuss this with boost developers. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Andrea, OK, after finishing with currently mutually exclusive Boost without Python and Boost with Python ports I will try to create Base libraries from Boost port and complementary Boost.Python bridge ports. Alexander Churanov 2008/11/24 Andrea Venturoli [EMAIL PROTECTED] Alexander Churanov ha scritto: ... To my mind suggested approach would simplify understanding of how to install boost. The user would ask a question like 'should I add python to my boost installation' instead of 'is my boost built with python support or not'. Sounds like a good idea to me. bye Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Hi folks! This is a status update on boost-1.37 porting. Currently port builds, installs and removes successfully. However, a PR is not filed, because I've suddenly discovered the way 'boost-python' port works. So, I've decided to take additional time for verifying that 'boost-python' is OK. I suspect that at present at least pkg-plist is not complete. My estimate for completing the work is is 2-3 days from now. For the future, I'd like to discuss the possibility of breaking boost into pieces and installing them separately. The 'devel/boost-jam' port would install bjam, the 'devel/boost/' port would install all but python-related stuff, the 'devel/boost-python' port would add pyhon stuff to existing boost installation, and 'devel/boost-build' would do something simiar to what it does now. To my mind suggested approach would simplify understanding of how to install boost. The user would ask a question like 'should I add python to my boost installation' instead of 'is my boost built with python support or not'. The only drawback I see is that several ports would require the same source tarball. For people interested in trying new port early current port tarball is placed at http://www.driveway.com/n2g6d8k2m0 Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Hi folks! I've finished with the first phase of porting boost-1.37:package builds, installs, and deinstalls correctly. The remaining tasks are to ensure how it behaves in different environments and without optional components. Boost.Python is not tested. The question is what to do next?. I see several possibilities: 1) Send a PR and hope that everything is OK. Fix issues after they actually happen. 2) Devote time to verifying that libraries actually work on different supported versions of FreeBSD. Also verify that they work with different sets of optional components and that port correctly handles dependencies. The first can be performed right now. I already have the tarball. The seconds can take additional week or more. Please, reccommend appropriate way to finish with this. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
OK, I'll send a PR. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Emanuel, It's also disappoints me that there is only year-old boost library in ports tree. I've already offered my help to Simon (see http://lists.freebsd.org/pipermail/freebsd-ports/2008-September/050846.html). I have time, equipment, experience and will for assisting in porting latest stable boost into the ports tree. After I've posted into the mailing list, people started to contact me and ask whether I know what's happened to boost port. For that reason I've send an e-mail to [EMAIL PROTECTED] at October, 14, offering my help second time. And still do not have an answer. So then, I insist on contacting Simon using other ways than [EMAIL PROTECTED] and starting a discussion about approaches for speeding up this porting task. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
Emanuel, Copying devel/boost to devel/boost-devel sounds reasonable. However, I'd like to suggest moving devel/boost to devel/boost-134 and having devel/boost updated to 1.37. For me '-devel' is always felt like something not stable enough. Another concern is that maintaners of ports that depend on boost would probably slow down the process of updating to 1.37. Forking to old version contains element of intention - it's more clear that devel/boost-134 is something out of date and temporary. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My interactive version of pkg_add - finished!
Marin, Let me suggest some names: 1) pkg_search 2) pkg_find 3) pkg_install 4) package-finder 5) package-installer 6) find-package 7) install-package 8) easy-install 9) interactive-install Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail
Simon, It's nice to have an e-mail from you. And since I'm highly interested to have most recent stable development tools and libraries on FreeBSD, I'm willing to take part in porting if necessary. So if you ever run into problems with this (technical or just lack of time), I probably will be able to help. Do not hesitate to ask me. Having recent boost is top priority for me. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail
2008/9/18 Mark Linimon [EMAIL PROTECTED] For future reference, the address to contact with issues with maintainers is [EMAIL PROTECTED] I've already forwarded your email to [EMAIL PROTECTED] mcl OK, Thank you ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
