public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Darren Grant <dgrant@monstertech.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from gcc-3.4.5 to gcc-3.4.6-r1
Date: Wed, 28 Jun 2006 14:30:29 -0700	[thread overview]
Message-ID: <44A2F4F5.4050100@monstertech.ca> (raw)
In-Reply-To: <44A2E9E0.3000708@monstertech.ca>

Darren Grant wrote:
> Benno Schulenberg wrote:
>> Darren Grant wrote:
>>  
>>> # gcc-config 1
>>>
>>>  * Switching native-compiler to x86_64-pc-linux-gnu-3.4.5
>>> ...             [ ok ]
>>> # env | grep 'GCC_SPECS='
>>>
>>> ...nothing.
>>>     
>>
>> Log back in first.  Environment is set when bash starts.
>>
>> Benno
>>   
> Ok... logged out and back in...
>
> env | grep 'GCC' ... returns nothing.
>
> env | grep 'gcc'
> MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.16.1/man:/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.5/man 
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.5 
>
> INFOPATH=/usr/share/info:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.16.1/info:/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.5/info 
>
>
> grep GCC_SPECS /etc/env.d/* /etc/profile* ~/.bash* ~/.profile*
> /etc/env.d/05gcc:GCC_SPECS=""
> /etc/profile.csh:setenv GCC_SPECS=''
> /etc/profile.env:export GCC_SPECS=''
> /root/.bash_history:unset GCC_SPECS && emerge --oneshot glibc
> /root/.bash_history:grep GCC_SPECS /etc/env.d/* /etc/profile* ~/.bash* 
> ~/.profile*
> /root/.bash_history:grep GCC_SPECS /etc/env.d/* /etc/profile* ~/.bash* 
> ~/.profile*
> /root/.bash_history:grep GCC_SPECS /etc/env.d/* /etc/profile* ~/.bash* 
> ~/.profile*
> /root/.bash_history:env | grep 'GCC_SPECS'
> /root/.bash_history:env | grep 'GCC_SPECS='
> grep: /root/.profile*: No such file or directory
>
Back in May I thought I was streamlining my make.conf file by changing 
from this...

CFLAGS="-mtune=k8 -O2 -pipe"
CFLAGS="-march=athlon64 -O2 -pipe"
MAKEOPTS="-j3"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
USE="session unicode cli pcre xml zlib threads mpm-prefork mysql imap 
libwww maildir sasl ssl gnome gtk2 -kde -qt dvdr alsa cdr apache2 nvidia 
opengl"

to this...

CFLAGS="-march=athlon64 -mtune=k8 -O2 -pipe"
MAKEOPTS="-j3"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
USE="nptl nptlonly session unicode cli pcre xml zlib threads mpm-prefork 
mysql imap libwww maildir sasl ssl gnome gtk2 -kde -qt dvdr alsa cdr 
apache2 nvidia opengl"

Any chance that's what's causing my gcc problems now?


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-28 22:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 18:39 [gentoo-user] Upgrading from gcc-3.4.5 to gcc-3.4.6-r1 Darren Grant
2006-06-27 20:28 ` Benno Schulenberg
2006-06-27 21:26   ` Darren Grant
2006-06-28  2:53     ` Richard Fish
2006-06-28 15:44       ` Darren Grant
2006-06-28 16:00         ` Richard Fish
2006-06-28 16:40           ` Richard Fish
2006-06-28 16:43             ` Richard Fish
2006-06-28 17:17               ` Darren Grant
2006-06-28 17:42                 ` Richard Fish
2006-06-28 18:18                   ` Benno Schulenberg
2006-06-28 18:53                     ` Darren Grant
2006-06-28 19:11                       ` Benno Schulenberg
2006-06-28 20:43                         ` Darren Grant
2006-06-28 21:30                           ` Darren Grant [this message]
2006-06-29 10:49                             ` Benno Schulenberg
2006-06-29 16:45                               ` Darren Grant
2006-06-29 20:37                                 ` Benno Schulenberg
2006-06-29 18:19                             ` Richard Fish
2006-06-30  0:10                               ` Darren Grant
2006-06-30 17:15                                 ` Richard Fish
2006-06-30 17:44                                   ` Darren Grant
2006-06-30 18:36                                     ` Alexander Skwar
2006-06-28 18:44                   ` Darren Grant
2006-06-28  2:48 ` Richard Fish

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=44A2F4F5.4050100@monstertech.ca \
    --to=dgrant@monstertech.ca \
    --cc=gentoo-user@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