Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[gentoo-user] Re: mesa 9.1.2.r1 fails to build
5 views
Skip to first unread message
walt
Jun 13, 2013, 8:50:02 PM6/13/13
to
On 06/13/2013 02:44 PM, Walter Dnes wrote:
> I'm on a new Dell i5 machine, stable, straight amd64 profile. I tried
> makeopts -j1 in depseration; doesn't help. The gzipped buildlog is
> attached.
The problem isn't obvious to me, but in the past I've seen strange linking
errors happen when the ebuild (for some strange reason) uses the headers
in /usr/include (from the previous version of the package) instead of the
headers in the new source code. No idea why.
Anyway, you could try removing your current mesa installation (after using
quickpkg, of course) and then trying the emerge again.
> I'm on a new Dell i5 machine, stable, straight amd64 profile. I tried
> makeopts -j1 in depseration; doesn't help. The gzipped buildlog is
> attached.
The problem isn't obvious to me, but in the past I've seen strange linking
errors happen when the ebuild (for some strange reason) uses the headers
in /usr/include (from the previous version of the package) instead of the
headers in the new source code. No idea why.
Anyway, you could try removing your current mesa installation (after using
quickpkg, of course) and then trying the emerge again.
Gregory Shearman
Jun 14, 2013, 12:50:02 AM6/14/13
to
In linux.gentoo.user, you wrote:
> The problem isn't obvious to me, but in the past I've seen strange linking
> errors happen when the ebuild (for some strange reason) uses the headers
> in /usr/include (from the previous version of the package) instead of the
> headers in the new source code. No idea why.
> Anyway, you could try removing your current mesa installation (after using
> quickpkg, of course) and then trying the emerge again.
Sometimes when a package fails to build while doing an:
> The problem isn't obvious to me, but in the past I've seen strange linking
> errors happen when the ebuild (for some strange reason) uses the headers
> in /usr/include (from the previous version of the package) instead of the
> headers in the new source code. No idea why.
> Anyway, you could try removing your current mesa installation (after using
> quickpkg, of course) and then trying the emerge again.
emerge -auDN world
I've had to add the '--with-bdeps=y' option:
emerge -auDN --with-bdeps=y world
For some reason I can't understand, it seems to work. It may not help
with mesa-9.1.2-r1 but it doesn't take much effort and can't hurt to try
--
Regards,
Gregory Shearman.
Daniel Pielmeier
Jun 14, 2013, 4:40:02 AM6/14/13
to
Bug 458550
--
Regards
Daniel
--
Regards
Daniel
Philip Webb
Jun 14, 2013, 7:30:02 AM6/14/13
to
130613 Walter Dnes wrote:
> I'm on a new Dell i5 machine, stable, straight amd64 profile.
> I tried makeopts -j1 in desperation; doesn't help.
> I'm on a new Dell i5 machine, stable, straight amd64 profile.
As someone noted : Bug 458550 . I ran into this,
but was too busy to look for a bug report & left 9.0.1 in place.
The extra USE flag allows it to install on my machine.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
Walter Dnes
Jun 14, 2013, 8:30:02 AM6/14/13
to
On Fri, Jun 14, 2013 at 10:35:54AM +0200, Daniel Pielmeier wrote
> Bug 458550
Thanks. My Google-fu isn't what it used to be. I've now built it
successfully with the shared-glapi flag.
--
Walter Dnes <walt...@waltdnes.org>
I don't run "desktop environments"; I run useful applications
> Bug 458550
Thanks. My Google-fu isn't what it used to be. I've now built it
successfully with the shared-glapi flag.
--
Walter Dnes <walt...@waltdnes.org>
I don't run "desktop environments"; I run useful applications
0 new messages