[gentoo-user] Re: Is this an alsa th'ang?
On 2017-07-11 00:11, Mick wrote: > A few days ago I noticed as the operc messages pass by at boot time, > alsasound boot service was complaining it can't find some > files/settings. This may not be relevant, but just in case: I often get ALSA warnings when booting with a newly built kernel. Apparently the way it stores the mixer settings depends on the kernel version, and it gets slightly confused when it finds ones saved under an earlier kernel. This has been happening for as long as I remember, on any distro, and I learned to ignore it, because sound always works okay in spite of it. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
[gentoo-user] Is this an alsa th'ang?
A few days ago I noticed as the operc messages pass by at boot time, alsasound boot service was complaining it can't find some files/settings. Now I tried launching linphone from a terminal and I get this, which perplexes me as to why it is happening: $ linphone (linphone:1549): Gtk-WARNING **: Could not find signal handler 'linphone_gtk_show_assistant' ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/control/control.c:1352:(snd_ctl_open_noupdate) Invalid CTL default:0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/pcm/pcm.c:2450:(snd_pcm_open_noupdate) Unknown PCM default:0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/pcm/pcm.c:2450:(snd_pcm_open_noupdate) Unknown PCM default:0 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 1 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/control/control.c:1352:(snd_ctl_open_noupdate) Invalid CTL default:1 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 1 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/pcm/pcm.c:2450:(snd_pcm_open_noupdate) Unknown PCM default:1 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/conf.c:4817:(snd_config_expand) Unknown parameters 1 ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa- lib-1.1.2/src/pcm/pcm.c:2450:(snd_pcm_open_noupdate) Unknown PCM default:1 It seems to me linphone is calling alsa, but alsa is referring to its compile- time path. I am thinking such a path has no purpose being called at run time. Is this due to some alsa bug, or is there something wrong with my system? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Unikernels from Gentoo
Hello, http://unikernel.org/blog/2017/unikernels-are-secure https://wiki.xenproject.org/wiki/Unikernels Has anyone built a unikernel-image, from gentoo as the seed OS? I have no interests for commercial or vendor-constrained approaches to unikernels. But, to me, unikernels offer a nice and compatible pathway for many in the gentoo community. I have a looser focus on Unikernel that may of the Xen and unikernel purist. Unikernels may be of interests to those interest in bubble-tight security, performance, minimization, clusters, vm, containers or just running on less expensive or older hardware, depending on what codes you include. My goals are hundreds of images that run on a variety of low power resources, but mostly focused on 64 bit processors, DSP or many forms of resource intensive system. The super-fast boot semantic so lots of boards can brought up or shutdown, as desire has me evaluation a variety of traditional as well as minimal boot strapping codes as the kernel-seed that ties into the always on ether (ipmi, coreboot, misc-firmware, efi etc etc). Is there anyone using a gentoo centric approach to rolling (gentoo) unikernels? Ultimately once a workstation (cross)tool-chain is establish, with flexibility, it may not an issue to maintain dozens of images depending on hardware diversification. amd6 and arm64 are my current evaluation/testing architects. There are (2) approaches that are most common from my work and research:: 1. No software can be added, only data so the frameworks (software stacks) have to be preconceived and included in the image. This approach would eventually require one to develop dozens or hundreds of fully-self-contained images. But with full boot in the order of a few seconds, it might be a wonderful approach to managing resources securely. dev-util/catalyst maybe useful for generating this sorts of unikernel images. Surely a stage-4 approach is viable. 2. Flexible so you can add codes, modify frameworks and software stacks, without rebuilding everything into the boot image. This is ideal, but may open up more attack surfaces. This would be more similar to embedded-gentoo or minimized gentoo system. I have little experience with this approach. Another wonderful benefit for Unikernels, is HPC and other linux clusters; just simple fly as Unikernels leave more processor/memory available for tasks. Alpine/docker is dominating this space for now, but it's a natural pathway for gentooers to follow, imho. So if you run into github, webpages or other relevant resources, please drop me a line, or post to this thread. TIA, James
Re: [gentoo-user] grub error I've never seen in many installs
On 10 July 2017 at 22:06, Harry Putnamwrote: > grub-install /dev/sda Installing for i386-pc platform. > grub-install: error: cannot find a GRUB drive for /dev/sda1. Check > your device.map. > > Where might I find `device.map'... it isn't part of grub2. At least > grep doesn't find it with `qlist grub' > As far as I understand it, grub2 will dynamically create the device.map when it needs it, so it doesn't actually exist as a file. On my grub legacy system it is installed as /boot/grub/device.map, with the only contents being "(hd0) /dev/sda". How you would feed grub this information *before* it is installed I'm not sure, but maybe look into the USE=device-mapper flag, maybe it installs the grub-mkdevicemap executable. Arve
[gentoo-user] grub error I've never seen in many installs
Installing from install-amd64-minimal-20170706.iso into vbox vm I've done this many times and never saw this grub error: Attempting to run grub-install /dev/sda I get: grub-install /dev/sda Installing for i386-pc platform. grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. When I started googling I find hits all of which are involved with efi drives. I don't really even know for sure what an `efi' drive is and certainly never had any dealings with it when installing gentoo in a vbox vm. (Even after googling efi ... still didn't really understand what it is. Other than what it stands for. wikipaedia talks about a fat file system being involved... .. all news to me) I found something even more curious... I tried unmounting boot (dev/sda1) and recreating the ext2 file system. I left the computer for a bit, and when I came back I forgot I had not remounted boot, and ran `grub-install /dev/sda' again with /dev/sda1 unmounted. It ran with no errors and created a grub directory on / (/dev/sda4) I don't understand why grub is looking for a GRUB drive on /dev/sda1 when I asked it to install on /dev/sda The error tells me to check `device.map'. But gives no clue where it might be found. Where might I find `device.map'... it isn't part of grub2. At least grep doesn't find it with `qlist grub' Near as I can tell I've done things ... so far in the same way I have before several times... probably within 4 to 6 mnths. So I may be forgetting something important... but I know I have never run across this error before. And I have followed the handbook at least mostly.
Re: [gentoo-user] Uninstalling vbox guest addtions
On Mon, Jul 10, 2017 at 08:13:58AM -0400, Harry Putnam wrote > I notice in attempts to re-install vbox guest-additions that the > process shows `!!' at certain lines during the process. > > So, it is apparently failing to uninstall some parts of existing > guest-additions. > > I suspect that may be why the install fails. > > Anyone know how I might go about uninstalling all the bits and pieces > of a prior vbox guest-additions install manually? Manually? If it's still installed, I suggest... equery f virtualbox-guest-additions > vgafiles.txt ...to get a list of all its files, and then uninstall. Then remove any leftovers manually, checking against the list in vgafiles.txt. If it's already "uninstalled" equery won't help. In that case, go through the log file in /var/log/portage and look for lines with "!!" and remove the files it's complaining about. grep will speed up the search. Before actually removing a file, I suggest... equery b filename ...to check if it also belongs to another package. That might be the reason for the problem in the first place. -- Walter DnesI don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Hall of FAIL.
On Monday 10 Jul 2017 12:43:58 Marc Joliet wrote: > I don't think he wants help; at least, I don't *see* any explicit or > implicit requests for help. No, he's just winding you up - and anyone else who doesn't keep his/her eyes open. -- Regards Peter
Re: [gentoo-user] Anjuta - Segmentation Fault
On Monday 10 Jul 2017 12:05:56 Mart Raudsepp wrote: > The point was, no new application development should be done against > libglade, and any existing projects (that are apparently actively > worked on, as would be the case when an IDE is sought for) should work > on migrating to GtkBuilder, available in gtk+ core since 2.12 or so; so > not even a gtk3 thing to talk death exaggeration about. Ah, okay. I see now. -- Regards Peter
Re: [gentoo-user] To install a testing version of a package on a stable OS installation.
On Mon, Jul 10, 2017 at 3:52 AM, Ста Деюсwrote: > Hi, R0b0t1. > > > On Sun, 9 Jul 2017 19:18:50 -0500, you wrote: > >> > I run mixed stable and testing packages, and it seems to work very >> well. The issues I have had had made me consider switching to entirely >> testing (~amd64) because a lot of issues are actually >> incompatibilities between stable and testing packages. There are some >> people in the IRC channel on Freenode who will recommend the same >> thing. > > I consider security that is more on stable part that on testing, and i > do not need whole system to be testing -- just one package that so > poorly designed/made that requires for its new version to abandon all > the data used for its previous version and make all that data anew! -- > So, after that had been done for the new version (on another system), i > would use that data for the new version in Gentoo (rather than > recreate that data again for old version and then recreate again when > new version becomes stable) -- but in Gentoo the program is in testing > for now. > Compared to distributions like Debian, Fedora, and Ubuntu, nearly all of the packages in portage are "new," even the stable versions. As such I'm not really sure you can call the testing packages less secure by virtue of being newer. The distributions listed are the main targets for security support and Gentoo misses out on most of that. On Gentoo security support is often provided as a new version of the software in question, so testing packages might be more secure than stable ones! In a similar vein depending on what you want to do and what you need to install, the testing versions have more useful features or crucial bugfixes. I don't intend this to be an argument to convince you to globally keyword ~arch. If you don't see the need for it then that is the end of it. However, as a software developer I often need a testing version of a package, and that needs other packages which are in testing, and eventually there is some widely used package which that needs to be the version in testing or a set of packages that is mutually exclusive that becomes selected. It eventually starts to look easier to just install all testing packages by default. Gentoo is a distribution mainly for developers. Even if you are not a developer, I suspect you will start using software that is closer to the bleeding edge by virtue of using Gentoo. At some point you may start having problems like people have outlined in this thread, and if you do, do not be afraid to start using unstable packages. R0b0t1.
[gentoo-user] Uninstalling vbox guest addtions
Setup: OS: Openindian/hipster (A branch of Solaris 11) Hardware: HP xw8600 workstation: 2x Intel(R) Xeon(R) CPU X5470 @ 3.33GHz - 32 GB Ram --- --- ---=--- --- --- I notice in attempts to re-install vbox guest-additions that the process shows `!!' at certain lines during the process. So, it is apparently failing to uninstall some parts of existing guest-additions. I suspect that may be why the install fails. Anyone know how I might go about uninstalling all the bits and pieces of a prior vbox guest-additions install manually?
[gentoo-user] Re: install of vbox guest-additions failing
Peter Humphreywrites: >> Yes, or at least I have been using modules.. not sure where I would >> determine if it were enabled or not. > > Make menuconfig; it's on the first page: > [*] Enable loadable module support ---> > Ahh, at the kernel level... then yes I do.
Re: [gentoo-user] Hall of FAIL.
Hello, On Mon, 10 Jul 2017, Peter Humphrey wrote: >On Monday 10 Jul 2017 04:30:38 David Haller wrote: > >> Sorry, no such luck, my crystal ball is currently under maintainance >> and to be put in the dishwasher afterwards. > >I sent mine back for a refund - it was dead on arrival. And rightly so! Mine has, usually, worked quite as specified[0] in the last 15+ years. But at times, I just got some cryptic error message like "ENODEV" or "EAGAIN" or "ECOMM" or "EINVAL" or some such ... Or, I think, mostly "ENOMEDIUM" ... But, as I said, mine is off to its regular maintainance anyway. -dnh [0] the specs though are, uhhm, aaahm, somewhat, let's say, intricate? -- > I've gone through over-stressed to physical exhaustion... what's next? Tuesday -- Simon Burr & Kyle Hearn
Re: [gentoo-user] Hall of FAIL.
Am Montag, 10. Juli 2017, 12:21:25 CEST schrieb Mick: > On Sunday 09 Jul 2017 19:33:28 Alan Grimes wrote: > > Hey, I'm having some pretty dire FAIL issues with respect to a small but > > critical collection of packages... > > > > tortoise portage # tree -L 2 > > . > > ├── dev-libs > > │ ├── libcdio-0.94-r1 > > │ └── libcdio-paranoia-0.94_p1-r1 > > ├── media-libs > > │ └── opencv-3.1.0-r7 > > ├── media-video > > │ ├── ffmpeg-3.3.2 > > │ ├── mplayer-1.3.0-r1 > > │ ├── transcode-1.1.7-r3 > > │ └── vcdimager-0.7.24 > > ├── net-fs > > │ └── samba-4.5.11 > > ├── sys-libs > > │ ├── ldb-1.1.29-r1 > > │ └── tdb-1.3.14 > > └── www-client > > > > └── chromium-60.0.3112.40 > > Where in your fs did you get this tree from? Is it showing what you have > installed, what you want to install, something else? I think it's fairly obvious that this is supposed to be $PORTAGE_TMPDIR, i.e., we're supposed to be flabbergasted (maybe even shocked!) at all the packages that are failing. > > The most critical root failure is ffmpeg. It appears to be a gcc > > incompatibility issue with an asm directive marked volatile... =\ > > Your *interpretation* of the error is tainted by your incapacity to > understand it and resolve it. If you expect others to try to do this on > your behalf you will need to post the complete error, in unadulterated > form, as generated by emerge. I don't think he wants help; at least, I don't *see* any explicit or implicit requests for help. > > Looks like I'm going to have to go to 5.4.0... =\ > > The current stable media-video/ffmpeg is on version 3.2.4. It compiled and > installed fine here with these USE flags: > > Installed versions: 3.2.4(21:27:45 02/17/17)(X alsa amr bzip2 encode > gpl hardcoded-tables iconv librtmp mp3 network opengl opus postproc > pulseaudio sdl threads truetype vaapi vdpau vorbis vpx x264 xcb xvid zlib > -altivec -amrenc - armv5te -armv6 -armv6t2 -armvfp -bluray -bs2b -cdio > -celt -chromaprint - cpudetection -debug -doc -ebur128 -fdk -flite > -fontconfig -frei0r -fribidi - gcrypt -gme -gmp -gnutls -gsm -iec61883 > -ieee1394 -jack -jpeg2k -kvazaar - ladspa -libass -libcaca -libilbc > -libsoxr -libv4l -lzma -mipsdspr1 -mipsdspr2 -mipsfpu -mmal -modplug -neon > -nvenc -openal -openh264 -openssl -oss -pic - rubberband -samba > -schroedinger -snappy -speex -ssh -static-libs -test -theora -twolame -v4l > -wavpack -webp -x265 -zimg -zvbi ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 > -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" CPU_FLAGS_X86="mmx mmxext sse > sse2 sse3 sse4_1 sse4_2 ssse3 -3dnow -3dnowext -aes -avx -avx2 - fma3 -fma4 > -xop" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt > graph2dot ismindex pktdumper qt-faststart sidxindex trasher") > > You have not provided the output of 'emerge -upNDv media-video/ffmpeg' for > others to know which version you are trying to install and what may be > affecting the error you are getting when emerging ffmpeg. You could also > attach the output of 'emerge --info media-video/ffmpeg' as a separate file > for those who may be inclined to delve into the depths of this problem to > help you. > > If you share more relevant information to the problem you are encountering, > more people may be able to help. If you are just venting, then that's OK > for me, although it may annoy others. I find the titles of your posts > immensely entertaining. :-) That's what I think this is, venting. (Alan, if you are in fact venting, could you at least mark such posts as OT in the future, please?) Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Hall of FAIL.
On Sunday 09 Jul 2017 19:33:28 Alan Grimes wrote: > Hey, I'm having some pretty dire FAIL issues with respect to a small but > critical collection of packages... > > tortoise portage # tree -L 2 > . > ├── dev-libs > │ ├── libcdio-0.94-r1 > │ └── libcdio-paranoia-0.94_p1-r1 > ├── media-libs > │ └── opencv-3.1.0-r7 > ├── media-video > │ ├── ffmpeg-3.3.2 > │ ├── mplayer-1.3.0-r1 > │ ├── transcode-1.1.7-r3 > │ └── vcdimager-0.7.24 > ├── net-fs > │ └── samba-4.5.11 > ├── sys-libs > │ ├── ldb-1.1.29-r1 > │ └── tdb-1.3.14 > └── www-client > └── chromium-60.0.3112.40 Where in your fs did you get this tree from? Is it showing what you have installed, what you want to install, something else? > The most critical root failure is ffmpeg. It appears to be a gcc > incompatibility issue with an asm directive marked volatile... =\ Your *interpretation* of the error is tainted by your incapacity to understand it and resolve it. If you expect others to try to do this on your behalf you will need to post the complete error, in unadulterated form, as generated by emerge. > Looks like I'm going to have to go to 5.4.0... =\ The current stable media-video/ffmpeg is on version 3.2.4. It compiled and installed fine here with these USE flags: Installed versions: 3.2.4(21:27:45 02/17/17)(X alsa amr bzip2 encode gpl hardcoded-tables iconv librtmp mp3 network opengl opus postproc pulseaudio sdl threads truetype vaapi vdpau vorbis vpx x264 xcb xvid zlib -altivec -amrenc - armv5te -armv6 -armv6t2 -armvfp -bluray -bs2b -cdio -celt -chromaprint - cpudetection -debug -doc -ebur128 -fdk -flite -fontconfig -frei0r -fribidi - gcrypt -gme -gmp -gnutls -gsm -iec61883 -ieee1394 -jack -jpeg2k -kvazaar - ladspa -libass -libcaca -libilbc -libsoxr -libv4l -lzma -mipsdspr1 -mipsdspr2 -mipsfpu -mmal -modplug -neon -nvenc -openal -openh264 -openssl -oss -pic - rubberband -samba -schroedinger -snappy -speex -ssh -static-libs -test -theora -twolame -v4l -wavpack -webp -x265 -zimg -zvbi ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 sse4_1 sse4_2 ssse3 -3dnow -3dnowext -aes -avx -avx2 - fma3 -fma4 -xop" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart sidxindex trasher") You have not provided the output of 'emerge -upNDv media-video/ffmpeg' for others to know which version you are trying to install and what may be affecting the error you are getting when emerging ffmpeg. You could also attach the output of 'emerge --info media-video/ffmpeg' as a separate file for those who may be inclined to delve into the depths of this problem to help you. If you share more relevant information to the problem you are encountering, more people may be able to help. If you are just venting, then that's OK for me, although it may annoy others. I find the titles of your posts immensely entertaining. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Anjuta - Segmentation Fault
Ühel kenal päeval, E, 10.07.2017 kell 08:44, kirjutas Peter Humphrey: > On Monday 10 Jul 2017 05:22:04 Mart Raudsepp wrote: > > > Glade, as in libglade, is deprecated for years and should > > definitely > > not be used. Glade the UI design tool[1] however is not deprecated, > > it > > just now outputs GtkBuilder XML [2] instead of Glade XML. > > gnome-builder does intend to add glade UI design integration (for > > GtkBuilder), but doesn't have that feature implemented yet [3]. > > You should very seriously consider moving over [4] to GtkBuilder, > > libglade is dead. > > prh@peak ~ $ equery d libglade > * These packages depend on libglade: > dev-python/pygtk-2.24.0-r4 (>=gnome-base/libglade-2.5:2.0) > prh@peak ~ $ equery d pygtk > * These packages depend on pygtk: > media-gfx/gimp-2.8.22 (>=dev- > python/pygtk-2.10.4:2[python_targets_python2_7(-)?,- > python_single_target_jython2_7(-),-python_single_target_pypy(-),- > python_single_target_pypy3(-),-python_single_target_python3_4(-),- > python_single_target_python3_5(-),- > python_single_target_python3_6(-),python_single_target_python2_7(+)]) > > Rumours of its death are being exaggerated, so to speak. Yes, sorry. I've been busy with work, cold virus and getting gstreamer- 1.12 and GNOME 3.24 ready, so I haven't been able to deal with lower priority things, like getting rid of completely upstream unmaintained software, or security vulnerable webkit-gtk-2.4 and gstreamer:0.10. The point was, no new application development should be done against libglade, and any existing projects (that are apparently actively worked on, as would be the case when an IDE is sought for) should work on migrating to GtkBuilder, available in gtk+ core since 2.12 or so; so not even a gtk3 thing to talk death exaggeration about. Mart
Re: [gentoo-user] To install a testing version of a package on a stable OS installation.
Hi, R0b0t1. On Sun, 9 Jul 2017 19:18:50 -0500, you wrote: > > I run mixed stable and testing packages, and it seems to work very > well. The issues I have had had made me consider switching to entirely > testing (~amd64) because a lot of issues are actually > incompatibilities between stable and testing packages. There are some > people in the IRC channel on Freenode who will recommend the same > thing. I consider security that is more on stable part that on testing, and i do not need whole system to be testing -- just one package that so poorly designed/made that requires for its new version to abandon all the data used for its previous version and make all that data anew! -- So, after that had been done for the new version (on another system), i would use that data for the new version in Gentoo (rather than recreate that data again for old version and then recreate again when new version becomes stable) -- but in Gentoo the program is in testing for now. Thank you for your time, Sthu.
Re: [gentoo-user] Hall of FAIL.
On Monday 10 Jul 2017 04:30:38 David Haller wrote: > Sorry, no such luck, my crystal ball is currently under maintainance > and to be put in the dishwasher afterwards. I sent mine back for a refund - it was dead on arrival. -- Regards Peter
Re: [gentoo-user] Re: install of vbox guest-additions failing
On Sunday 09 Jul 2017 17:37:03 Harry Putnam wrote: > "J. Roeleveld"writes: > > > [...] > > > Do you have module support enabled? > > Yes, or at least I have been using modules.. not sure where I would > determine if it were enabled or not. Make menuconfig; it's on the first page: [*] Enable loadable module support ---> > I guess I'm not sure what you mean... it sounds as if you expect there > to be a conf file that says `enable modules = yes' or something. > > /etc/conf.d/modules does not seem to have any info about `enabling > modules. > > Just now to insert specific modules > > lsmod shows: > > Module Size Used by > vboxsf 40960 0 > vboxguest 208896 6 vboxsf You clearly do have module support, as you have modules loaded. > > Is the /usr/src/linux symlink pointing to the correct kernel version? > > Yes. > > > In a VBOX VM, you would normally need to compile a kernel, > > And I have done so many times. > > > the commands given are only needed when the sources are not used to > > compile the kernel. > > What commands are you talking about? > > How else would I compile a kernel but with the source? -- Regards Peter
Re: [gentoo-user] Anjuta - Segmentation Fault
On Monday 10 Jul 2017 05:22:04 Mart Raudsepp wrote: > Glade, as in libglade, is deprecated for years and should definitely > not be used. Glade the UI design tool[1] however is not deprecated, it > just now outputs GtkBuilder XML [2] instead of Glade XML. > gnome-builder does intend to add glade UI design integration (for > GtkBuilder), but doesn't have that feature implemented yet [3]. > You should very seriously consider moving over [4] to GtkBuilder, > libglade is dead. prh@peak ~ $ equery d libglade * These packages depend on libglade: dev-python/pygtk-2.24.0-r4 (>=gnome-base/libglade-2.5:2.0) prh@peak ~ $ equery d pygtk * These packages depend on pygtk: media-gfx/gimp-2.8.22 (>=dev- python/pygtk-2.10.4:2[python_targets_python2_7(-)?,- python_single_target_jython2_7(-),-python_single_target_pypy(-),- python_single_target_pypy3(-),-python_single_target_python3_4(-),- python_single_target_python3_5(-),- python_single_target_python3_6(-),python_single_target_python2_7(+)]) Rumours of its death are being exaggerated, so to speak. -- Regards Peter