Re: Python install catch 22
On 5/04/2014 9:12 PM, Willem Jan Withagen wrote: > > > Op 5 apr. 2014 om 05:48 heeft Shane Ambler het > volgende geschreven: > >> On 04/04/2014 22:42, Willem Jan Withagen wrote: >>> Hi, >>> >>> I've tried to upgrade my python 2.7 which did not work. >>> Then I deinstalled all python stuff and tried to install python3 (aka 3.3) >> >> You can install both versions of python (2.7 & 3.3) at the same time, >> but currently you can only install a module to one of the versions at a >> time. > > Sorry, > > I did not explain the situation clear enough. > > I was at 2.7, and wanted to install a 2.7 upgrade because of a bug. > If memory serves me, from 2.7.3 to 2.7.6 > > But that started mounting about missing db stuff, and having to install a > py/db of choice. > That is where I ran into the catch22, installing a db required py-tools, > which in turn starts to try to upgrade python from 2.7.3 to 2.7.6. Hi Willem, a) Can you clarify/confirm whether you tried installing/upgrading Python via ports or packages. b) Tell us exactly (method & commands) how you attempted to upgrade Python 2.7 to Python 3.3 b) If via ports, it would be helpful to know how and why the dbm module fails to build for python33 Either attach a complete build log here, or join us on IRC #freebsd-python on freenode so we can help you isolate. Koobs > Then I cleaned/removed al python stuff, and tried again. > First with 2.7 and when that did not work, I tried 3.3 with the same result. > I tried with portinstall/portupgrade as well as make && make install, but > both fail for the same reason. > > So atm I have no python at al. > >> So far there are still many modules that don't work with 3.x so you may >> want to use 2.7 if you want python with more than the default modules. >> >> The default python is still 2.7, if you want to use 3.3 then you might >> want to add >> DEFAULT_VERSIONS=PYTHON=3.3 PYTHON3=3.3 >> to your /etc/make.conf >> >>> The system everytime refuses to install because of missing a database: >>> >>> pkg-static: >>> lstat(/home2/usr/ports/lang/python33/work/stage/usr/local/lib/python3.3/lib-dynload/_dbm.so): >>> No such file or directory >>> *** [fake-pkg] Error code 74 >>> >>> [ replace python33 by python27 te get the similar error for 2.7 ] >> >> This would indicate that the dbm module wasn't built. It should be built >> and is a module that gives access to others that may be installed from >> the list below. The db modules below don't need to be installed first >> for _dbm.so to be built. >> >> This is an error compiling not related to the other modules. If your >> using a gui then scrollback in the terminal to see the error - increase >> scrollback limit if needed, from cli maybe use script to keep a log of >> the build to look through. > > Using command line in putty. > I will try again, and scan de build output for more errors. So there should > be an error building the part in the stage tree? > > >> >> gettext libiconv and gmake are the only things that need to be installed >> before python to build. > > So where does it get the DBMS stuff from? > >> Maybe there is an issue with you not building >> from /usr/ports ? > > That would be a first. This config is like this for about 6 years. > And /user/ports links to this tree. > >> >>> And then hints: >>> >>> Note that some of the standard modules are provided as separate >>> ports since they require extra dependencies: >>> >>> gdbmdatabases/py-gdbm >>> sqlite3 databases/py-sqlite3 >>> tkinter x11-toolkits/py-tkinter >>> >>> Install them as needed. >>> >>> >>> Which is nasty catch22, because one needs a recent/working python to >>> actually be able to do this. >>> >>> How do other cope with this? >>> >> >> Could using pkg to install a prebuilt binary package be an option? > > That would be the alternative, but I only do that, if nothing else works. > I've grown to always build my stuff. > >> >> What FreeBSD version are you using? > > I386 9.2-STABLE > > --WjW > ___ > 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"
problem with kde4 next step
Scanning dependencies of target kwin gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' gmake[11]: Entrando no diretório `/usr/ports/x11/kde4-workspace/work/.build' [ 98%] Building CXX object kwin/CMakeFiles/kwin.dir/kwin_dummy.cpp.o Linking CXX executable kwin [ 98%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/basictab.cpp. o gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' [ 98%] Built target kwin gmake[11]: Entrando no diretório `/usr/ports/x11/kde4-workspace/work/.build' Scanning dependencies of target kwin_gles gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' gmake[11]: Entrando no diretório `/usr/ports/x11/kde4-workspace/work/.build' [ 98%] Building CXX object kwin/CMakeFiles/kwin_gles.dir/kwin_gles_dummy.cpp.o Linking CXX executable kwin_gles [ 98%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/treeview.cpp. o /usr/local/lib/libGLESv2.so: undefined reference to `_glapi_get_dispatch' /usr/local/lib/libGLESv2.so: undefined reference to `_glapi_Dispatch' c++: error: linker command failed with exit code 1 (use -v to see invocation) gmake[11]: ** [kwin/kwin_gles] Erro 1 gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' gmake[10]: ** [kwin/CMakeFiles/kwin_gles.dir/all] Erro 2 gmake[10]: *** Esperando que os outros processos terminem [ 98%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/kmenuedit.cpp .o [ 98%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/menufile.cpp. o [100%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/menuinfo.cpp. o [100%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/khotkeys.cpp. o [100%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/kmenueditadap tor.cpp.o [100%] Building CXX object kmenuedit/CMakeFiles/kdeinit_kmenuedit.dir/khotkeys_inte rface.cpp.o Linking CXX shared library ../lib/libkdeinit4_kmenuedit.so gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' [100%] Built target kdeinit_kmenuedit gmake[10]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' gmake[9]: ** [all] Erro 2 gmake[9]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[8]: stopped in /usr/ports/x11/kde4-workspace *** Error code 1 Stop. make[7]: stopped in /usr/ports/x11/kde4-workspace *** Error code 1 Stop. make[6]: stopped in /usr/ports/x11/kde4-workspace *** Error code 1 Stop. make[5]: stopped in /usr/ports/x11-themes/kdeartwork4 *** Error code 1 Stop. make[4]: stopped in /usr/ports/x11-themes/kdeartwork4 *** Error code 1 Stop. make[3]: stopped in /usr/ports/x11-themes/kdeartwork4 *** Error code 1 Stop. make[2]: stopped in /usr/ports/x11/kde4 *** Error code 1 Stop. make[1]: stopped in /usr/ports/x11/kde4 *** Error code 1 Stop. make: stopped in /usr/ports/x11/kde4 Some idea to restore this? --- /* **Nilton José RizzoUFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **/ ___ 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: mnemosyne: gcc related error
> Hi all,
> I get the following error when running mnemosyne (games/py-mnemosyne):
> % mnemosyne
> An unexpected error has occurred.
> Please forward the following info to the developers:
> Traceback (innermost last):
> File "/usr/local/bin/mnemosyne", line 155, in
> debug_file=options.debug_file)
> File
> "/usr/local/lib/python2.7/site-packages/mnemosyne/libmnemosyne/__init__.py",
> line 164, in initialise
> self.register_components()
> File
> "/usr/local/lib/python2.7/site-packages/mnemosyne/libmnemosyne/__init__.py",
> line 215, in register_components
> exec("from %s import %s" % (module_name, class_name))
> File "", line 1, in
> File
> "/usr/local/lib/python2.7/site-packages/mnemosyne/pyqt_ui/statistics_wdgts_plotting.py",
> line 7, in
> from matplotlib import rcParams
> File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line
> 151, in
> from matplotlib.rcsetup import (defaultParams,
> File "/usr/local/lib/python2.7/site-packages/matplotlib/rcsetup.py", line
> 20, in
> from matplotlib.colors import is_color_like
> File "/usr/local/lib/python2.7/site-packages/matplotlib/colors.py", line
> 52, in
> import numpy as np
> File "/usr/local/lib/python2.7/site-packages/numpy/__init__.py", line 153,
> in
> from . import add_newdocs
> File "/usr/local/lib/python2.7/site-packages/numpy/add_newdocs.py", line
> 13, in
> from numpy.lib import add_newdoc
> File "/usr/local/lib/python2.7/site-packages/numpy/lib/__init__.py", line
> 18, in
> from .polynomial import *
> File "/usr/local/lib/python2.7/site-packages/numpy/lib/polynomial.py", line
> 19, in
> from numpy.linalg import eigvals, lstsq, inv
> File "/usr/local/lib/python2.7/site-packages/numpy/linalg/__init__.py",
> line 50, in
> from .linalg import *
> File "/usr/local/lib/python2.7/site-packages/numpy/linalg/linalg.py", line
> 29, in
> from numpy.linalg import lapack_lite, _umath_linalg
> ImportError: /lib/libgcc_s.so.1: version GCC_4.6.0 required by
> /usr/local/lib/gcc47/libgfortran.so.3 not found
> There is no problem with importing numpy or matplotlib in python:
> % python -c 'import numpy, matplotlib.pyplot'
> What could be causing this problem?
> I'm running FreeBSD 10.0-RELEASE with packages updated by pkgng.
> Thank you in advance for help,
> Henryk
I found a workaround. Instead of using the default python interpreter,
I can run mnemosyne using ipython:
% ipython /usr/local/bin/mnemosyne
I would like to ask, if someone could install mnemosyne and the
problem described above. If so, I could fill up a PR.
Please add my email to the CC field in reply.
Thank you in advance and best regards
Henryk
___
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"
problem build kde4
when i try to install the ktorrent it's always stop with an error. So I decided that will install the full kde4 meta ports, but this error occur ever time i type make install command. My solution (I think have some problem with makefile) was change the version number 4.12.3 -> 4.12.4, and the jovie ports was installed Problem report --- lor/48x48/actions/./speak.png > Compressing man pages (compress-man) ===> Installing for jovie-4.12.4 ===> Registering installation for jovie-4.12.4 pkg-static: lstat(/usr/ports/accessibility/jovie/work/stage/usr/local/lib/libkttsd.so.4.12.4): No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/accessibility/jovie *** Error code 1 Stop. make: stopped in /usr/ports/accessibility/jovie root@valfenda:/usr/ports/accessibility/jovie # find ./ -name "libkttsd*" -type f -print ./work/.build/lib/libkttsd.so.4.12.3 ./work/stage/usr/local/lib/libkttsd.so.4.12.3 root@valfenda:/usr/ports/accessibility/jovie # mv ./work/stage/usr/local/lib/libkttsd.so.4.12.3 ./work/stage/usr/local/lib/libkttsd.so.4.12.4 root@valfenda:/usr/ports/accessibility/jovie # TIA, --- /* **Nilton José RizzoUFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **/ ___ 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: cdrecord hangs hen accessing the drive
On Sat, Apr 5, 2014 at 3:58 PM, Polytropon wrote: > You could try to forcedly detach it from the SCSI bus by > using "camcontrol stop ". Maybe resetting the > bus also helps. It will then maybe be possible to kill the > cdrecord process from another terminal. See "man camcontrol" > for details. Thank you! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
ggnds:Buy R4/R4i 3DS Cards and save up to 69%
Dear client, We're pleased to inform you that, with months of research, we've introduced our new R4 products to market. We offer an over 50% discount on all our R4/R4i 3DS Cards. http://www.ggnds.com/nds-card-list.html You can get an additional discount of 15% with coupon code "ggnds.com". Promo period is until April 30 only. So hurry before you miss your chance on this amazing offer. ___ 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: cdrecord hangs hen accessing the drive
Yes, this is exactly when accessing the drive: % cdrecord lubuntu-13.10-desktop-i386.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright (C) 1995-2010 J�rg Schilling cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2). cdrecord: WARNING: This causes a high risk for buffer underruns. cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler. cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). cdrecord: WARNING: This causes a high risk for buffer underruns. Using libscg version 'schily-0.9'. No target specified, trying to find one... cdrecord: Too many CD/DVD/BD-Recorder targets found. scsibus0: 0,0,0 0) 'ASUS' 'DRW-22B2L ' '1.02' Removable CD-ROM 0,1,0 1) 'LG ' 'CD-RW CED-8120B ' '1.02' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus4: 4,0,0 400) '' '' '' NON CCS Disk 4,1,0 401) * 4,2,0 402) * 4,3,0 403) * 4,4,0 404) * 4,5,0 405) * 4,6,0 406) * 4,7,0 407) * scsibus6: 6,0,0 600) '' '' '' NON CCS Disk ^C ^C^C^C^C ^C^C^C^C^C -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: cdrecord hangs hen accessing the drive
On Sat, 5 Apr 2014 14:22:45 +0200, CeDeROM wrote: > Hello :-) > > I have noted a problem with accessing the optical disk recorders with > cdrecord - it gets stuck at start and cannot be killed (-9), probably > at the device access/detect stage. Any hints welcome :-) You could try to forcedly detach it from the SCSI bus by using "camcontrol stop ". Maybe resetting the bus also helps. It will then maybe be possible to kill the cdrecord process from another terminal. See "man camcontrol" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
cdrecord hangs hen accessing the drive
Hello :-) I have noted a problem with accessing the optical disk recorders with cdrecord - it gets stuck at start and cannot be killed (-9), probably at the device access/detect stage. Any hints welcome :-) # cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright (C) 1995-2010 J�rg Schilling Using libscg version 'schily-0.9'. scsibus0: 0,0,0 0) 'ASUS' 'DRW-22B2L ' '1.02' Removable CD-ROM 0,1,0 1) 'LG ' 'CD-RW CED-8120B ' '1.02' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus4: 4,0,0 400) '' '' '' NON CCS Disk 4,1,0 401) * 4,2,0 402) * 4,3,0 403) * 4,4,0 404) * 4,5,0 405) * 4,6,0 406) * 4,7,0 407) * scsibus6: 6,0,0 600) '' '' '' NON CCS Disk 6,1,0 601) 'PIONEER ' 'BD-RW BDR-208D' '1.10' Removable CD-ROM 6,2,0 602) * 6,3,0 603) * 6,4,0 604) * 6,5,0 605) * 6,6,0 606) * 6,7,0 607) * scsibus8: 8,0,0 800) 'Generic ' 'USB SD Reader ' '1.00' Removable Disk 8,1,0 801) * 8,2,0 802) * 8,3,0 803) * 8,4,0 804) * 8,5,0 805) * 8,6,0 806) * 8,7,0 807) * scsibus9: 9,0,0 900) 'MBED.ORG' 'MBED USB DISK ' '1.0 ' Removable Disk 9,1,0 901) * 9,2,0 902) * 9,3,0 903) * 9,4,0 904) * 9,5,0 905) * 9,6,0 906) * 9,7,0 907) * # cdrecord -dev=6,1,0 -blank=fast Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright (C) 1995-2010 J�rg Schilling scsidev: '6,1,0' scsibus: 6 target: 1 lun: 0 ^C^C^C^C ^C^C^C^C ^C ^C^C ^C^C ^C^C^C ^C^C^C^C^C^C # dmesg | tail -2 WARNING: attempt to domain_add(bluetooth) after domainfinalize() ata0: already running! # uname -a FreeBSD hexagon 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
-Original Message- From: Robert Huff OK, Obi-wan - what's the replacement for: a) "portsclean" with the C, D (single and double), and L options? (Use no more than two commands.) b) "pkg_sort" ? With these, I will cheerfully delete portupgrade. portupgrade != pkg_old Actually, for me portupgrade with pkgng is getting close the ideal solution, made yesterday the portsnap fetch upgrade portversion -v | grep -v '=' portupgrade -rf php5 dance and got the whole php rebuild from source with one minor hitch. Due the way extensions.ini is "rebuilt" every php installation I got wrong module order and couple of modules got signal 11's when trying to rebuild. After manually correcting extensions.ini order I just portupgrade -f'd the 2 failed packages in dependency order, this time without any problems. pkgng pretty nicely built just the stuff that needed rebuild, not half the installed ports. I'm already running php in cgi mode, so no mod for apache was needed (and due the recent improvement, the said mod was not autoinstalled to my httpd.conf either). -Reko ___ 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: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
On Sat, 05 Apr 2014 07:55:48 -0400 Robert Huff wrote: > Matthew Seaman writes: > > > pkg(8) does a damn sight more than the old pkg_tools. > > Granted, though much of it I currently have little use > for. :-) > > >> "pkgng" can do almost everything the old system can, and does it > >> better.> > > > > s/almost// > > OK, Obi-wan - what's the replacement for: > > a) "portsclean" with the C, D (single and double), and L > options? (Use no more than two commands.) > b) "pkg_sort" ? > > With these, I will cheerfully delete portupgrade. portupgrade isn't part of "the old pkg_tools" ___ 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"
pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
Matthew Seaman writes: > pkg(8) does a damn sight more than the old pkg_tools. Granted, though much of it I currently have little use for. :-) >> "pkgng" can do almost everything the old system can, and does it >> better.> > > s/almost// OK, Obi-wan - what's the replacement for: a) "portsclean" with the C, D (single and double), and L options? (Use no more than two commands.) b) "pkg_sort" ? With these, I will cheerfully delete portupgrade. Robert Huff ___ 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 install catch 22
Op 5 apr. 2014 om 05:48 heeft Shane Ambler het volgende geschreven: > On 04/04/2014 22:42, Willem Jan Withagen wrote: >> Hi, >> >> I've tried to upgrade my python 2.7 which did not work. >> Then I deinstalled all python stuff and tried to install python3 (aka 3.3) > > You can install both versions of python (2.7 & 3.3) at the same time, > but currently you can only install a module to one of the versions at a > time. Sorry, I did not explain the situation clear enough. I was at 2.7, and wanted to install a 2.7 upgrade because of a bug. If memory serves me, from 2.7.3 to 2.7.6 But that started mounting about missing db stuff, and having to install a py/db of choice. That is where I ran into the catch22, installing a db required py-tools, which in turn starts to try to upgrade python from 2.7.3 to 2.7.6. Then I cleaned/removed al python stuff, and tried again. First with 2.7 and when that did not work, I tried 3.3 with the same result. I tried with portinstall/portupgrade as well as make && make install, but both fail for the same reason. So atm I have no python at al. > So far there are still many modules that don't work with 3.x so you may > want to use 2.7 if you want python with more than the default modules. > > The default python is still 2.7, if you want to use 3.3 then you might > want to add > DEFAULT_VERSIONS=PYTHON=3.3 PYTHON3=3.3 > to your /etc/make.conf > >> The system everytime refuses to install because of missing a database: >> >> pkg-static: >> lstat(/home2/usr/ports/lang/python33/work/stage/usr/local/lib/python3.3/lib-dynload/_dbm.so): >> No such file or directory >> *** [fake-pkg] Error code 74 >> >> [ replace python33 by python27 te get the similar error for 2.7 ] > > This would indicate that the dbm module wasn't built. It should be built > and is a module that gives access to others that may be installed from > the list below. The db modules below don't need to be installed first > for _dbm.so to be built. > > This is an error compiling not related to the other modules. If your > using a gui then scrollback in the terminal to see the error - increase > scrollback limit if needed, from cli maybe use script to keep a log of > the build to look through. Using command line in putty. I will try again, and scan de build output for more errors. So there should be an error building the part in the stage tree? > > gettext libiconv and gmake are the only things that need to be installed > before python to build. So where does it get the DBMS stuff from? > Maybe there is an issue with you not building > from /usr/ports ? That would be a first. This config is like this for about 6 years. And /user/ports links to this tree. > >> And then hints: >> >> Note that some of the standard modules are provided as separate >> ports since they require extra dependencies: >> >> gdbmdatabases/py-gdbm >> sqlite3 databases/py-sqlite3 >> tkinter x11-toolkits/py-tkinter >> >> Install them as needed. >> >> >> Which is nasty catch22, because one needs a recent/working python to >> actually be able to do this. >> >> How do other cope with this? >> > > Could using pkg to install a prebuilt binary package be an option? That would be the alternative, but I only do that, if nothing else works. I've grown to always build my stuff. > > What FreeBSD version are you using? I386 9.2-STABLE --WjW ___ 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: pkgng vs. portupgrade reporting ports outdated
On 05/04/2014 00:44, sindrome wrote: > foo:109:/home/foobar# pkg_version -v |grep needs it shows 240 ports that need > updating. It shows that you have out-of-date data in the remains of the old-style /var/db/pkg that pkg2ng leaves in place. Please execute the following command to clean up /var/db/pkg and leave just the database that pkg(8) uses: # find /var/db/pkg -mindepth 1 -type d -print0 | xargs -0 rm -rf Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: pkgng vs. portupgrade reporting ports outdated
On 04/04/2014 23:49, Robert Huff wrote: > "pkgng" can do almost everything the old system can, and does it > better. s/almost// pkg(8) does a damn sight more than the old pkg_tools. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pkgng vs. portupgrade reporting ports outdated
On 04/04/2014 23:02, sindrome wrote: > So I still keep my source, ports and docs in sync via svn update. Here's > where the issue comes in. After I have done the pkg upgrade and it tells me > all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens > of ports that are not up-to-date and further the versions it's saying I have > installed are not consistent with the versions that were installed through > pkgng. If I try and portupgrade it won't upgrade the ports and just > returns me to the prompt as if there is nothing out of date. > Why is there such a difference here? It seems that if I do a pkgng update / > pkg upgrade it should be consistent with the same versions that are being > reported after an 'svn update' and report back that all ports are up-to-date > no matter which command I type. So now I can't seem to upgrade through > portupgrade to get the rest of the ports to the versions reported in the > ports tree and pkgng says I'm up-to-date. Once you have switched to pkg(8), the old pkg_tools commands will return bogus results. You *cannot* mix usage of pkg(8) and pkg_tools. I don't know why this seems to be such a difficult concept for people to understand. In your case, you need to use 'pkg version -v' not 'pkg_version -v'. Actually instead of this: pkg version -v | grep needs Try this: pkg version -vIl\< That compares your installed ports to what is listed as available in the ports index. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
