[gentoo-user] mesa-10.3.7-r1 S3TC option
After I updated mesa to 10.3.7-r1, I was provided with this message: Messages generated by process 2287 on 2015-02-19 20:32:50 GMT for package media-libs/mesa-10.3.7-r1: LOG: postinst Note that in order to have full S3TC support, it is necessary to install media-libs/libtxc_dxtn as well. This may be necessary to get nice textures in some apps, and some others even require this to run. I couldn't see a USE flag, which is what I was expecting for enabling S3TC support and pulling in media-libs/libtxc_dxtn as a dependency. So I emerged media-libs/libtxc_dxtn manually. Is this how it is meant to be, or is there a USE flag missing from mesa? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] distcc implementation failure
On Fri, 20 Feb 2015 17:09:02 -0800 Daniel Frey wrote:
Well, I decided to try distcc once again and set up a few machine to do so.
I have set the -march directive on each machine to its own (and not
native), and set up the accesses. It seems to work on most packages.
However, I've found that there's some packages that just don't work:
-mysql/mariadb errors out can't find synch.h
-ffmpeg errors out can't find windows.h
-xbmc and mythtv both failed as well, but this may be because of the
above two errors.
Looks like you are using pump mode. Disable it and use normal
distcc.
These are repeatable errors and they occur on all three of my mythtv
frontends.
Now, I've disabled distcc on one machine completely and above packages
compile fine, so it must be something to do with distcc. So that's what
I'm doing for the time being.
However, this poses another question: is there a way to tell portage to
NOT use distcc for certain packages? Rather than manually disabling it.
Yes, there is. Create a file /etc/portage/env/no-distcc.conf with
the following content:
FEATURES=${FEATURES} -distcc
and add the following entry in /etc/portage/package.env (create
file, if it doesn't exist):
category1/foo no-distcc.conf
category2/bar no-distcc.conf
Best regards,
Andrew Savchenko
pgpfH5oQn8S7W.pgp
Description: PGP signature
Re: [gentoo-user] distcc implementation failure
On 02/20/2015 05:19 PM, Andrew Savchenko wrote:
Looks like you are using pump mode. Disable it and use normal
distcc.
Yes, I read about how it works and enabled it. Of course I didn't think
of that when these errors happened. I'll try disabling that shortly.
Yes, there is. Create a file /etc/portage/env/no-distcc.conf with
the following content:
FEATURES=${FEATURES} -distcc
and add the following entry in /etc/portage/package.env (create
file, if it doesn't exist):
category1/foo no-distcc.conf
category2/bar no-distcc.conf
Good to know, thanks. Hopefully I won't need it after disabling distcc-pump.
Dan
[gentoo-user] distcc implementation failure
Well, I decided to try distcc once again and set up a few machine to do so. I have set the -march directive on each machine to its own (and not native), and set up the accesses. It seems to work on most packages. However, I've found that there's some packages that just don't work: -mysql/mariadb errors out can't find synch.h -ffmpeg errors out can't find windows.h -xbmc and mythtv both failed as well, but this may be because of the above two errors. These are repeatable errors and they occur on all three of my mythtv frontends. Now, I've disabled distcc on one machine completely and above packages compile fine, so it must be something to do with distcc. So that's what I'm doing for the time being. However, this poses another question: is there a way to tell portage to NOT use distcc for certain packages? Rather than manually disabling it. Dan
Re: [gentoo-user] compiling via distcc
On Wed, 11 Feb 2015 17:19:22 -0600 Jeff Smelser wrote:
People do it all the time. You have to set up the amd64's to cross compile.
https://wiki.gentoo.org/wiki/Distcc/Cross-Compiling
One doesn't need to setup cross-compilation in order to generate
x86 code on amd64 systems: 64-bit amd64 gcc natively supports this,
just be sure to add -m32 to your {C,CXX,F,FC,LD}FLAGS variables.
Care should be taken with -march=native or -mtune=native arguments.
Vanilla distcc doesn't support this. Patch can be taken here[1] or
distcc from my overlay[2] may be used.
Another approach will be to use one powerful box to build all
packages for an older system: either root filesystem may be
exported via NFS to a powerful host or just copy entire disk image
to and fro that host; afterwards just setarch chroot to that
image / NFS mount and build all packages using modern hardware.
An old but still useful guide is here[3].
[1] https://groups.google.com/forum/#!topic/distcc-patches/eeP-9pTgz7E
[2] git://git.overlays.gentoo.org/dev/bircoph.git sys-devel/distcc
[3] http://www.gentoo-wiki.info/HOWTO_Emerge_on_very_slow_systems
Best regards,
Andrew Savchenko
pgpqjFjXODScJ.pgp
Description: PGP signature
Re: [gentoo-user] Re: which ebuilds use a specific eclass?
On Thu, 19 Feb 2015 22:56:20 + (UTC), James wrote: Neil Bothwick neil at digimed.co.uk writes: So for a given eclass, how to I find the list of all ebuilds Well, brute force works grep -Er 'inherit.*systemd' /var/portage '/usr/portage/' works for me, when bruting. Yes, I'd forgot to adjust for my moving the portage tree to a more logical location :) That shows every ebuild, you may want to reduce it to a list of packages for i in $(grep -Erl 'inherit.*systemd' /var/portage) do dirname $i done | sort -u Yea, sure, cool. (THANKS). However, I was looking for (wink wink nudge nudge) something sexy, using VDB (/var/db/pkg/) That only shows installed packages. If you want something a little more portagey, you could use qgrep. -- Neil Bothwick Disinformation is not as good as datinformation. pgpFekx6c1Xj7.pgp Description: OpenPGP digital signature
