[gentoo-user] webkit-gtk-2.4.8 fails to compile
I seem to be hitting this bug: https://bugs.gentoo.org/show_bug.cgi?id=513386 webkit-gtk fails: GNUmakefile:40431: recipe for target 'Programs/GtkLauncher' failed make[1]: *** [Programs/GtkLauncher] Error 1 make[1]: *** Waiting for unfinished jobs Source/WebKit/gtk/webkit/webkitversion.h:37: Warning: WebKit: symbol='WEBKITGTK_API_VERSION': Unknown namespace for symbol 'WEBKITGTK_API_VERSION' /var/tmp/portage/net-libs/webkit- gtk-2.4.8/work/webkitgtk-2.4.8/.libs/libwebkitgtk-3.0.so: undefined reference to `_ZNSt6chrono3_V212steady_clock3nowEv@GLIBCXX_3.4.19' /var/tmp/portage/net-libs/webkit- gtk-2.4.8/work/webkitgtk-2.4.8/.libs/libjavascriptcoregtk-3.0.so: undefined reference to `_ZNSt6chrono3_V212system_clock3nowEv@GLIBCXX_3.4.19' collect2: error: ld returned 1 exit status linking of temporary binary failed: Command '['/bin/sh', './libtool', '-- mode=link', '--tag=CC', '--silent', 'i686-pc-linux-gnu-gcc', '-o', '/var/tmp/portage/net-libs/webkit-gtk-2.4.8/work/webkitgtk-2.4.8/tmp- introspectdaQWqM/WebKit-3.0', '-export-dynamic', '-O2', '-march=i686', '- pipe', '-pthread', '-std=c99', '-Wno-deprecated-declarations', '-Wl,-O1', '- Wl,--as-needed', '-Wl,--no-keep-memory', '-Wl,--reduce-memory-overheads', '- Wl,--no-demangle', '/var/tmp/portage/net-libs/webkit- gtk-2.4.8/work/webkitgtk-2.4.8/tmp-introspectdaQWqM/WebKit-3.0.o', '-L.', '- lwebkitgtk-3.0', '-ljavascriptcoregtk-3.0', '-Wl,--export-dynamic', '- lgmodule-2.0', '-pthread', '-lgtk-3', '-lgdk-3', '-lpangocairo-1.0', '- lpango-1.0', '-latk-1.0', '-lcairo-gobject', '-lcairo', '-lgdk_pixbuf-2.0', '- lsoup-2.4', '-lgio-2.0', '-lgobject-2.0', '-lglib-2.0']' returned non-zero exit status 1 GNUmakefile:82193: recipe for target 'WebKit-3.0.gir' failed make[1]: *** [WebKit-3.0.gir] Error 1 If I'm reading the bug correctly, it seems to be caused there by having gcc 4.8 installed and having 4.7 active. From comment #30: quote gcc ebuild adds /etc/ld.so.conf.d/05gcc-i686-pc-linux-gnu.conf entries, sorted by version. During compilation, API from *active* version is used. During linking, ABI from the first *listed* version is used. If those two disagree, like it's the case here for c++11, you'll getting various funny results. /quote That's not the case on my system. I only have version 4.8 installed root@kushiel ~ # gcc-config -l [1] i686-pc-linux-gnu-4.8.3 * root@kushiel ~ # root@kushiel ~ # cat /etc/ld.so.conf.d/05gcc-i686-pc-linux-gnu.conf /usr/lib/gcc/i686-pc-linux-gnu/4.8.3 root@kushiel ~ # There's only one line in the above file, so it should be compiling and linking from the same source. I've reemerged libtool, reemerged glibc and run revdep- rebuild. The two packages built with no errors and revdep comes up with nothing required. Emerging @preserved-rebuilds tries to rebuild webkit-gtk and fails. The full build log for webkit-gtk is WAY to big to post here but I've included emerge --info and -pvq below. Any help or suggestions greatly appreciated. root@kushiel ~ # emerge --info '=net-libs/webkit-gtk-2.4.8::gentoo' Portage 2.2.14 (python 2.7.9-final-0, default/linux/x86/13.0/desktop/kde, gcc-4.8.3, glibc-2.19-r1, 3.18.9-gentoo i686) = System Settings = System uname: Linux-3.18.9-gentoo-i686-Intel-R-_Core-TM- _i7-2600K_CPU_@_3.40GHz-with-gentoo-2.2 KiB Mem:16609028 total, 12465696 free KiB Swap:2097148 total, 2097092 free Timestamp of tree: Thu, 26 Mar 2015 05:30:01 + ld GNU ld (Gentoo 2.24 p1.4) 2.24 app-shells/bash: 4.2_p53 dev-java/java-config: 2.2.0 dev-lang/perl:5.20.1-r4 dev-lang/python: 2.7.9-r1, 3.3.5-r1, 3.4.1 dev-util/cmake: 2.8.12.2-r1 dev-util/pkgconfig: 0.28-r1 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.13.11 sys-apps/sandbox: 2.6-r1
[gentoo-user] Re: xfreerdp clipboard not working
On 2015-03-26, Mike Gilbert flop...@gentoo.org wrote: On Thu, Mar 26, 2015 at 11:34 AM, Grant Edwards grant.b.edwa...@gmail.com wrote: On 2015-03-26, Grant Edwards grant.b.edwa...@gmail.com wrote: I'm going to unamsk xfreerdp 1.2.0 and see if it works any better. 1.2.0 is unusable. Personally, I maintain and use the live ebuild (freerdp-.1) more than the others. I use it on an almost daily basis. It might be worth giving that a shot. If it works better for you, I can create a new snapshot to add to ~arch. Thanks for suggesting the git ebuild (I hadn't noticed one was available). It looks like it's working well. Clipboard features work consistently, and I see none of the lockup or network traffic problems I saw with 1.2.0. -- Grant Edwards grant.b.edwardsYow! Hand me a pair of at leather pants and a CASIO gmail.comkeyboard -- I'm living for today!
[gentoo-user] [distcc redux] A working distcc setup
First of all, thanks to everybody who answered my questions, and
helped me get it working. Now for the setup. This is a home LAN, so I
don't bother with ssh tunneling, etc, which will be necessary if you're
going over untrusted links, e.g. the public internet.
* The host, IP address 192.168.123.251, is an over 7 year old Dell
Dimension 530 with a Core Duo, running 64-bit Gentoo. It will
compile for the client.
* The client, IP address 192.168.123.253, is an ancient Acer netbook,
with an Atom CPU so old that it only runs 32-bit mode.
*** On the host ***
=
* emerge crossdev
* build a toolchain that can compile for the client's architecture...
crossdev -S -t client's CHOST
You need to know what the CHOST variable is in the client's make.conf.
e.g. on my netbook CHOST=i686-pc-linux-gnu so the command would be
crossdev -S -t i686-pc-linux-gnu
The -S tells crossdev to build the latest stable gcc and utilities
version. The default (without the -S) is to build the absolute latest
version available, as if gcc and utilities were keyworded. Note that
the gcc versions must be essentially the same on the client and the
server crossdev toolchain. E.g. for gcc-a.b.c, the 3rd part (the
revison # c) can differ. But if either the major or minor version
portions differ, you are guaranteed to have problems.
* emerge distcc
* edit the DISTCCD_OPTS variable to indicate allowed clients. On my
host machine, it's...
DISTCCD_OPTS=--port 3632 --log-level notice --log-file /var/log/distccd.log -N
15 --allow 192.168.123.253
Notes;
- The default port is 3632
- N is the nice level.
- you can allow multiple addresses, e.g.
--allow 192.168.123.253 --allow 169.254.0.1 etc.
* start up the distccd daemon with the command
/etc/init.d/distccd start
* optionally set it to come up whenever the machine boots up
rc-update add distccd default
*** On the client ***
=
specify host(s) in /etc/distcc/hosts e.g. in my case
192.168.123.251/6,lzo,cpp
Notes;
- you can have multiple entries, using a space as the separator. The
leftmost entry will be the preferred host, and any additional entries
will have descending priority.
- the /6 is not a CIDR number. It specifies how many simultaneous
jobs to send to that server. The optimal number will vary depending
on how powerful the server is, and whether it's also being used as a
desktop, etc.
- The lzo entry specifies lzo compression. It is necessary for pump
mode. You will want pump mode.
- The cpp entry is also necessary for pump mode. You will want pump
mode.
If you have distcc distcc-pump in FEATURES in make.conf, the
emerge command will transparently invoke pump mode. Without them,
builds will be done locally. Does that mean you have to edit your
make.conf file each time you switch between local and distcc builds?
NO. Remember how you can temporarily modify the USE variable for an
emerge like so...
USE=foo emerge bar
...the exact same method works for the FEATURES variable.
* do *NOT* put distcc distcc-pump directly into FEATURES in make.conf
* make an executable script /root/bin/xmerge with 2 lines...
#!/bin/bash
FEATURES=distcc distcc-pump emerge ${*}
Now compare the outputs of...
emerge --info | grep ^FEATURES
xmerge --info | grep ^FEATURES
aa1 portage # emerge --info | grep ^FEATURES
FEATURES=assume-digests binpkg-logs distlocks ebuild-locks fixlafiles
merge-sync news parallel-fetch protect-owned sandbox sfperms strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync
aa1 portage # xmerge --info | grep ^FEATURES
FEATURES=assume-digests binpkg-logs distcc distcc-pump distlocks ebuild-locks
fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync
Your FEATURES options will probably differ from mine. The important
point is that when launched from the xmerge script, emerge sees the
options distcc distcc-pump in FEATURES, and transparently uses distcc.
When launched directly from the command line, emerge won't see this, and
will therefore build locally. In the above example, only the parameter
--info was passed to xmerge. But you can pass any legal energe
parameters to xmerge, e.g.
xmerge --changed-use --deep --update @world
--
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications
[gentoo-user] Re: Please explain X fonts?
On 03/26/2015 07:15 PM, Walter Dnes wrote: snip all questions I can't answer When I do a control-right-click on an xterm to manipulate fonts, the xterm crashes. I had the same problem once. IIRC, strace showed me that xterm was trying to load the default font but there was no value set for default. Somehow I managed to set the default font, but I can't remember how it did it. Maybe someone else can supply details?
Re: [gentoo-user] Overlay for wickr
On Friday 20 Mar 2015 19:59:12 Matti Nykyri wrote:
On Mon, Mar 16, 2015 at 08:49:18AM +0200, Matti Nykyri wrote:
On Mar 16, 2015, at 8:28, Mick michaelkintz...@gmail.com wrote:
I've looked at zugaina too and didn't find anything, hence I asked
here. I'll file a bug at some point, unless anyone beats me to it.
Writing an ebuild to do the install is like 5 min job :) I'm now in a
train only with a phone, but when i get home i can write you one.
Just my opinion... I would never ever trust non open source encryption
software. Everyting published isn't true :)
Ok... No I'm happily back home after circling around the World ;)
Doing the ebuild was a bit more tricky... The program has bad bugs :(
The wickr executable is linked against icu-52, but in the archive the
libraries are libicui18n-53 - had to make symbolic link Also the
symboltable in wickr had to be altered.
And the ebuild:
- Clip ---
EAPI=5
inherit eutils
DESCRIPTION=Wickr Top-Secret Messenger
HOMEPAGE=https://www.wickr.com/downloads/;
SRC_URI=x86? ( http://mywickr.info/download.php?p=332 - ${P}_i386.deb )
amd64? ( http://mywickr.info/download.php?p=364 - ${P}_amd64.deb )
LICENCE=
SLOT=0
KEYWORDS=~amd64 ~x86
IUSE=x86 amd64
RDEPEND=sys-libs/glibc
sys-devel/gcc
sys-apps/util-linux
media-sound/pulseaudio
src_unpack() {
mkdir ${S}
cd ${S}
ar x ${DISTDIR}/${A}
}
src_install() {
cd ${D}
tar --same-owner --preserve-permissions -xof ${S}/data.tar.xz
if use x86 ; then
MY_OFFSET=332312
elif use amd64 ; then
MY_OFFSET=393763
fi
echo 3 | dd of=usr/bin/wickr bs=1 count=1 seek=${MY_OFFSET}
conv=notrunc
cd usr/lib/wickr
ln -s libicui18n.so.53 libicui18n.so.52
}
- Clip ---
After correcting those the software segfaults in libQt5core.so that is
provided in the archive... So you probably need Qt5 installed.
Thanks! I will try it when I install qt5.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
[gentoo-user] Re: webkit-gtk-2.4.8 fails to compile
On 03/27/2015 02:56 AM, ddjones wrote: I seem to be hitting this bug: https://bugs.gentoo.org/show_bug.cgi?id=513386 webkit-gtk fails: gtk-2.4.8/work/webkitgtk-2.4.8/.libs/libwebkitgtk-3.0.so: undefined reference to `_ZNSt6chrono3_V212steady_clock3nowEv@GLIBCXX_3.4.19' I don't know if you understand the concepts discussed in that bug report, but this this is basic idea: You see that the undefined symbol includes the string GLIBCXX. From this you can tell that the program uses the well-known c++ standard library, which happens to be installed separately by each version of gcc you have on your computer. The error you are seeing is caused by using a different version of gcc to compile webkit-gtk than you used to compile some other package that webkit-gtk depends on. The tedious but necessary fix is to find every package on your computer that needs libstdc++ and then recompile all of them with the same version of gcc. Yup, boring.
Re: [gentoo-user] How recent is this Gentoo documentation?
150328 meino.cra...@gmx.de wrote: I am on the way to configure linux-3.19.3 (vanilla) and want to start with kexec. On the internet via google I found this (first hit): https://forums.gentoo.org/viewtopic-t-294644-start-0.html Is this still up to date and useable? That dates from 2005 . Google offers me https://wiki.archlinux.org/index.php/Kexec (140915) http://www.gossamer-threads.com/lists/gentoo/user/294573 (this list 141126). -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] How recent is this Gentoo documentation?
Rich Freeman ri...@gentoo.org [15-03-28 03:56]: On Fri, Mar 27, 2015 at 10:34 PM, Philip Webb purs...@ca.inter.net wrote: 150328 meino.cra...@gmx.de wrote: I am on the way to configure linux-3.19.3 (vanilla) and want to start with kexec. On the internet via google I found this (first hit): https://forums.gentoo.org/viewtopic-t-294644-start-0.html Is this still up to date and useable? That dates from 2005 . Google offers me https://wiki.archlinux.org/index.php/Kexec (140915) http://www.gossamer-threads.com/lists/gentoo/user/294573 (this list 141126). In general kexec itself hasn't really changed much recently. You load a kernel/etc, and then exec it. What may very well have changed is tools used by openrc and such to launch it. That guide obviously doesn't explain how to do it with systemd either. I'm pretty sure you just have to load your kernel at some point and then run systemctl kexec to shutdown and kexec the new kernel. I should probably do that more often. What I haven't gotten to work lately is a crash kernel. With all my btrfs panics of late it would sure be handy for troubleshooting... -- Rich Ok, since there are many ways to do it and documents such old, that are simply wrong (why not to remove that stuff): If possible: I want to reboot a new kernel with kexec and without systemd (I am using openrc). What document is recommended to read and to use? Thanks fpr any help in advance! Best regards, Meino
[gentoo-user] How recent is this Gentoo documentation?
Hi, I am on the way to configure linux-3.19.3. (vanilla) and want to start with kexec. On the internet via google I found this (first hit): https://forums.gentoo.org/viewtopic-t-294644-start-0.html I read a few lines and have a question: Is this still up to date and useable? Best regards, Meino
Re: [gentoo-user] How recent is this Gentoo documentation?
On Fri, Mar 27, 2015 at 10:34 PM, Philip Webb purs...@ca.inter.net wrote: 150328 meino.cra...@gmx.de wrote: I am on the way to configure linux-3.19.3 (vanilla) and want to start with kexec. On the internet via google I found this (first hit): https://forums.gentoo.org/viewtopic-t-294644-start-0.html Is this still up to date and useable? That dates from 2005 . Google offers me https://wiki.archlinux.org/index.php/Kexec (140915) http://www.gossamer-threads.com/lists/gentoo/user/294573 (this list 141126). In general kexec itself hasn't really changed much recently. You load a kernel/etc, and then exec it. What may very well have changed is tools used by openrc and such to launch it. That guide obviously doesn't explain how to do it with systemd either. I'm pretty sure you just have to load your kernel at some point and then run systemctl kexec to shutdown and kexec the new kernel. I should probably do that more often. What I haven't gotten to work lately is a crash kernel. With all my btrfs panics of late it would sure be handy for troubleshooting... -- Rich
