Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 51360 - Bug when emerging gedit 2.6.1 when installing latest gnome 2.6.1
Summary: Bug when emerging gedit 2.6.1 when installing latest gnome 2.6.1
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-18 01:03 UTC by Avinash Meetoo
Modified: 2004-08-08 16:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Avinash Meetoo 2004-05-18 01:03:20 UTC
I use 2004.1 on an AMD Athlon XP and libstdc++.la can be found (as expected) in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2

But when emerging gedit (the command I used was ACCEPT_KEYWORDS="~x86" emerge gnome), the ebuild script stops with the following error (from memory...) :

libtool: grep and sed cannot find /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la

which is pretty simple to understand. libtool is trying to find the file in i386-pc-linux-gnu whereas in reality it is in i686-pc-linux-gnu...

To solve the problem, I simply made a symbolic link from i686-pc-linux-gnu to i386-pc-linux-gnu and all went well.

I then removed the symbolic link and gedit works well in gnome now.

Reproducible: Always
Steps to Reproduce:
1. emerge -sync (done on 17/05/2004 at 12:00 GMT)
2. ACCEPT_KEYWORDS="~x86" emerge gnome
3.

Actual Results:  
libtool: grep and sed cannot find
/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/libstdc++.la

Expected Results:  
Found libstdc++.la in i686-pc-linux-gnu as the other ebuilds do :-)

AMD Athlon XP 1800+
256 MB RAM
Building everything without gdm or X being active (of course :-)
Comment 1 foser (RETIRED) gentoo-dev 2004-05-18 09:11:21 UTC
i'm quite sure there's something messed on your system and has little todo with gedit.

reopen if there's more proof
Comment 2 Gernot Ziegler 2004-06-04 15:23:17 UTC
I had the same problem when emerging gnome from a virgin 2004.1 inst, completely masked before, so it seems to be common. I base my system on a stage3 package, maybe that is the reason ? 
Comment 3 Dmitry M. Shatrov 2004-06-05 00:47:18 UTC
Had the bug also, and had to ln -s i686-pc-linux-gnu i386-pc-linux-gnu, then it went fine
The bug arises when make reaches plugins/spell directory
I've gat a stage3 GRP 2004.1 installation
Comment 4 Joe McCann (RETIRED) gentoo-dev 2004-06-05 01:13:51 UTC
did any of you mess with the CHOST line in make.conf after installing from a stage 3? 
Comment 5 Joe McCann (RETIRED) gentoo-dev 2004-06-05 01:14:28 UTC
also post emerge info when reporting bugs (always)
Comment 6 Avinash Meetoo 2004-06-05 02:53:55 UTC
Replying to Joe McCann :

Personally, I didn't touch the CHOST variable in make.conf (it has always been CHOST="i686-pc-linux-gnu")

By the way, I also installed a stage3 Gentoo. Might be related to that?

Avinash
Comment 7 foser (RETIRED) gentoo-dev 2004-08-08 16:53:25 UTC
I don't know what to do with this, it doesn't seem to me a gedit bug. Maybe the 2004.1 was partially screwed up, but then i would've expected more reports.

Anyway i'm gonna close this on a lack of info basis.