public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org, jeramia.poland@gmail.com
Subject: Re: [gentoo-catalyst] emerge ati-drivers-14.4_p1 fails 3.16.5-sources xorg 1.15 gcc 4.8.3 graphite and lto
Date: Sat, 22 Nov 2014 16:21:34 -0500	[thread overview]
Message-ID: <5470FE5E.9090809@gentoo.org> (raw)
In-Reply-To: <CAGNNSAC6C9RVZ3e4MnzQH6rViXhH4Bkt6HteJ3Kj5QvkS7C=-w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

This appears to belong on bugzilla, and has absolutely nothing to do
with catalyst.

-Zero

On 11/20/2014 03:19 AM, Jeramia Poland wrote:
> Emerging ati-drivers-14.4_p1 fails on a 3.16.5-sources install with xorg
> 1.15 and gcc 4.8.3 with graphite and lto enabled.  I enabled graphite and
> lto using these steps:
> http://yuguangzhang.com/blog/enabling-gcc-graphite-and-lto-on-gentoo/
> 
> I thought graphite and or lto could be a problem so I added the no-lto and
> no-graphite options for ati-drivers in the package.env file but no luck.
> 
> I tried changing to the gcc-4.8.3 vanilla profile through gcc-config but
> that didn't work either.
> 
> I am getting a message from portage about missing xattr pax and how that
> might lead to a problem with ati-drivers but I'm not sure how to enable
> those.
> 
> Attached are the info file, build log, pqv output and environment files.
> 
> Anybody know what I should do?
> 
> Thanks,
> Jeramia
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

      reply	other threads:[~2014-11-22 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  8:19 [gentoo-catalyst] emerge ati-drivers-14.4_p1 fails 3.16.5-sources xorg 1.15 gcc 4.8.3 graphite and lto Jeramia Poland
2014-11-22 21:21 ` Rick "Zero_Chaos" Farina [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5470FE5E.9090809@gentoo.org \
    --to=zerochaos@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.org \
    --cc=jeramia.poland@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox