-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
alain.didierj...@free.fr wrote:
> Has one of you guys already switched from gcc-4.1.2 to gcc-4.3.2 and
> performed "emerge system" ?
> What gives ? Any problem ? Is it worth it right now ? Please tell...
>
> --
> ~adj~
I am afraid I can't really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Volker Armin Hemmann wrote:
> On Freitag 06 Februar 2009, Christopher Walters wrote:
>
>> for 64-bit systems, Debian and its child Ubuntu, have packages compiled to
>> use the "generic x86_64" option, so they can be use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Mike Edenfield wrote:
> On 2/5/2009 7:01 AM, Volker Armin Hemmann wrote:
>
>> no. He is an idiot if he does not read the docs. Simple. Like people
>> who don't
>> read the manual to their car or vcr and then complaining if something
>> does not
>> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alan McKinnon wrote:
> On Wednesday 04 February 2009 01:48:34 Nikos Chantziaras wrote:
>> So all in all, I agree. Using Gentoo is nowadays not so much a matter
>> of performance optimization but of better control of how to build the
> I also get si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dirk Uys wrote:
> Hi
>
> Have anyone else successfully built kde4.2?
>
> Regards
> Dirk
Hi Dirk,
I was able to compile KDE 4.2 successfully with no problems, without using
anything outside of Portage.
What arch are you using? Did you use the ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Mark Knecht wrote:
> Hi,
>I'm not used to seeing all the additional messages below the
> blockage indication. Can someone possibly help me understand how to
> read this?
>
>Are there really application packages that cannot be installed at
>
6 matches
Mail list logo