[gentoo-user] Re: Broken GCC

[Viktor Larionov <Viktor.Larionov@salva.ee>]

[-- Attachment #1.1.1: Type: text/plain, Size: 2176 bytes --]


Viktor Larionov
IT osakonna juhataja
IT-osakond
Salva Kindlustuse AS
Tel: (+372) 683 0630 | GSM: (+372) 566 86811 | Viktor.Larionov@salva.ee | www.salva.ee
(SMX)338844

On 2012-09-09 05:08 AM, Samuraiii <samurai.no.dojo [at] gmail> wrote:
> On 2012-09-08 02:33, Andrey Moshbear wrote: 
>> On Fri, Sep 7, 2012 at 5:03 PM, Samuraiii <samurai.no.dojo [at] gmail>
wrote: 
>>> 
>>> 
>>> On 2012-09-07 19:38, Andrey Moshbear wrote: 
>>>> On Fri, Sep 7, 2012 at 1:24 PM, Samuraiii <samurai.no.dojo [at] gmail>
wrote: 
>>>> 
>>>>> Are there any tips for gentoo amd64 with core2duo? 
>>>>> Google doesn't seem to give any usable answers (I don't need configure

>>>>> binhost yet) 
>>>> While I can make a binpkg for gcc:{4,5,4.6,4.7} or glibc-2.15-r2 on my 
>>>> c2d-penryn laptop, my adsl upload rate is pretty slow, so it'll take a 
>>>> while to upload it to my VPS. 
>>>> 
>>>> In terms of guides, a 5-second googling showed up: 
>>>> https://wiki.gentoo.org/wiki/Binary_package_guide 
>>>> http://en.gentoo-wiki.com/wiki/Using_Portage_BINHOST 
>>>> 
>>> I have an idea waht about make chrooted mini install just to compile gcc

>>> glibc and binutils... wouldn't take so long time than upload or emerge 
>>> -NuDe @world... 
>> Download stage1, chroot into it, and run 
>> /usr/portage/scripts/bootstrap.sh, then exit the chroot and copy 
>> usr/include recursively. 
>> However, you will still need to do emerge -e @world because the rest 
>> of /usr/include may still be dysfunctional. 
>> 
>> Also, -D -N -u is redundant when combined with -e. -e implies -D and 
>> -N -u is pointless when -e is used, since everything is already 
>> included. 
>> 
> After building, installig gcc glibc and binutils packages still no 
> luck... I thing there must be some config messed rather than package.

Just to be mentioned.
For anyone else running into the same kind of problem Samuraiii described,
before you start rebuilding your glibc or doing anything else global: check
the permissions for your /usr/local/include and your /usr/local in general.

In case you by accident set it to wrong, you will get exactly the same
results, Samuraii got.

Hope this helps anybody.

Cheers,
vik

[-- Attachment #1.1.2: Type: text/html, Size: 4269 bytes --]

[-- Attachment #1.2: fSRqcm148ZzXjGP.gif --]
[-- Type: image/gif, Size: 6207 bytes --]