| View previous topic :: View next topic |
| Author |
Message |
amightywind
Tux's lil' helper
Joined: 01 Jun 2004
Posts: 137
Location: Andover, MN USA
|
 Posted: Sun Jul 29, 2007 6:03 pm Post subject: Aspell build fails during emerge gnome |
 |
|
I am installing Gentoo for for a new core duo machine. I am doing an initial 'emerge gnome'. There are 356 packages to install. The build fails on aspell in an examples directory:
| Code: |
/usr/lib/gcc/i486-pc-linux-gnu/4.1.2/../../../../i486-pc-linux-gnu/bin/ld: warning libstdc++.so.6 needed by ../lib/,libs/libaspell.so, not found (try using -rpath or -rpath-link)
../lib/.libs/libaspell.so: undefined reference to `std::basic_string<char, std::char_traits<char>, std::allocator<char> >Basic_string....
|
Is anyone else seeing this?
_________________
amightywind |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sun Jul 29, 2007 9:38 pm Post subject: |
|
|
Can you do this:
and post the output?
Also, "emerge --info"
_________________
Thomas S. Howard |
|
| Back to top |
|
|
amightywind
Tux's lil' helper
Joined: 01 Jun 2004
Posts: 137
Location: Andover, MN USA
|
| Posted: Mon Jul 30, 2007 12:05 am Post subject: |
|
|
Thanks for the response.
| Code: | Code:
gcc-config -l |
| Quote: | | and post the output? |
| Code: |
# gcc-config -l
[1] i486-pc-linux-gnu-4.1.2
|
| Quote: | | Also, "emerge --info" |
| Code: |
Portage 2.1.2.9 (default-linux/x86/2007, gcc-4.1.2 glibc-2.5-r4, 2.6.20-gentoo-r8
====================================================
System uname: 2.6.20-gentoo-r8 i686 Intel(R) Core (TM)2 CPU 6400 @ 2.13GHz
Gentoo Base System release 1.12.9
Timestamp of tree: Sun, 29 Jul 2007 15:30:10 +0000
ccace version 2.4 [enabled]
dev-lang/python: 2.4.4-r4
dev-python/pycrypto: 2.01-r5
dev-util/ccache: 2.4-r7
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake 1.5,1.6.3, 1,7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils-2.17
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.23b
virtual/os-headers: 2.6.21
ACCEPT_KEYWORDS="~x86"
AUTOCLEAN="yes"
CBUILD="i486-pc-linux-gnu"
CFLAGS="O2 -mtune=i686 -pipe"
CHOST="i486-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-O2 -mtune=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTIONS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=local --exclude=/packages --filter=H_**/files/digest-*-"
PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
USE="X acl alsa berkdb bitmap-fonts cli cracklib crypt cups dbus dri firefox fortran gdbm gpm gtk guile iconv ipv6..."
...
|
I typed this in by hand, as there is not enough running on the machine for a flashkey to work and I have no mail client installed. If you need more I will have to get the USB going. The ebuild looks like the LDFLAGS are wrong for one directory. All I'd need to do to get it running is to comment the target dir "example" out of the Makefile.am.
_________________
amightywind |
|
| Back to top |
|
|
Dirk.R.Gently
Guru
Joined: 29 Jan 2007
Posts: 546
Location: Titan
|
| Posted: Mon Jul 30, 2007 12:23 am Post subject: |
|
|
First of all if using a Core Duo, i486 is the wrong CHOST! Core Duo's are 686 arch's. This could be very potientially bad news. If I remember correctly change CHOST at this point can be very dangerous. There is this but I would be scared to try it unless you are desperate. What did you set your CHOST and CFLAGS to?
_________________
• Helpful Linux Tidbits |
|
| Back to top |
|
|
amightywind
Tux's lil' helper
Joined: 01 Jun 2004
Posts: 137
Location: Andover, MN USA
|
| Posted: Mon Jul 30, 2007 1:12 am Post subject: |
|
|
| Quote: | | First of all if using a Core Duo, i486 is the wrong CHOST! Core Duo's are 686 arch's. |
Setting the CHOST was not part of the installation docs. GCC itself it seems did not pick up the canonical target when it was configured and emerged. Also, I set the gcc options for -mtune=i686. I don't think it has any effect on the portage profile. I can go back to the chroot sequence if necessary, or remake the world and kernel with the new flags.
What are proper CFLAGS and CHOST for a Core Duo system, and at what point in the install should they be applied?
| Quote: | | There is this but I would be scared to try it unless you are desperate. |
Well, this is Gentoo after all. A manual install only takes a couple of hours.
_________________
amightywind |
|
| Back to top |
|
|
Dirk.R.Gently
Guru
Joined: 29 Jan 2007
Posts: 546
Location: Titan
|
| Posted: Mon Jul 30, 2007 5:54 am Post subject: |
|
|
| amightywind wrote: | | Quote: | | First of all if using a Core Duo, i486 is the wrong CHOST! Core Duo's are 686 arch's. |
Setting the CHOST was not part of the installation docs. GCC itself it seems did not pick up the canonical target when it was configured and emerged. Also, I set the gcc options for -mtune=i686. I don't think it has any effect on the portage profile. I can go back to the chroot sequence if necessary, or remake the world and kernel with the new flags.
What are proper CFLAGS and CHOST for a Core Duo system, and at what point in the install should they be applied?
| Quote: | | There is this but I would be scared to try it unless you are desperate. |
Well, this is Gentoo after all. A manual install only takes a couple of hours. |
Could you post your CHOST?
_________________
• Helpful Linux Tidbits |
|
| Back to top |
|
|
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Mon Jul 30, 2007 5:30 pm Post subject: |
|
|
Moved from Installing Gentoo to Desktop Environments.
Desktop stuff, so moved here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
amightywind
Tux's lil' helper
Joined: 01 Jun 2004
Posts: 137
Location: Andover, MN USA
|
| Posted: Tue Aug 07, 2007 6:04 pm Post subject: [solved] Aspell build fails during emerge gnome |
|
|
Didn't install the right stage3. For Core Duo use i686.
_________________
amightywind |
|
| Back to top |
|
|
|
Desktop Environments
