INDEX now builds successfully on 7.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Le Dim 11 jan 09 à 0:25:54 +0100, Pav Lucistnik p...@freebsd.org écrivait : 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 That's certainly a possibility -- but can two boost versions coexist in a single system? I don't know, but I know at least one port which is broken and cannot be fixed, because the required upgrade needs a newer boost (cad/freecad). Regards, -- Th. Thomas. pgp3I6QdIFiha.pgp Description: PGP signature
INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: firefox-i18n-2.0.0.20: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: ja-zope-jaMailHost-0.4.4: no entry for /usr/ports/www/zope make_index: firefox3-i18n-3.0.5: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: squishdot-1.5.0_1: no entry for /usr/ports/www/zope make_index: thunderbird-i18n-2.0.0.18: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: plone-2.5.5: no entry for /usr/ports/www/zope29 make_index: ja-zope-ejSplitter-0.5.1: no entry for /usr/ports/www/zope make_index: ja-pycodec-zope-1.4.11_1: no entry for /usr/ports/www/zope make_index: knowledgekit-1.6.7: no entry for /usr/ports/www/zope make_index: hs-gtk2hs-0.9.13,1: no entry for /usr/ports/www/xulrunner make_index: hs-gtk2hs-0.9.13,1: no entry for /usr/ports/www/xulrunner make_index: eclipse-3.3.2: no entry for /usr/ports/www/xulrunner make_index: eclipse-3.3.2: no entry for /usr/ports/www/xulrunner make_index: plone3-3.1.7: no entry for /usr/ports/www/zope210 make_index: ngmp-0.1.3_1: no entry for /usr/ports/www/zend-framework make_index: sunbird-i18n-0.8: no entry for /usr/ports/www/xpi-quick-locale-switcher Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Committers on the hook: chinsan glewis leeym obrien Most recent CVS update was: U audio/p5-Audio-MPD-Common/Makefile U audio/p5-Audio-MPD-Common/distinfo U devel/libcheck/Makefile U devel/libcheck/distinfo U devel/libcheck/pkg-plist U devel/libcheck/files/patch-Makefile.in U devel/libcheck/files/patch-check.m4 U devel/libcheck/files/patch-doc-Makefile.in U graphics/p5-Graphics-Color/Makefile U graphics/p5-Graphics-Color/distinfo U java/eclipse-webtools/Makefile U java/eclipse-webtools/distinfo U misc/figlet/pkg-plist U net/mtr/Makefile ___ 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: INDEX build failed for 8.x
This is due to pointyhat filling its discs up. No worries here. -erwin On Sun, Jan 11, 2009 at 09:26:47AM +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-8 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: firefox-i18n-2.0.0.20: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: ja-zope-jaMailHost-0.4.4: no entry for /usr/ports/www/zope make_index: firefox3-i18n-3.0.5: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: squishdot-1.5.0_1: no entry for /usr/ports/www/zope make_index: thunderbird-i18n-2.0.0.18: no entry for /usr/ports/www/xpi-quick-locale-switcher make_index: plone-2.5.5: no entry for /usr/ports/www/zope29 make_index: ja-zope-ejSplitter-0.5.1: no entry for /usr/ports/www/zope make_index: ja-pycodec-zope-1.4.11_1: no entry for /usr/ports/www/zope make_index: knowledgekit-1.6.7: no entry for /usr/ports/www/zope make_index: hs-gtk2hs-0.9.13,1: no entry for /usr/ports/www/xulrunner make_index: hs-gtk2hs-0.9.13,1: no entry for /usr/ports/www/xulrunner make_index: eclipse-3.3.2: no entry for /usr/ports/www/xulrunner make_index: eclipse-3.3.2: no entry for /usr/ports/www/xulrunner make_index: plone3-3.1.7: no entry for /usr/ports/www/zope210 make_index: ngmp-0.1.3_1: no entry for /usr/ports/www/zend-framework make_index: sunbird-i18n-0.8: no entry for /usr/ports/www/xpi-quick-locale-switcher Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Warning: Duplicate INDEX entry: Committers on the hook: chinsan glewis leeym obrien Most recent CVS update was: U audio/p5-Audio-MPD-Common/Makefile U audio/p5-Audio-MPD-Common/distinfo U devel/libcheck/Makefile U devel/libcheck/distinfo U devel/libcheck/pkg-plist U devel/libcheck/files/patch-Makefile.in U devel/libcheck/files/patch-check.m4 U devel/libcheck/files/patch-doc-Makefile.in U graphics/p5-Graphics-Color/Makefile U graphics/p5-Graphics-Color/distinfo U java/eclipse-webtools/Makefile U java/eclipse-webtools/distinfo U misc/figlet/pkg-plist U net/mtr/Makefile ___ 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 -- Erwin Lansing http://droso.org Prediction is very difficult er...@freebsd.org especially about the future er...@aauug.dk pgpbvuxSTHroC.pgp Description: PGP signature
/ports/cad/spice is broken
/ports/cad/spice comes back with a size mismatch. I kinda new so it is not easily fixable my me yet. ___ 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
numerous gcc installations
Hi list, Could anyone please explain to me whether it's really required to have two extra versions of gcc installed. I Recently upgraded py25-numpy, which in turn pulled in gcc-4.2.5_20081126 as a dependency. A few days ago blas refused to compile because: ===Verifying reinstall for gfortran43 in /usr/ports/lang/gcc43 Making GCC 4.3.3 for FreeBSD 7.1 target=i386-portbld-freebsd7.1 You need to increase the datasize limit to at least 70 (and set kern.maxdsiz=734003200 in /boot/loader.conf) to build with Java support. *** Error code 1 ... so if it wasn't for these missing settings, I would now be the proud owner of two extra gcc installations, gcc-4.2.5 and gcc-4.3.3. Is this correct??? blas is required by py-num, which then effectively requires the two gcc's. br - Nikolaj ___ 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: audio/squeezecenter-7.3.1 Extension downloader broken?
In message xzc+vxyq7ozjf...@lap.knigma.org, Mark Knight ma...@knigma.org writes Directories are appearing in this location but when I re-start squeezecenter it's as if the Plugins aren't installed. I'm not seeing any errors in the log files. This is fixed in the latest version of the port. Thanks!! -- Mark A. R. Knight finger: ma...@knigma.org Tel: +44 7880 556751http://www.knigma.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: numerous gcc installations
Nikolaj Thygesen wrote: Could anyone please explain to me whether it's really required to have two extra versions of gcc installed. I Recently upgraded py25-numpy, which in turn pulled in gcc-4.2.5_20081126 as a dependency. A few days ago blas refused to compile because: This occurred to me recently. Fortunately you can find precompiled blas, scipy and numpy (pkg_add -r py-numpy works). But i was out of luck with matplotlib, which required pkg_adding gcc-42 and then compiling tons of stuff. One of them (agg, i think, requires DISPLAY to be set and accessible in the configure script !!!) hence breaks the build for matplotlib. -- Michel TALON ___ 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
Porting sup MUA to FreeBSD
Hi everyone, I'm trying to port sup[1], a MUA, to FreeBSD. For that I've created its port and the ports of it dependencies. I've faced following problems while porting: 1. Some of its dependencies are already ported to FreeBSD but are using a tarball as source instead of the gem which is expected by the sup gem. So, I've created separate ports for those packages as gems. I'm wondering if this is okay. 2. The gem of sup needs some patching for FreeBSD, which I'm not able to do because FreeBSD ports system install gems in oneshot (i.e. no separate build or extract target, everything is done in install target). The NetBSD's rubygem[2] packaging system on the other hand extracts, builds and packages gems separately. So my port of sup installs fine but doesn't function as expected due to some GNU/Linux specific stuff involved. Any suggestions about the problems mentioned above are welcome. I've not submitted them to the PR database yet. As I don't know ruby, it will be difficult for me to maintain the ports. If anyone else is interested in maintaining/looking at the ports, please visit following URL: http://gitorious.org/projects/abbe-freebsd-ports/repos/mainline/commits/b4577e9ed16f0f2d18f061804e784f294b264a98 References: [1] http://sup.rubyforge.org/ [2] ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc-current/misc/rubygems/rubygem.mk Thanks -- Ashish Shukla pgpcxFdcp1UJ9.pgp Description: PGP signature
INDEX now builds successfully on 8.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: xterm-238
Hello, After updating my xterm port, uxterm stopped working saying that: % uxterm xterm: bad command line option -u8 usage: xterm [-/+132] [-C] [-Sccn] [-T string] [-/+ah] [-/+ai] [-/+aw] [-b number] [-/+bc] [-bcf milliseconds] [-bcn milliseconds] [-bd color] [-/+bdc] [-bg color] [-bw number] [-/+cb] [-cc classrange] [-class string] [-/+cm] [-/+cn] [-cr color] [-/+cu] [-/+dc] [-display displayname] [-e command args ...] [-fa pattern] [-fb fontname] [-/+fbb] [-/+fbx] [-fd pattern] [-fg color] [-fi fontname] [-fn fontname] [-fs size] [-fx fontname] [#geom] [%geom] [-geometry geom] [-help] [-/+hm] [-/+hold] [-iconic] [-/+ie] [-/+im] [-into windowId] [-/+j] [-/+k8] [-kt keyboardtype] [-/+l] [-leftbar] [-lf filename] [-/+ls] [-/+mb] [-mc milliseconds] [-/+mesg] [-ms color] [-n string] [-name string] [-nb number] [-/+nul] [-/+pc] [-/+pob] [-rightbar] [-/+rv] [-/+rvc] [-/+rw] [-/+s] [-/+samename] [-/+sb] [-selbg color] [-selfg color] [-/+sf] [-/+si] [-/+sk] [-sl number] [-/+sm] [-/+sp] [-/+t] [-ti termid] [-title string] [-tm string] [-tn name] [-/+uc] [-/+ulc] [-/+ulit] [-/+ut] [-/+vb] [-version] [-/+wf] [-xrm resourcestring] [-ziconbeep percent] Type xterm -help for a full description. % Then I found in the x11/xterm Makefile this: .if defined(WITH_WIDE_CHARS) CONFIGURE_ARGS+=--enable-wide-chars --enable-luit .endif and, of course after I've rebuilt x11/xterm with make -DWITH_WIDE_CHARS everything worked. I guess if the uxterm wrapper script is installed, then WITH_WIDE_CHARS should probably be enabled by default. What do you think? Have a nice day! Vlad ___ 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: HEADS UP: GNOME 2.24.2 is now available for FreeBSD
Hello Joe! Can you let us know when associated updates to The FreeBSD-Gnome site will be updated to reflect the new version, including recommended upgrade procedures, please? I'm referring to: http://www.freebsd.org/gnome/. If I'm pointing to the wrong place here, do forgive.., Thanks. Regards, S Roberts On Sat, 10 Jan 2009, Joe Marcus Clarke wrote: Presenting GNOME 2.24 for FreeBSD. See http://library.gnome.org/misc/release-notes/2.24/ for the general release notes. On the FreeBSD front, this release introduces Fuse support in HAL, adds multi-CPU support to libgtop, WebKit updates, and fixes some long-standing seahorse and gnome-keyring bugs. The documentation updates to the website are forthcoming. Be sure to read /usr/ports/UPDATING, and let gn...@freebsd.org know if you have any problems. This release features commits by adamw, ahze, kwm, mezz, and myself. It would not have been possible without are contributors and testers: Alexander Loginov Craig Butler Dmitry Marakasov Eric L. Chen Joseph S. Atkinson Kris Moore Lapo Luchini Nikos Ntarmos Pawel Worach Romain Tartiere TAOKA Fumiyoshi Romain Tartiere TAOKA Fumiyoshi Yasuda Keisuke Zyl aZ bf Florent Thoumie Peter Wemm pluknet Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: HEADS UP: GNOME 2.24.2 is now available for FreeBSD
On Sun, 11 Jan 2009 08:13:45 -0600, Stacey Roberts sta...@vickiandstacey.com wrote: Hello Joe! Can you let us know when associated updates to The FreeBSD-Gnome site will be updated to reflect the new version, including recommended upgrade procedures, please? I'm referring to: http://www.freebsd.org/gnome/. If I'm pointing to the wrong place here, do forgive.., The /usr/ports/UPDATING is always first place you should be look at for the upgrade. Thanks. Regards, S Roberts On Sat, 10 Jan 2009, Joe Marcus Clarke wrote: Presenting GNOME 2.24 for FreeBSD. See http://library.gnome.org/misc/release-notes/2.24/ for the general release notes. On the FreeBSD front, this release introduces Fuse support in HAL, adds multi-CPU support to libgtop, WebKit updates, and fixes some long-standing seahorse and gnome-keyring bugs. The documentation updates to the website are forthcoming. Read above here again. Cheers, Mezz Be sure to read /usr/ports/UPDATING, and let gn...@freebsd.org know if you have any problems. This release features commits by adamw, ahze, kwm, mezz, and myself. It would not have been possible without are contributors and testers: Alexander Loginov Craig Butler Dmitry Marakasov Eric L. Chen Joseph S. Atkinson Kris Moore Lapo Luchini Nikos Ntarmos Pawel Worach Romain Tartiere TAOKA Fumiyoshi Romain Tartiere TAOKA Fumiyoshi Yasuda Keisuke Zyl aZ bf Florent Thoumie Peter Wemm pluknet Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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: numerous gcc installations
Nikolaj Thygesen wrote: Hi list, Could anyone please explain to me whether it's really required to have two extra versions of gcc installed. I Recently upgraded py25-numpy, which in turn pulled in gcc-4.2.5_20081126 as a dependency. A few days ago blas refused to compile because: ===Verifying reinstall for gfortran43 in /usr/ports/lang/gcc43 Making GCC 4.3.3 for FreeBSD 7.1 target=i386-portbld-freebsd7.1 You need to increase the datasize limit to at least 70 (and set kern.maxdsiz=734003200 in /boot/loader.conf) to build with Java support. *** Error code 1 ... so if it wasn't for these missing settings, I would now be the proud owner of two extra gcc installations, gcc-4.2.5 and gcc-4.3.3. Is this correct??? blas is required by py-num, which then effectively requires the two gcc's. br - Nikolaj A few days ago, gcc-4.3 became the default fortran compiler for the ports. Go ahead and erase the gcc-4.2 compiler - create the gcc-4.3 compiler, and everything after that will be fine. If you don't want to increase kern.maxdsiz, then it looks like setting WITHOUT_JAVA will stop that error occurring. ___ 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
Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300: 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. 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. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: FreeBSD Port: xterm-238
Vlad GURDIGA writes: Hello, After updating my xterm port, uxterm stopped working saying that: % uxterm xterm: bad command line option -u8 usage: xterm [-/+132] [-C] [-Sccn] [-T string] [-/+ah] [-/+ai] [-/+aw] [-b number] [-/+bc] [-bcf milliseconds] [-bcn milliseconds] [-bd color] [-/+bdc] [-bg color] [-bw number] [-/+cb] [-cc classrange] [-class string] [-/+cm] [-/+cn] [-cr color] [-/+cu] [-/+dc] [-display displayname] [-e command args ...] [-fa pattern] [-fb fontname] [-/+fbb] [-/+fbx] [-fd pattern] [-fg color] [-fi fontname] [-fn fontname] [-fs size] [-fx fontname] [#geom] [%geom] [-geometry geom] [-help] [-/+hm] [-/+hold] [-iconic] [-/+ie] [-/+im] [-into windowId] [-/+j] [-/+k8] [-kt keyboardtype] [-/+l] [-leftbar] [-lf filename] [-/+ls] [-/+mb] [-mc milliseconds] [-/+mesg] [-ms color] [-n string] [-name string] [-nb number] [-/+nul] [-/+pc] [-/+pob] [-rightbar] [-/+rv] [-/+rvc] [-/+rw] [-/+s] [-/+samename] [-/+sb] [-selbg color] [-selfg color] [-/+sf] [-/+si] [-/+sk] [-sl number] [-/+sm] [-/+sp] [-/+t] [-ti termid] [-title string] [-tm string] [-tn name] [-/+uc] [-/+ulc] [-/+ulit] [-/+ut] [-/+vb] [-version] [-/+wf] [-xrm resourcestring] [-ziconbeep percent] Type xterm -help for a full description. % Then I found in the x11/xterm Makefile this: .if defined(WITH_WIDE_CHARS) CONFIGURE_ARGS+=--enable-wide-chars --enable-luit .endif and, of course after I've rebuilt x11/xterm with make -DWITH_WIDE_CHARS everything worked. I guess if the uxterm wrapper script is installed, then WITH_WIDE_CHARS should probably be enabled by default. What do you think? I think this should be in the OPTIONS variable of xterm port's Makefile. Because this variable is not even documented anywhere and you won't notice this unless you're in habit of reading the port Makefile. -- Ashish SHUKLA pgp4Z6TrHojQt.pgp Description: PGP signature
Re: numerous gcc installations
Robert Huff wrote: Hello: A few days ago, gcc-4.3 became the default fortran compiler for the ports. Go ahead and erase the gcc-4.2 compiler - create the gcc-4.3 compiler, and everything after that will be fine. 1) What is the realtionship between this gcc and the gcc used to compile the system? 2) Do you know why this isn't noted in /usr/ports/UPDATING? Answers: 2) You make a good point. Why don't you raise this on po...@freebsd? This should be corrected. In fact, I am going to copy this to po...@freebsd. 1) I think that in most cases, the only reason why gcc is brought in is because the gcc that is in the base system does not include a fortran compiler. So any port that uses fortran (e.g. lapack, etc) has to install a fortran compiler. Having said all this, why doesn't bsd.gcc.mk first check to see if gfortran42 was already installed, and then only install gfortran43 if a fortran is needed? But I have the impression that quite a few changes have been made to bsd.gcc.mk recently, so some mistakes are understandable. Stephen ___ 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
(no subject)
FYI Regarding the pib port under FreeBSD 7.1 (Release). After a 'make install', I needed to do the following for it to work: cd /usr/local/bin/ ln -s wish8.4 wish8.2 cd /usr/ports ln -s INDEX-7 INDEX - thanks for your time, Patrice Remy PORTNAME= pib PORTVERSION=1.2 PORTREVISION= 2 CATEGORIES= ports-mgmt tk ___ 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
On Sun, 11 Jan 2009 12:38:10 -0600, Alexander Churanov alexanderchura...@gmail.com wrote: 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 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 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 -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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
numerous gcc installations
Yes, the gcc ports are used partly because the Fortran compiler was removed from the base system. (They might have been used anyway, to take advantage of the improvements in later versions of gcc. ) bsd.gcc.mk fixes the specific compiler used via the value of the WITH_FORTRAN variable in a port Makefile. This is done intentionally, as there are substantive differences between the available compilers -- the compilers are not considered to be interchangeable. The fact that some ports continued to use gfortran42, which gerald@ and maho@ deprecated in the recent round of changes, was a mistake that has been or will be corrected. If you want to use it, don't use the WITH_FORTRAN knob; or patch bsd.gcc.mk. I agree that this probably should have been mentioned in UPDATING, but they were probably too busy fixing the many small problems that arose after the changes. Regards, b. ___ 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
