On Sunday 29 October 2006 15:17, Hans de Hartog wrote:
[SNIP]
> > I guess you've learned by now that you should never run
> > --depclean blindly. Always run it with --pretend first and ensure that it
> > doesn't do something stupid. Unfortunately this is a little late for that
> > though... :(
>
>
Bo Ørsted Andresen wrote:
>
> Oh, and just for the the record. Whatever you do with this don't downgrade
> glibc! :p That will make you even more screwed that you are already. I guess
> you've learned by now that you should never run --depclean blindly. Always
> run it with --pretend first and
Bo Ørsted Andresen wrote:
>
> I assume you've changed your CHOST when upgrading glibc without having a clue
> about you were doing...
>
> http://www.gentoo.org/doc/en/change-chost.xml
>
Yes, now I remember something like that.
Don't know if it was glibc, but some
package told me to do so. So I
On Saturday 28 October 2006 22:01, Bo Ørsted Andresen wrote:
> I assume you've changed your CHOST when upgrading glibc without having a
> clue about you were doing...
>
> http://www.gentoo.org/doc/en/change-chost.xml
Oh, and just for the the record. Whatever you do with this don't downgrade
glibc
On Saturday 28 October 2006 17:33, Hans de Hartog wrote:
[SNIP]
> >>CHOST="i486-pc-linux-gnu"
> >
> > do 'gcc-config -c' & 'gcc-config -l' to explore;
> > try 'gcc-config i486-pc-linux-gnu-4.1.1' to fix the problem.
>
> [EMAIL PROTECTED] ~ $ gcc-config -c
> * gcc-config: Active gcc profile is inva
On AD 2006 October 28 Saturday 11:40:13 AM +0200, Hans de Hartog wrote:
> checking for C++ compiler default output file name... configure: error:
> C++ compiler cannot create executables
>
> or
>
> gcc-config error: Could not run/locate "gcc"
> ...
> [I--] [ -] sys-devel/gcc-4.1.1 (4.1)
> [I--] [
Philip Webb wrote:
> 061028 Hans de Hartog wrote:
>
>>it dies at the first emerge with:
>>checking for C++ compiler default output file name... configure: error:
>>C++ compiler cannot create executables.
>
> ...
>
>>CHOST="i486-pc-linux-gnu"
>
>
> do 'gcc-config -c' & 'gcc-config -l' to explor
061028 Hans de Hartog wrote:
> it dies at the first emerge with:
> checking for C++ compiler default output file name... configure: error:
> C++ compiler cannot create executables.
...
> CHOST="i486-pc-linux-gnu"
do 'gcc-config -c' & 'gcc-config -l' to explore;
try 'gcc-config i486-pc-linux-gnu-4.
Bo Ørsted Andresen wrote:
> On Saturday 28 October 2006 13:43, Hans de Hartog wrote:
>
>>but it dies at the first emerge with:
>>checking for C++ compiler default output file name... configure: error:
>>C++ compiler cannot create executables.
>
>
> Do you have ccache installed? If you do try to
On Saturday 28 October 2006 13:43, Hans de Hartog wrote:
> but it dies at the first emerge with:
> checking for C++ compiler default output file name... configure: error:
> C++ compiler cannot create executables.
Do you have ccache installed? If you do try to remerge that.
# emerge --oneshot ccac
After the thread about depclean I thought that dep (emerge udept)
was a better way to clean up things, so I did a "dep -d".
It took a long time so I went away. When I came back, emerge dies
constantly with:
checking for C++ compiler default output file name... configure: error:
C++ compiler cannot
11 matches
Mail list logo
