From: Raphael Bastos <tecnologia@bastosservice.com.br>
To: gentoo-user-br@lists.gentoo.org
Subject: Re: [gentoo-user-br] Problema ao atualizar GLIBC para versão 2.13-r4
Date: Wed, 7 Dec 2011 21:01:20 -0200 [thread overview]
Message-ID: <CAPQRN=VC23cn1C23VwC5hUrw90es+CBF_97rfjn7TqdbC5QONQ@mail.gmail.com> (raw)
In-Reply-To: <007801ccb52c$0c3e74f0$24bb5ed0$@esds.com.br>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Em 7 de dezembro de 2011 20:03, Eduardo Schoedler <listas@esds.com.br>escreveu:
> Em 07/12/2011 20:00, Raphael Bastos escreveu:
> > Take a look Eduardo,
> >
>
> http://www.valleytechnologiesllc.com/industry-technology/gentoo-linux-gcc-gl
> ibc-updates.html
>
> Ok, esse procedimento é para upgrade do gcc... quando atualizo o gcc,
> sempre
> faço isso.
> Mas nada diz que preciso recompilar todo o system *só* por causa do glibc.
>
> Abs,
>
> --
> Eduardo Schoedler
>
>
> Se fosse desnecessário, na geração do stage3 via catalyst a ordem de
compilação poderia ser invertida....
>>> Emerging (128 of 140) sys-libs/glibc-2.13-r4
>>> Installing (128 of 140) sys-libs/glibc-2.13-r4
>>> Emerging (129 of 140) sys-devel/gcc-4.5.3-r1
>>> Installing (129 of 140) sys-devel/gcc-4.5.3-r1
;)
[-- Attachment #2: Type: text/html, Size: 1610 bytes --]
next prev parent reply other threads:[~2011-12-07 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 16:19 [gentoo-user-br] Problema ao atualizar GLIBC para versão 2.13-r4 Raphael Bastos
2011-12-07 18:46 ` Eduardo Schoedler
2011-12-07 19:28 ` Raphael Bastos
2011-12-07 19:36 ` Raphael Bastos
2011-12-07 19:54 ` Dalton Barreto
2011-12-07 20:18 ` RES: " Eduardo Schoedler
2011-12-07 21:59 ` Raphael Bastos
2011-12-07 22:03 ` RES: " Eduardo Schoedler
2011-12-07 23:01 ` Raphael Bastos [this message]
2011-12-08 15:24 ` Thiago Nunes
2011-12-08 15:51 ` Raphael Bastos
2011-12-08 16:17 ` Daniel da Veiga
2011-12-08 18:06 ` Raphael Bastos
2011-12-08 1:54 ` Dalton Barreto
2011-12-08 14:22 ` Raphael Bastos
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='CAPQRN=VC23cn1C23VwC5hUrw90es+CBF_97rfjn7TqdbC5QONQ@mail.gmail.com' \
--to=tecnologia@bastosservice.com.br \
--cc=gentoo-user-br@lists.gentoo.org \
/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