kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
Hi, on 2.9-DEVELOPMENT DragonFly v2.9.1.183.g32fe4-DEVELOPMENT #5: Tue Dec 7 19:38:14 IST 2010 I get this error during bmake update EP' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:134: error: 'SWAIT' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:135: error: 'SLOCK' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp: In member function 'bool KSysGuard::ProcessesLocal::Private::readProcCmdline(long int, KSysGuard::Process*)': /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:158: warning: unused variable 'p' gmake[2]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/processes_local_p.o] Error 1 gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2 gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase4 *** Error code 1 thanks --Siju
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
On 13.12.10 13:18, Siju George wrote: I get this error during bmake update EP' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase- workspace-4.4.5/libs/ksysguard/processcore /processes_freebsd_p.cpp:134: error: 'SWAIT' was not declared in this scope Please, someone write reasonable support for DragonFly - separate files, no messing with FreeBSD specific files etc. I promise I'll blow the dust away from my DragonFly machine and will commit it into the upstream. -- Hasso Tepper
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
I have answered this question quite often on this mailing list. Kde4 as in pkgsrc doesn't compile on DragonFly. I have submitted patches upstream to kde a few months ago. If you want a workaround just search for my patches on this ml or on bugs.kde4.org. Regards, Alex On 13 Dec 2010 11:25, Siju George sgeorge...@gmail.com wrote: Hi, on 2.9-DEVELOPMENT DragonFly v2.9.1.183.g32fe4-DEVELOPMENT #5: Tue Dec 7 19:38:14 IST 2010 I get this error during bmake update EP' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:134: error: 'SWAIT' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:135: error: 'SLOCK' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp: In member function 'bool KSysGuard::ProcessesLocal::Private::readProcCmdline(long int, KSysGuard::Process*)': /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:158: warning: unused variable 'p' gmake[2]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/processes_local_p.o] Error 1 gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2 gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase4 *** Error code 1 thanks --Siju
Re: less at end of file
Chris Turner c.tur...@199technologies.org wrote: Jeremy C. Reed wrote: less is not more. man uses more by default. you can: export PAGER=less or setenv PAGER less to change the man(1) behavior, btw. Just for completeness, if you rather want the opposite behaviour, i.e. less to behave like traditional more, you can do this: export LESS_IS_MORE=1 Of course, you can configure the behaviour when hitting end-of-file with the -e and -E options. You can put them in the LESS environment variable (or MORE if you use the more compatibility mode) or in the .lesskey file. See the less(1) and lesskey(1) manual pages for details. Best regards Oliver PS: For inspiration, here's an excerpt from my personal .lesskey file (actually there are more key bindings) ... #command \e[ggoto-mark \^ g goto-mark \^ #env LESS= -Meiqa -\#8 -j.5 -z-4 LESSCHARSET = latin1 LESSOPEN= |/usr/bin/lesspipe.sh %s -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
Re: Encrypted root questions
Thanks! Yes, I'm using master because I need it for the SATA ports on my
motherboard. I'd be willing to put up some documentation for this stuff,
but I don't want to snatch the google code-in opportunity away from some
deserving person. ;-)
Tim
On Mon, Dec 13, 2010 at 12:00 AM, Alex Hornung ahorn...@gmail.com wrote:
I'm assuming you are using the 'master' branch, otherwise the
dm_target_crypt_load=YES is not necessary. For whatever it's worth, I've
added a task to google code-in a few weeks ago to document all this dm
stuff, both cryptsetup and lvm, basically. Hopefully there will be a taker.
For encrypted swap you definitely should be running the 'master' branch, as
the release dm_target_crypt, while it supports it, would have problems under
memory pressure. In any case: to set it up, you'd use the /etc/crypttab
file; just add a line a la:
swap/dev/da0s1bnonenone
or, possibly, setting a keyfile, if that's what you'd like to use, as the
third parameter. Man page should help you out on that. Then just add the
following line to fstab:
/dev/mapper/swapnoneswapsw10
and you'll be all set up.
Regards,
Alex Hornung
On 13/12/2010 06:24, Tim Darby wrote:
I'm trying to set up an encrypted root filesystem with disk A containing
/boot and swap and disk B containing the encrypted root. Having never done
this before, I figured I'd use /share/examples/rconfig/encrypted_root.sh as
a guide. However, I ran into a couple of snags, so maybe someone can tell
me what I'm doing wrong.
First, this command appears to have a typo:
cryptsetup -y luksFormat /dev/${disk}s1 == shouldn't this be s1d?
Second, in these lines for loader.conf:
dm_load=YES
initrd.img_load=YES
initrd.img_type=md_image
vfs.root.mountfrom=ufs:md0s0
vfs.root.realroot=crypt:hammer:/dev/${disk}s1d:root
This failed for me during boot right after it prompted me for the
passphrase. Eventually, I realized that it was not able to find
dm_target_crypt.ko at the point where it was trying to open the encrypted
filesytem and I was only able to get the machine to successfully boot all
the way by adding the line:
dm_target_crypt_load=YES
I'm also interested in encrypted swap. Is there anything tricky about
setting that up?
Thanks,
Tim
Re: Encrypted root questions
Alex Hornung wrote: For whatever it's worth, I've added a task to google code-in a few weeks ago to document all this dm stuff, both cryptsetup and lvm, basically. A bit OT but shouldn't this stuff go in bugs / the wiki and then be referenced to any google code-in or foo barbaz-quux to prevent fragmentation? (from someone who has had to do 'where did that note go' many a time :) cheers
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
On Mon, Dec 13, 2010 at 5:41 PM, Alex Hornung ahorn...@gmail.com wrote: I have answered this question quite often on this mailing list. Kde4 as in pkgsrc doesn't compile on DragonFly. I have submitted patches upstream to kde a few months ago. I searched and got http://leaf.dragonflybsd.org/~alexh/kdebase-workspace4.patch from http://leaf.dragonflybsd.org/mailarchive/users/2010-01/msg00030.html but that patch URL gives http 404 error. Why cant't it be committed directly to the dragonfly-pkgsrc branch? Well I don't know much about this but I thought dragonfly-pkgsrc branch was made just for this? thanks :-) --Siju
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
On Mon, Dec 13, 2010 at 5:01 AM, Hasso Tepper ha...@estpak.ee wrote: On 13.12.10 13:18, Siju George wrote: I get this error during bmake update EP' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase- workspace-4.4.5/libs/ksysguard/processcore /processes_freebsd_p.cpp:134: error: 'SWAIT' was not declared in this scope Please, someone write reasonable support for DragonFly - separate files, no messing with FreeBSD specific files etc. I promise I'll blow the dust away from my DragonFly machine and will commit it into the upstream. -- Hasso Tepper Hasso, I will make sure this gets done. Sam
