Re: [gentoo-user] Computer does not boot
Joseph syscon...@gmail.com [15-02-01 10:04]: On 01/31/15 23:42, Dale wrote: [snip] Hi Joseph, may be only a accidental coincidence... One thing I can think of is an empty bios coin cell. If that battery is flat, the bios will complain settings are gone. Why would that cause grub to fail? Dont know the reason...I only experienced it several times... Regards Meino I've had it happen to me once too. In my case, the BIOS just went back to default settings. The only real change was the loss of the clock setting but it didn't complain, it just booted. After I replaced the battery, I went back and changed my settings to what I remembered them being. Since then, I change that battery every few years, while the system is running so that I don't lose any settings at all. ;-) Be careful. Dale Is there a way to backup bios setting to a text file etc.; beside special Windows utility? -- Joseph Depends on the mobo. Mine is a ASUS Cross Hair Formula IV. That BIOS is able to store several BIOS configurations. Best regards, Meino
[gentoo-user] [OT] ASUS Crosshair V Formula-Z MB
I just got me a new MB, a ASUS Crosshair V Formula-Z, after my old MB fried due to a fan failure. Is anyone else (on this list) using this MB, with Gentoo of cause? If you are, have you got all the sensors working? I can not get information from all the sensors on this MB (compared with what the BIOS shows) and some of the values that do show are wrong , some temp-sensor shows as negative (and my room is not THAT cold). Regards, -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! *** smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS
On Sunday 01 Feb 2015 00:18:40 Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough, but a 'login shell', that is, one started by /bin/login, is setup with a different environment to a shell that's started by su (or by, say, cron). This is why a shell command or script may work for you when you're logged in, but not if you run it from cron. I'm sure other's can explain it more correctly and fully. When you follow su with - it will login into the pwd of /root. Without - you will find yourself in the same directorate you happened to be when you ran su. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] [OT] ASUS Crosshair V Formula-Z MB
On Sunday, February 01, 2015 12:16:20 PM Dan Johansson wrote: I just got me a new MB, a ASUS Crosshair V Formula-Z, after my old MB fried due to a fan failure. Is anyone else (on this list) using this MB, with Gentoo of cause? If you are, have you got all the sensors working? I can not get information from all the sensors on this MB (compared with what the BIOS shows) and some of the values that do show are wrong , some temp-sensor shows as negative (and my room is not THAT cold). Regards, I don't have that motherboard, but most ASUS boards I used (still use one, really old board (p5b)) use SENSORS_ATK0110.
Re: [gentoo-user] [OT] ASUS Crosshair V Formula-Z MB
On Sunday 01 Feb 2015 11:16:20 Dan Johansson wrote: I just got me a new MB, a ASUS Crosshair V Formula-Z, after my old MB fried due to a fan failure. Is anyone else (on this list) using this MB, with Gentoo of cause? If you are, have you got all the sensors working? I can not get information from all the sensors on this MB (compared with what the BIOS shows) and some of the values that do show are wrong , some temp-sensor shows as negative (and my room is not THAT cold). Regards, I only recently bought a lowly A88XM-Plus and it also does not show up the sensors. I spent some time fighting with different settings in the kernel to get them recognised, but I had no success. The values that it does read seem to be incorrect too (like negative temperatures). $ sensors radeon-pci-0008 Adapter: PCI adapter temp1: -3.0°C (crit = +120.0°C, hyst = +90.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: N/A (crit = 95.09 W) k10temp-pci-00c3 Adapter: PCI adapter temp1: +0.0°C (high = +70.0°C) (crit = +70.0°C, hyst = +69.0°C) I am waiting for later kernels to see if this improves. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user][SOLVED] Computer does not boot
On Sat, 31 Jan 2015 15:40:37 -0700, Joseph wrote: Indeed grub was updated to grub-0.97-r14 genlop --list --date 3 days ago |grep grub Fri Jan 30 23:37:03 2015 sys-boot/grub-0.97-r14 Sat Jan 31 00:28:04 2015 sys-boot/grub-2.02_beta2-r3 Though all my other system were updated as well, and it didn't cause any problem, nor did I run grub-install on any of them. So I don't think emerging/updating grub package would cause any problem unless one run grub-install Well, something caused the problem. Why do you have two versions of GRUB installed? GRUB2 used t install files to /boot/grub2 but ISTR this changed recently to /boot/grub, so you could have the two packages causing some kind of conflict. -- Neil Bothwick Things which must be shipped together as a set, aren't. pgpd0jEb16iVj.pgp Description: OpenPGP digital signature
Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS
On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough, but a 'login shell', that is, one started by /bin/login, is setup with a different environment to a shell that's started by su (or by, say, cron). This is why a shell command or script may work for you when you're logged in, but not if you run it from cron. I'm sure other's can explain it more correctly and fully. This stuff is complex the first time you run into it. There are three kinds of shell depending on how you start them: login shell, interactive shell, and non-interactive shell. When you get a login prompt on the console and type your username/password, you get a login shell. bash will have done it's full complete start-up routine, will have read all the .bashrc and.profile files, and will set up your default environment just the way you like it. If you then type say vi at the command line, bash will launch it. vi does not try and set up a complete new environment for you - what would be the point? the shell already did it for you. So if you are at a bash prompt, and type bash, the running bash will start a new bash but won't do the whole startup routine for you (exactly the same way vi also doesn't try do it). The kind of bash shell is called an interactive shell, and it's different from a login shell. It's called interactive because you get a prompt, you can type stuff at the keyboard and get a response on the screen. A non-interactive shell is what a daemon/service like cron gets when it starts bash to run some program in the background. Almost all programming languages have an exec() function where you can run shell commands - these shells are also non-interactive. Why non-interactive? Because a daemon can't type stuff the keyboard, doesn't have a screen, and doesn't need $PATH set. It's a program, it doesn't need cute shortcuts. When you run su you might want an interactive shell, or you might want a login shell. Maybe you want to quickly run a command as the effective ID of the apache user, but don't need to change your entire environment. You run that as su Maybe you want to run su and log in as root to do a whole lot of maintenance. You decide you need root's full setup with PATH and everything else for this, so you run su - (the - means start a login shell) Well, OK, that's how it SUPPOSED to work. Usually it doesn't because distros decide to be clever. The files bash reads when it starts follow a convoluted path (see INVOCATION in man bash) and your average user gets confused. So distros helpfully make it easy for the user and rig it so that when you start an interactive shell, it goes and reads all the startup files anyway. So you don't get an interactive shell, you get a full-blown login shell! So how do you get an interactive shell in a distro like that? Well, errr, you don't. This explains the different behaviours of su vs su - between distros. Some, like SuSE have rigged it so there's no difference. Gentoo doesn't do that because a) Gentoo sticks closely to upstream and b) Gentoo users are not morons and don't need helpful distros dicking around with their shells. The topic of cron came up. A common issue is you run myscript.sh at the command line and it works. Run it in a cron as you and it doesn't work. Cron gets a non-interactive shell and $PATH is not set. So in cron, you must call it like this: /path/to/bin/myscript.sh In cron, it's always best to use fully-qualified paths to all files everywhere and always. Don't rely on startup profiles - those have always been to make life easier for human users, and were never intended to be used by system daemons. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Smart 'eclean packages'?
Do we have an eclean option that will consider how long ago a package was uninstalled? Last I checked this didn't exist yet. - Grant
Re: [gentoo-user] USE-flags description?
On 01-Feb-15 18:53, Markos Chandras wrote: where can I find description of *all* USE flags? I checked /usr/portage/profiles/use.desc and use.local.desc but still I can not find some... try /usr/portage/desc/cpu_flags_x86.desc You probably mean /usr/portage/profiles/desc/cpu_flags_x86.desc Thanks, I did not know about that desc sub-dir at all... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
On Sun, Feb 1, 2015 at 8:44 PM, Matthias Hanft m...@hanft.de wrote:
Hi,
I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86
told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3
When I did emerge -NDuv @world afterwards, there were some re-installs.
Everything was fine, except ffmpeg. emerge displays:
[ebuild R] media-video/ffmpeg-1.2.6-r1 USE=bzip2 encode examples
fontconfig gnutls hardcoded-tables iconv libcaca mp3 network truetype
vorbis x264 xvid zlib -X -aac -aacplus -alsa (-altivec)
-amr -bindist -bluray -cdio (-celt) -cpudetection -debug -doc -faac -fdk
-flite -frei0r -gsm -iec61883 -ieee1394 -jack -jpeg2k -libass -libsoxr
-libv4l -modplug (-neon) -openal -openssl -opus -oss
-pic -pulseaudio -rtmp -schroedinger -sdl -speex -static-libs {-test}
-theora -threads -twolame -v4l -vaapi -vdpau (-vis) -vpx (-3dnow%)
(-3dnowext%) (-avx%) (-mmx%) (-mmxext%) (-ssse3%)
CPU_FLAGS_X86=mmx%* mmxext%* -3dnow% -3dnowext% -avx% -ssse3%
FFTOOLS=aviocat cws2fws ffescape ffeval fourcc2pixfmt graph2dot ismindex
pktdumper qt-faststart trasher 0 KiB
and running emerge, after many lines, I get
[...]
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/mpeg12.c:1164:12:
warning: 'mpeg_decode_update_thread_context' defined but not used
[-Wunused-function]
static int mpeg_decode_update_thread_context(AVCodecContext *avctx, const
AVCodecContext *avctx_from)
^
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/common.mak:48:
recipe for target 'libavcodec/motion_est.o' failed
make: *** [libavcodec/motion_est.o] Error 1
make: *** Waiting for unfinished jobs
* ERROR: media-video/ffmpeg-1.2.6-r1::gentoo failed (compile phase):
* emake failed
Google can't find this special error message (yet?), so I believe I'm
the only one getting that error (and, hence, didn't want to file a bug
report instantly). Perhaps I set some weird use flags?
(No graphics installed on that machine, it's just a server which uses
command-line ffmpeg-converting, mainly sound files, not even videos.)
Thanks,
-Matt
What's the output of the command lines shown below on your system?
grep -Es 'ffmpeg|CPU' /etc/portage/*
equery -q u media-video/ffmpeg|grep cpu
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
On Sun, Feb 1, 2015 at 1:44 PM, Matthias Hanft m...@hanft.de wrote:
Hi,
I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86
told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3
When I did emerge -NDuv @world afterwards, there were some re-installs.
Everything was fine, except ffmpeg. emerge displays:
[ebuild R] media-video/ffmpeg-1.2.6-r1 USE=bzip2 encode examples
fontconfig gnutls hardcoded-tables iconv libcaca mp3 network truetype vorbis
x264 xvid zlib -X -aac -aacplus -alsa (-altivec)
-amr -bindist -bluray -cdio (-celt) -cpudetection -debug -doc -faac -fdk
-flite -frei0r -gsm -iec61883 -ieee1394 -jack -jpeg2k -libass -libsoxr
-libv4l -modplug (-neon) -openal -openssl -opus -oss
-pic -pulseaudio -rtmp -schroedinger -sdl -speex -static-libs {-test} -theora
-threads -twolame -v4l -vaapi -vdpau (-vis) -vpx (-3dnow%) (-3dnowext%)
(-avx%) (-mmx%) (-mmxext%) (-ssse3%)
CPU_FLAGS_X86=mmx%* mmxext%* -3dnow% -3dnowext% -avx% -ssse3%
FFTOOLS=aviocat cws2fws ffescape ffeval fourcc2pixfmt graph2dot ismindex
pktdumper qt-faststart trasher 0 KiB
and running emerge, after many lines, I get
[...]
You failed to include the real error message in your email. Look
further up in the log for a line containing error:.
Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS
On 01/02/2015 17:07, Peter Humphrey wrote: On Sunday 01 February 2015 14:17:04 Alan McKinnon wrote: On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough, but a 'login shell', that is, one started by /bin/login, is setup with a different environment to a shell that's started by su (or by, say, cron). This is why a shell command or script may work for you when you're logged in, but not if you run it from cron. I'm sure other's can explain it more correctly and fully. This stuff is complex the first time you run into it. ---8 [Much good advice] I think of it simply like this: su switches user, and that's all; su - gives you the full environment of the user you switch to. Indeed, that is the heart of it. Your version above is perfect for the tl;dr people :-) -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Ghost cyber threat
glsa-check is working fine, it was a slotted issue. Still curious about a way to check for statically linked packages. There is no simple solution for this... USE flags static and static-libs handle cases where there is a choice between static and non-static version. In theory it is possible that some package (like boot loader helper) can be linked only statically, thus you will not be able to find it by USE flag. Though probability of this is very low, and due to a special nature of such binaries (or libraries) attack surface is even less. So you may assume your system reasonable secure if: - all GLSAs are applied; - there are no preserved libraries left (all packages using vulnerable libs must be rebuilt); - all static binaries and libraries depending directly or indirectly on vulnerable packages are rebuild; - there are no running processes using deleted files (reboot is a brute, but effective way to do this, otherwise one should grep lsof -n output for (deleted) files in use). I think 'checkrestart' is a good substitute for this. - kernel should be updated to the latest version in branch if it is still supported, or upgrade to another branch, preferably LTS, if it is EOLed already. I have not seen GLSAs for kernel in ages, though old kernels definitely have serious security issues, and they may be far more serious than Ghost glibc bug. I didn't know that, thank you. - Grant
[gentoo-user] Cannot reinstall ffmpeg since new cpu flags
Hi,
I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86
told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3
When I did emerge -NDuv @world afterwards, there were some re-installs.
Everything was fine, except ffmpeg. emerge displays:
[ebuild R] media-video/ffmpeg-1.2.6-r1 USE=bzip2 encode examples
fontconfig gnutls hardcoded-tables iconv libcaca mp3 network truetype vorbis
x264 xvid zlib -X -aac -aacplus -alsa (-altivec)
-amr -bindist -bluray -cdio (-celt) -cpudetection -debug -doc -faac -fdk -flite
-frei0r -gsm -iec61883 -ieee1394 -jack -jpeg2k -libass -libsoxr -libv4l
-modplug (-neon) -openal -openssl -opus -oss
-pic -pulseaudio -rtmp -schroedinger -sdl -speex -static-libs {-test} -theora
-threads -twolame -v4l -vaapi -vdpau (-vis) -vpx (-3dnow%) (-3dnowext%) (-avx%)
(-mmx%) (-mmxext%) (-ssse3%)
CPU_FLAGS_X86=mmx%* mmxext%* -3dnow% -3dnowext% -avx% -ssse3%
FFTOOLS=aviocat cws2fws ffescape ffeval fourcc2pixfmt graph2dot ismindex
pktdumper qt-faststart trasher 0 KiB
and running emerge, after many lines, I get
[...]
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/mpeg12.c:1164:12:
warning: 'mpeg_decode_update_thread_context' defined but not used
[-Wunused-function]
static int mpeg_decode_update_thread_context(AVCodecContext *avctx, const
AVCodecContext *avctx_from)
^
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/common.mak:48:
recipe for target 'libavcodec/motion_est.o' failed
make: *** [libavcodec/motion_est.o] Error 1
make: *** Waiting for unfinished jobs
* ERROR: media-video/ffmpeg-1.2.6-r1::gentoo failed (compile phase):
* emake failed
Google can't find this special error message (yet?), so I believe I'm
the only one getting that error (and, hence, didn't want to file a bug
report instantly). Perhaps I set some weird use flags?
(No graphics installed on that machine, it's just a server which uses
command-line ffmpeg-converting, mainly sound files, not even videos.)
Thanks,
-Matt
Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS
On Sunday 01 February 2015 14:17:04 Alan McKinnon wrote: On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough, but a 'login shell', that is, one started by /bin/login, is setup with a different environment to a shell that's started by su (or by, say, cron). This is why a shell command or script may work for you when you're logged in, but not if you run it from cron. I'm sure other's can explain it more correctly and fully. This stuff is complex the first time you run into it. ---8 [Much good advice] I think of it simply like this: su switches user, and that's all; su - gives you the full environment of the user you switch to. -- Rgds Peter.
Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS
On Sunday 01 February 2015 18:00:23 Alan McKinnon wrote: On 01/02/2015 17:07, Peter Humphrey wrote: I think of it simply like this: su switches user, and that's all; su - gives you the full environment of the user you switch to. Indeed, that is the heart of it. Your version above is perfect for the tl;dr people :-) Well, it would be - look who suggested it! -- Rgds Peter.
Re: [gentoo-user] USE-flags description?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/01/2015 05:36 PM, Jarry wrote: Hi Gentoo-users, where can I find description of *all* USE flags? I checked /usr/portage/profiles/use.desc and use.local.desc but still I can not find some... cpuinfo2cpuflags-x86 suggested my CPU_FLAGS_X86 should be: aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 But I'd like to know what they means, but I could not find any description for aes and popcnt... Jarry try /usr/portage/desc/cpu_flags_x86.desc - -- Regards, Markos Chandras -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJUzmglXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGRDlGMzA4MUI2MzBDODQ4RDBGOEYxMjQx RjEwRUQ0QjgxREVCRjE5AAoJEB8Q7UuB3r8ZBcUH/RtFmb2/HEx8tnaI68RQdiaw arIHkUFmdiB0aIBm4bXFhVDEmuXXxuC+nK8jbRXPwbb9sBVKX44yRhmuZMqf5rMy i3kJbV2BciXvkpjEts5akzoJ4dYqoogu0ez4X4kdekZcMgT727OEb8fMXPaKj23i hRYZv90QrXeCKjGukRDdgxQx7Z4rEoHz+8F4BWIGv6SzqXDNYewNZys/CoyK35Tm bxOUxAXnX+RHPXl6obcNopR/0x3YwCg4yHvsRe0Wsa6hKuih+DasS2CosS+1UW1A oPO6h6Llacl7GyduI4a1so20Je9YN+G//OSvOtnV2Yrz8YCFLWO1K2p7fXzpqGU= =8lWs -END PGP SIGNATURE-
[gentoo-user] USE-flags description?
Hi Gentoo-users, where can I find description of *all* USE flags? I checked /usr/portage/profiles/use.desc and use.local.desc but still I can not find some... cpuinfo2cpuflags-x86 suggested my CPU_FLAGS_X86 should be: aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 But I'd like to know what they means, but I could not find any description for aes and popcnt... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] USE-flags description?
On Sun, Feb 1, 2015 at 7:36 PM, Jarry mr.ja...@gmail.com wrote: Hi Gentoo-users, where can I find description of *all* USE flags? I checked /usr/portage/profiles/use.desc and use.local.desc but still I can not find some... cpuinfo2cpuflags-x86 suggested my CPU_FLAGS_X86 should be: aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 But I'd like to know what they means, but I could not find any description for aes and popcnt... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted. quse -D aes popcnt local:aes:app-crypt/shishi: Enable AES encryption/checksum types. local:popcnt:dev-libs/marisa: Enable popcnt instruction support cpu_flags_x86.desc:aes: Enable support for Intel's AES instruction set (AES-NI) cpu_flags_x86.desc:popcnt: Enable popcnt instruction support ([abm] or [popcnt] in cpuinfo)
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
2015-02-01 21:44 GMT+03:00 Matthias Hanft m...@hanft.de:
Hi,
Hello
I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86
told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3
cpuinfo2cpuflags-x86 isn't telling to turn on all these flags
unconditionally but only those that are included in USE in
make.conf.
When I did emerge -NDuv @world afterwards, there were some re-installs.
Everything was fine, except ffmpeg. emerge displays:
[ebuild R] media-video/ffmpeg-1.2.6-r1 USE=bzip2 encode examples
fontconfig gnutls hardcoded-tables iconv libcaca mp3 network truetype vorbis
x264 xvid zlib -X -aac -aacplus -alsa (-altivec)
-amr -bindist -bluray -cdio (-celt) -cpudetection -debug -doc -faac -fdk
-flite -frei0r -gsm -iec61883 -ieee1394 -jack -jpeg2k -libass -libsoxr
-libv4l -modplug (-neon) -openal -openssl -opus -oss
-pic -pulseaudio -rtmp -schroedinger -sdl -speex -static-libs {-test} -theora
-threads -twolame -v4l -vaapi -vdpau (-vis) -vpx (-3dnow%) (-3dnowext%)
(-avx%) (-mmx%) (-mmxext%) (-ssse3%)
CPU_FLAGS_X86=mmx%* mmxext%* -3dnow% -3dnowext% -avx% -ssse3%
FFTOOLS=aviocat cws2fws ffescape ffeval fourcc2pixfmt graph2dot ismindex
pktdumper qt-faststart trasher 0 KiB
and running emerge, after many lines, I get
[...]
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/mpeg12.c:1164:12:
warning: 'mpeg_decode_update_thread_context' defined but not used
[-Wunused-function]
static int mpeg_decode_update_thread_context(AVCodecContext *avctx, const
AVCodecContext *avctx_from)
^
/var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/common.mak:48:
recipe for target 'libavcodec/motion_est.o' failed
make: *** [libavcodec/motion_est.o] Error 1
make: *** Waiting for unfinished jobs
* ERROR: media-video/ffmpeg-1.2.6-r1::gentoo failed (compile phase):
* emake failed
Google can't find this special error message (yet?), so I believe I'm
the only one getting that error (and, hence, didn't want to file a bug
report instantly). Perhaps I set some weird use flags?
(No graphics installed on that machine, it's just a server which uses
command-line ffmpeg-converting, mainly sound files, not even videos.)
Thanks,
-Matt
--
Regards,
Alex
Re: [gentoo-user] cannot emerge dev-qt/qtcore, undefined reference to `__stack_chk_fail'
On 01/13/2015 06:51 PM, Mike Gilbert wrote: On Mon, Jan 12, 2015 at 12:39 AM, Justin Findlay jfind...@gmail.com wrote: I am having a problem emerging dev-qt/qtcore that I have been unable to solve myself yet. The system is amd64 and I have ABI_X86='32 64' so that pipelight will work. I think the error is coming from somewhere within glibc's multilib compatability. You should file a bug. ^_^ Here's the bug in question (I didn't file it, though) in the case that someone else finds this thread first: https://bugs.gentoo.org/show_bug.cgi?id=503500 There are some linker flag suggestions there that I'll try. If I have success I'll update here what I've done. Justin
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Am Sonntag, 01.02.2015 um 14:41 schrieb walt w41...@gmail.com: On 02/01/2015 01:18 PM, walt wrote: I was happy with nfs3 until it stopped working for reasons I still don't understand :( Well, nfs3 still works, but only after failing on the first attempt: #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely until I hit Ctrl-C. If I then repeat the same command immediately the mount succeeds. This is the mysterious nfs black magic I've run into many times over the years and makes me dread nfs updates. Here is the postinstall info from the update to nfs-utils-1.3.1-r1. Maybe you run into that. If you use OpenRC, the nfsmount service has been replaced with nfsclient. If you were using nfsmount, please add nfsclient and netmount to the same runlevel as nfsmount. Regards wabe
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
On Mon, 2 Feb 2015 00:32:34 +0100, waben...@gmail.com wrote: #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely until I hit Ctrl-C. If I then repeat the same command immediately the mount succeeds. This is the mysterious nfs black magic I've run into many times over the years and makes me dread nfs updates. Here is the postinstall info from the update to nfs-utils-1.3.1-r1. Maybe you run into that. If you use OpenRC, the nfsmount service has been replaced with nfsclient. If you were using nfsmount, please add nfsclient and netmount to the same runlevel as nfsmount. It's got nothing to do with the init system used. That message tells you what to do to try to mount the NFS shares when you boot, but unless you have suitable mount options or kernel config, that attempt will fail. -- Neil Bothwick Why is the word abbreviation so long? pgpnhFLkIbNZz.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
Mike Gilbert wrote: You failed to include the real error message in your email. Look further up in the log for a line containing error:. Ah, I actually missed that: /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/x86/mathops.h:94:1: error: 'asm' operand has impossible constrain ts (12 times) Kernel 3.17.7, BTW. Last compilation is a long time ago (maybe 3.12 or so) -Matt
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
02.02.2015 0:24 пользователь Mike Gilbert flop...@gentoo.org написал: On Sun, Feb 1, 2015 at 2:13 PM, Alexey Mishustin shum...@shumkar.ru wrote: 2015-02-01 21:44 GMT+03:00 Matthias Hanft m...@hanft.de: Hi, Hello I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86 told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3 cpuinfo2cpuflags-x86 isn't telling to turn on all these flags unconditionally but only those that are included in USE in make.conf. Where did you get that silly idea? cpuinfo2cpuflags-x86 tells you exactly what to put in make.conf based on your host CPU. Ok. It tells me what _could_ be put in the new variable in make.conf. But make.conf existed before this new variable. And what flags existed in it - it's a separate question. If one wants to keep 'status quo', he should only duplicate those cpu flags whis were in USE to this new variable. If some cpu flag wasn't in USE, he shouldn't add it to the new variable. -- Regards, Alex
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
whis were in USE which were in USE
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
I wrote: /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/x86/mathops.h:94:1: error: 'asm' operand has impossible constraints The piece of source code at that point: #if HAVE_CMOV #define COPY3_IF_LT(x, y, a, b, c, d)\ __asm__ volatile(\ cmpl %0, %3 \n\t\ cmovl %3, %0 \n\t\ cmovl %4, %1 \n\t\ cmovl %5, %2 \n\t\ : +r (x), +r (a), +r (c)\ : r (y), r (b), r (d)\ ); #endif and the emerge messages: [...] In file included from /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/mathops.h:45:0, from /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/motion_est.c:35: /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/x86/mathops.h:94:1: error: 'asm' operand has impossible constraints __asm__ volatile(\ ^ /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/motion_est.c:378:5: note: in expansion of macro 'COPY3_IF_LT' COPY3_IF_LT(dminh, d, dx, x, dy, y)\ ^ /var/tmp/portage/media-video/ffmpeg-1.2.6-r1/work/ffmpeg-1.2.6/libavcodec/motion_est.c:440:17: note: in expansion of macro 'CHECK_SAD_HALF_MV' CHECK_SAD_HALF_MV(xy2, +1, -1) ^ [repeated 12 times] -Matt
[gentoo-user] [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Everybody's favoritest cuddly FOSS personality Theo de Raadt is quoted in Wikipedia as saying: NFS4 is not on our roadmap. It's a horribly bloated protocol that they keep adding crap to. The latest nfs-utils package demonstrates why he's annoyed with NFS4: This morning I got this when mounting an nfs share that's been working for many months: #mount.nfs -v a6:/usr/portage /usr/portage/ mount.nfs: timeout set for Sun Feb 1 13:09:39 2015 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.84,clientaddr=192.168.1.84' mount.nfs: mount(2): Invalid argument mount.nfs: an incorrect mount option was specified Note the vers=4.2, which is brand new behavior. My kernel doesn't have any config option for nfs-4.2 because I've never enabled nfs-4.1 and the 4.2 option is invisible in menuconfig without it. Who knew? So, you either need to enable nfs-4.1 *and* nfs-4.2 in your kernel, or start using the nfsvers=4 mount option in fstab. Anyone got an opinion on the need for nfs-4.2? Is it better, or just newer? I was happy with nfs3 until it stopped working for reasons I still don't understand :(
Re: [gentoo-user] cannot emerge dev-qt/qtcore, undefined reference to `__stack_chk_fail'
On 02/01/2015 01:44 PM, Justin Findlay wrote: On 01/13/2015 06:51 PM, Mike Gilbert wrote: On Mon, Jan 12, 2015 at 12:39 AM, Justin Findlay jfind...@gmail.com wrote: I am having a problem emerging dev-qt/qtcore that I have been unable to solve myself yet. The system is amd64 and I have ABI_X86='32 64' so that pipelight will work. I think the error is coming from somewhere within glibc's multilib compatability. You should file a bug. ^_^ Here's the bug in question (I didn't file it, though) in the case that someone else finds this thread first: https://bugs.gentoo.org/show_bug.cgi?id=503500 There are some linker flag suggestions there that I'll try. If I have success I'll update here what I've done. This worked for me: LDFLAGS=-Wl,-O1 -Wl,--no-as-needed emerge -v1 qtcore Justin
[gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
On 02/01/2015 01:18 PM, walt wrote: I was happy with nfs3 until it stopped working for reasons I still don't understand :( Well, nfs3 still works, but only after failing on the first attempt: #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely until I hit Ctrl-C. If I then repeat the same command immediately the mount succeeds. This is the mysterious nfs black magic I've run into many times over the years and makes me dread nfs updates. I'm going to remove nfs4* support completely from the kernel and nfs-utils now just as a voodoo trial (on a vbox guest, that is :)
Re: [gentoo-user] Cannot reinstall ffmpeg since new cpu flags
On Sun, Feb 1, 2015 at 2:13 PM, Alexey Mishustin shum...@shumkar.ru wrote: 2015-02-01 21:44 GMT+03:00 Matthias Hanft m...@hanft.de: Hi, Hello I have installed the new CPU_FLAGS_X86, as cpuinfo2cpuflags-x86 told me: CPU_FLAGS_X86=mmx mmxext sse sse2 sse3 cpuinfo2cpuflags-x86 isn't telling to turn on all these flags unconditionally but only those that are included in USE in make.conf. Where did you get that silly idea? cpuinfo2cpuflags-x86 tells you exactly what to put in make.conf based on your host CPU.
[gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
On 02/01/2015 03:32 PM, waben...@gmail.com wrote: Am Sonntag, 01.02.2015 um 14:41 schrieb walt w41...@gmail.com: On 02/01/2015 01:18 PM, walt wrote: I was happy with nfs3 until it stopped working for reasons I still don't understand :( Well, nfs3 still works, but only after failing on the first attempt: #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely until I hit Ctrl-C. If I then repeat the same command immediately the mount succeeds. This is the mysterious nfs black magic I've run into many times over the years and makes me dread nfs updates. Here is the postinstall info from the update to nfs-utils-1.3.1-r1. Maybe you run into that. If you use OpenRC, the nfsmount service has been replaced with nfsclient. If you were using nfsmount, please add nfsclient and netmount to the same runlevel as nfsmount. Thanks wabe. I forgot to mention that I use systemd now, and I've had to work out a few problems with nfs over past months because our gentoo systemd scripts are lagging a bit behind upstream, which is not surprising. For example, I had to add the rpcbind.service to the multi-user systemd target because even nfs3 seems to need it. (I knew when I switched to systemd I was volunteering for some extra problems, but I don't regret it. Yet ;) As I said in my earlier post, I've now disabled nfs4 in both kernel and nfs-utils on all my machines, with the same result: the first attempt to mount an nfs3 share hangs indefinitely, but if I kill the mount process and repeat it immediately, the mount succeeds. I'd love to know if anyone else can reproduce this problem with nfs3 on either OpenRC or systemd. Thanks!
Re: [gentoo-user] Ghost cyber threat
Do they need telnet or ssh access, Not telnet shell but this could be triggered with telnet/nc or even nmap, hping, or tcpreplay - all of which could send an arbitrary payload to tcp or udp ports. For clarity, its probably best to specify if we're talking about client or server end. The original question was whether telnet or ssh access was required, that is, does the attacker require access to the telnetd or sshd. In GHOSTs case the answer is no, but if the attacker does have access and an account, all they need to do is execute a local binary that uses the older gethostbyname function rather than the newer getaddrinfo function, and pass it a long hostname to lookup. However, in this case its considered a local attack. The attackers tool of choice (client end) will depend on personal preference and the network service that provides the access for the attack.
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Am Sonntag, 01.02.2015 um 16:31 schrieb walt w41...@gmail.com: For example, I had to add the rpcbind.service to the multi-user systemd target because even nfs3 seems to need it. (I knew when I I never used systemd, so I don't know if adding the rpcbind.service to the multi-user systemd target is also starting rpc.statd. AFAIK this process is also necessary for a proper working nfs. This is the rpc stuff running on my nfs client system: [rpciod] /sbin/rpcbind /sbin/rpc.statd --no-notify Regards wabe
[gentoo-user] libav/ffmpeg handling via gloabl USE
Hi, this is *NO* complaint/critsim neither implicitely nor explicitely! I am just curious... ;) What is the (technical) reason for makeing libav the default instead of ffmpeg? Best regards, Meino
[gentoo-user] Re: libav/ffmpeg handling via gloabl USE
On Mon, 2 Feb 2015 04:45:34 +0100 meino.cra...@gmx.de wrote: What is the (technical) reason for makeing libav the default instead of ffmpeg? http://blogs.gentoo.org/scarabeus/2013/01/15/libav-going-to-be-default-provider-for-your-codec-experience/ has some info about the decision, though I'm not sure it really answers your question.
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Am Sonntag, 01.02.2015 um 16:31 schrieb walt w41...@gmail.com: Thanks wabe. I forgot to mention that I use systemd now, and I've had to work out a few problems with nfs over past months because our gentoo systemd scripts are lagging a bit behind upstream, which is not surprising. For example, I had to add the rpcbind.service to the multi-user systemd target because even nfs3 seems to need it. (I knew when I switched to systemd I was volunteering for some extra problems, but I don't regret it. Yet ;) I'm still on OpenRC and I don't wanna switch to systemd for some reasons. As I said in my earlier post, I've now disabled nfs4 in both kernel and nfs-utils on all my machines, with the same result: the first attempt to mount an nfs3 share hangs indefinitely, but if I kill the mount process and repeat it immediately, the mount succeeds. I also have no nfs4 support in my kernel. Here is my kernel config for the NFS stuff: CONFIG_NFS_FS=y CONFIG_NFS_V2=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set # CONFIG_NFS_SWAP is not set # CONFIG_NFSD is not set CONFIG_NFS_COMMON=y I'd love to know if anyone else can reproduce this problem with nfs3 on either OpenRC or systemd. I'm using nfs3 since many years but I never had this problem. I'm sorry that I can't help you. Regards wabe
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
Am Montag, 02.02.2015 um 00:12 schrieb Neil Bothwick n...@digimed.co.uk: On Mon, 2 Feb 2015 00:32:34 +0100, waben...@gmail.com wrote: #mount.nfs a6://usr/portage /usr/portage -o nfsvers=3 hangs indefinitely until I hit Ctrl-C. If I then repeat the same command immediately the mount succeeds. This is the mysterious nfs black magic I've run into many times over the years and makes me dread nfs updates. Here is the postinstall info from the update to nfs-utils-1.3.1-r1. Maybe you run into that. If you use OpenRC, the nfsmount service has been replaced with nfsclient. If you were using nfsmount, please add nfsclient and netmount to the same runlevel as nfsmount. It's got nothing to do with the init system used. That message tells you what to do to try to mount the NFS shares when you boot, but unless you have suitable mount options or kernel config, that attempt will fail. Maybe I don't exactly understand what you are trying to tell me because of my lousy English. Of course you also need the right mount options and kernel config. But since nfsmount doesn't exist anymore, the rpc stuff isn't started by the OpenRC init system until you add nfsclient to the right runlevel. Regards wabe
Re: [gentoo-user] Re: [NOTE] New default behavior in latest nfs-utils (1.3.2-r1)
On Sun, Feb 1, 2015 at 8:35 PM, waben...@gmail.com wrote: Am Sonntag, 01.02.2015 um 16:31 schrieb walt w41...@gmail.com: For example, I had to add the rpcbind.service to the multi-user systemd target because even nfs3 seems to need it. (I knew when I I never used systemd, so I don't know if adding the rpcbind.service to the multi-user systemd target is also starting rpc.statd. AFAIK this process is also necessary for a proper working nfs. I believe that starting nfs-client.service or nfs-server.service starts everything needed EXCEPT rpcbind. I'd have to re-trace everything, but I think that there are multiple packages involved here and the upstream units don't include the necessary dependencies (I think nfs-server depends on rpcbind.target, but nothing in the target forces the rpcbind service to run - going from memory here). I believe this is only an issue for serving nfs. If you're just using the client then you're fine just starting nfs-client, and systemd will start that if it mounts the nfs share (such as from fstab). -- Rich
