Simon Strandman posted <[EMAIL PROTECTED]>, excerpted below, on
Tue, 14 Feb 2006 09:07:24 +0100:
> Duncan skrev:
>> For those using modular-x, has anyone run into bug 121394 [1], window
>> corruption if CFLAGS include -fweb?
> I guess this is a gcc 4.0 only bug. -fweb is broken in gcc 4.0 and als
On Monday 13 February 2006 23:09, Simon Stelling wrote:
> Harm Geerts wrote:
> > # emerge --info
>
> [snip]
>
> It is only that verbose when you emerge -v --info. Is emerge a alias for
> emerge -v?
Doh, I should have thought about that myself :+
Thanks Simon
--
gentoo-amd64@gentoo.org mailing li
Harm Geerts wrote:
> # emerge --info
[snip]
It is only that verbose when you emerge -v --info. Is emerge a alias for emerge
-v?
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-amd64@gentoo.org mailing list
On Monday 13 February 2006 22:51, Harm Geerts wrote:
>
> OT:
> My emerge --info keeps getting longer as I expand my systems default
> environment. Is it really necessary for emerge --info to include all this,
> is there a way to filter it? When I run emerge --info as a regular user in
> the portag
On Monday 13 February 2006 14:49, Duncan wrote:
> For those using modular-x, has anyone run into bug 121394 [1], window
> corruption if CFLAGS include -fweb?
>
> The latest xorg-server-1.0.1-r3 does a filterflags -fweb as a result.
> However, I've not experienced the issue here. The bug (and resul
