SEO

I just installed gentoo from CD - from stage 3.
I installed kde from binary from CD.
I just wanted quanta application and there are problems:

grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la: No such file or
directory
/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la:
No such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la' is
not a valid libtool archive
make[3]: *** [libkommanderwidgets.la] B³±d 1
make[3]: Leaving directory
`/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander/widgets'
make[2]: *** [all-recursive] B³±d 1
make[2]: Leaving directory
`/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander'
make[1]: *** [all-recursive] B³±d 1
make[1]: Leaving directory `/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1'
make: *** [all] B³±d 2

!!! ERROR: app-editors/quanta-3.2.1 failed.
!!! Function kde_src_compile, Line 128, Exitcode 2
!!! died running emake, kde_src_compile:make

What to do with this - in manual there is no solution.
Please help.

--
szpakuu(at)poczta.onet.pl

So anyway, it was like, 13:14 CEST May 05 2004, you know? Oh, and, yeah,
szpakuu was all like, "Dude,

> grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la: No such
> file or directory

Top of my head suggestion - run 'gcc-config -l' to find out which
compiler the system thinks it's using, then run 'gcc-config <string>'
to set it to the same one.

Copy and paste <string> from the output of the previous command, eg:
-----8<-----
# gcc-config -l
[1] x86_64-pc-linux-gnu-3.3.3
# gcc-config x86_64-pc-linux-gnu-3.3.3
----->8-----

If that doesn't work, try to locate the file that's allegedly missing
somewhere on your system and report back what you find.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
13:31:57 up 22 days, 18:05, 5 users, load average: 0.00, 0.00, 0.03
$ cat /dev/bollocks Registered Linux user #261729
synthesize viral e-services

szpakuu wrote:
> I just installed gentoo from CD - from stage 3.
> I installed kde from binary from CD.
> I just wanted quanta application and there are problems:
>
> grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la: No such file or
> directory
> /bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la:
> No such file or directory
> libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la' is
> not a valid libtool archive
> make[3]: *** [libkommanderwidgets.la] B³±d 1
> make[3]: Leaving directory
> `/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander/widgets'
> make[2]: *** [all-recursive] B³±d 1
> make[2]: Leaving directory
> `/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander'
> make[1]: *** [all-recursive] B³±d 1
> make[1]: Leaving directory `/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1'
> make: *** [all] B³±d 2
>
> !!! ERROR: app-editors/quanta-3.2.1 failed.
> !!! Function kde_src_compile, Line 128, Exitcode 2
> !!! died running emake, kde_src_compile:make
>
> What to do with this - in manual there is no solution.
> Please help.
>

Ooookay. Notice the following:
/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la
^^^^^^^^^^^^^^^^^
Did you change the CHOST flag in /etc/make.conf?
From
CHOST="i686-pc-linux-gnu"
to
CHOST="i386-pc-linux-gnu"
?

Now notice you installed from stage3.

Now read (from the installation handbook),
Warning: Although it might be tempting for non-stage1 users, they should
not change the CHOST setting in make.conf. Doing so might render their
system unusable. Again: only change this variable if you use a stage1
installation.

So you want to fix the problem? Unfortunately it's not trivial to fix
without a reinstallation.

So you have two options for your reinstallation:
1. Do not change the CHOST variable
2. Start from a stage1 installation

If at all possible, go route 1. By "possible", I mean that if you have a
Pentium II or above then do not change the CHOST flag.

Otherwise, you will have to go route 2 (which could take quite a while
in a i386-compatible processor).

HTH,
--
Ben M.

Johan Lindquist wrote:

> Copy and paste <string> from the output of the previous command, eg:
> -----8<-----
> # gcc-config -l
> [1] x86_64-pc-linux-gnu-3.3.3
> # gcc-config x86_64-pc-linux-gnu-3.3.3
> ----->8-----
>
> If that doesn't work, try to locate the file that's allegedly missing
> somewhere on your system and report back what you find.
>
> --
> Time flies like an arrow, fruit flies like a banana. Perth ---> *
> 13:31:57 up 22 days, 18:05, 5 users, load average: 0.00, 0.00, 0.03
> $ cat /dev/bollocks Registered Linux user #261729
> synthesize viral e-services

i686-pc-linux-gnu-3.3.2
gcc-config i686-pc-linux-gnu-3.3.2 - after that :

bash-2.05b# gcc-config i686-pc-linux-gnu-3.3.2
* Switching to i686-pc-linux-gnu-3.3.2 compiler...
[ ok ]
bash-2.05b#

but still:

/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la:
No such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la' is
not a valid libtool archive
make[3]: *** [libkommanderwidgets.la] B³±d 1
make[3]: Leaving directory
`/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander/widgets'
make[2]: *** [all-recursive] B³±d 1
make[2]: Leaving directory
`/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1/kommander'
make[1]: *** [all-recursive] B³±d 1
make[1]: Leaving directory `/var/tmp/portage/quanta-3.2.1/work/quanta-3.2.1'
make: *** [all] B³±d 2

!!! ERROR: app-editors/quanta-3.2.1 failed.
!!! Function kde_src_compile, Line 128, Exitcode 2
!!! died running emake, kde_src_compile:make
--
szpakuu(at)poczta.onet.pl

Ben Measures wrote:


> ^^^^^^^^^^^^^^^^^
> Did you change the CHOST flag in /etc/make.conf?
> From
> CHOST="i686-pc-linux-gnu"
> to
> CHOST="i386-pc-linux-gnu"

I changed nothing.
the line CHOST="i686-pc-linux-gnu" was there after installation


> Now notice you installed from stage3.
>
> Now read (from the installation handbook),
> Warning: Although it might be tempting for non-stage1 users, they should
> not change the CHOST setting in make.conf. Doing so might render their
> system unusable. Again: only change this variable if you use a stage1
> installation.
>
> So you want to fix the problem? Unfortunately it's not trivial to fix
> without a reinstallation.
>

So it seems that to avoid troubles I have to reinstall system and proceed
from stage 1.

--
szpakuu(at)poczta.onet.pl

szpakuu wrote:
> Ben Measures wrote:
>
>
>
>> ^^^^^^^^^^^^^^^^^
>>Did you change the CHOST flag in /etc/make.conf?
>>From
>>CHOST="i686-pc-linux-gnu"
>>to
>>CHOST="i386-pc-linux-gnu"
>
>
> I changed nothing.
> the line CHOST="i686-pc-linux-gnu" was there after installation
>
>
>
>>Now notice you installed from stage3.
>>
>>Now read (from the installation handbook),
>>Warning: Although it might be tempting for non-stage1 users, they should
>>not change the CHOST setting in make.conf. Doing so might render their
>>system unusable. Again: only change this variable if you use a stage1
>>installation.
>>
>>So you want to fix the problem? Unfortunately it's not trivial to fix
>>without a reinstallation.
>>
>
>
> So it seems that to avoid troubles I have to reinstall system and proceed
> from stage 1.
>

Not quite, but certainly if the CHOST flag was changed.

--
Ben M.

Ben Measures wrote:


>>
>> I changed nothing.
>> the line CHOST="i686-pc-linux-gnu" was there after installation
>>
>>
>>
>>>Now notice you installed from stage3.
>>>
>>>Now read (from the installation handbook),
>>>Warning: Although it might be tempting for non-stage1 users, they should
>>>not change the CHOST setting in make.conf. Doing so might render their
>>>system unusable. Again: only change this variable if you use a stage1
>>>installation.
>>>
>>>So you want to fix the problem? Unfortunately it's not trivial to fix
>>>without a reinstallation.
>>>
>>
>>
>> So it seems that to avoid troubles I have to reinstall system and proceed
>> from stage 1.
>>
>
> Not quite, but certainly if the CHOST flag was changed.
>
> --
> Ben M.

So I repeat:
>> I changed nothing.
>> the line CHOST="i686-pc-linux-gnu" was there after installation

If this is wrong - so there is bug in gentoo installation files.
Now I'm starting to reinstall from stage 1.

--
szpakuu(at)poczta.onet.pl

szpakuu wrote:
> Ben Measures wrote:
>> Ooookay. Notice the following:
>> /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la
>> ^^^^^^^^^^^^^^^^^
>> Did you change the CHOST flag in /etc/make.conf?
>> From
>> CHOST="i686-pc-linux-gnu"
>> to
>> CHOST="i386-pc-linux-gnu"
>> ?
>
>
> I changed nothing.
> the line CHOST="i686-pc-linux-gnu" was there after installation

Then if you get
# emerge info | grep 'CHOST'
CHOST="i686-pc-linux-gnu"

there is something else confusing the system (to cause it to look for
the i386 gcc libs).

I can't think of why at the moment but am working on it. Just make sure
that you *do* get the above result and post back (because I don't want
to be wasting time on a falsity).

--
Ben M.

szpakuu wrote:
> Ben Measures wrote:
>
>
>
>>>I changed nothing.
>>>the line CHOST="i686-pc-linux-gnu" was there after installation
>>>
>>>
>>>
>>>
>>>>Now notice you installed from stage3.
>>>>
>>>>Now read (from the installation handbook),
>>>>Warning: Although it might be tempting for non-stage1 users, they should
>>>>not change the CHOST setting in make.conf. Doing so might render their
>>>>system unusable. Again: only change this variable if you use a stage1
>>>>installation.
>>>>
>>>>So you want to fix the problem? Unfortunately it's not trivial to fix
>>>>without a reinstallation.
>>>>
>>>
>>>
>>>So it seems that to avoid troubles I have to reinstall system and proceed
>>>from stage 1.
>>>
>>
>>Not quite, but certainly if the CHOST flag was changed.
>>
>>--
>>Ben M.
>
>
> So I repeat:
>
>>>I changed nothing.
>>>the line CHOST="i686-pc-linux-gnu" was there after installation
>
>
> If this is wrong - so there is bug in gentoo installation files.
> Now I'm starting to reinstall from stage 1.
>

What I was saying is that if the CHOST flag wasn't changed then
something else is causing the problem. It may well be possible to fix
this (simply) without a reinstallation. However, you can (of course)
feel free to do so if you wish.

--
Ben M.

Ben Measures wrote:

> szpakuu wrote:
>> Ben Measures wrote:
>>
>>
>>
>>>>I changed nothing.
>>>>the line CHOST="i686-pc-linux-gnu" was there after installation
>>>>
>>>>
>>>>
>>>>
>>>>>Now notice you installed from stage3.
>>>>>
>>>>>Now read (from the installation handbook),
>>>>>Warning: Although it might be tempting for non-stage1 users, they
>>>>>should not change the CHOST setting in make.conf. Doing so might render
>>>>>their system unusable. Again: only change this variable if you use a
>>>>>stage1 installation.
>>>>>
>>>>>So you want to fix the problem? Unfortunately it's not trivial to fix
>>>>>without a reinstallation.
>>>>>
>>>>
>>>>
>>>>So it seems that to avoid troubles I have to reinstall system and
>>>>proceed from stage 1.
>>>>
>>>
>>>Not quite, but certainly if the CHOST flag was changed.
>>>
>>>--
>>>Ben M.
>>
>>
>> So I repeat:
>>
>>>>I changed nothing.
>>>>the line CHOST="i686-pc-linux-gnu" was there after installation
>>
>>
>> If this is wrong - so there is bug in gentoo installation files.
>> Now I'm starting to reinstall from stage 1.
>>
>
> What I was saying is that if the CHOST flag wasn't changed then
> something else is causing the problem. It may well be possible to fix
> this (simply) without a reinstallation. However, you can (of course)
> feel free to do so if you wish.
>

Sometime ago I installed from stage 1 and system worked OK till I changed
mainboard (but installing from stage1 take time).
So for now I just want to have working system without searching for
solutions what went wrong during install.

--
szpakuu(at)poczta.onet.pl