Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 107434 - app-emulation/bochs-2.1.1 compile failure
Summary: app-emulation/bochs-2.1.1 compile failure
Status: VERIFIED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-27 12:25 UTC by Zeljko Vrba
Modified: 2005-09-28 08:31 UTC (History)
1 user (show)

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 Zeljko Vrba 2005-09-27 12:25:38 UTC
When compiling bochs with debugger enabled I get compiler error.

Reproducible: Always
Steps to Reproduce:
1. add app-emulation/bochs debugger to /etc/portage/package.use
2. emerge -vp bochs reports [ebuild  N    ] app-emulation/bochs-2.1.1  +debugger 
+gtk2 +readline +sdl -wxwindows 0 kB 
3. emerge bochs fails

Actual Results:  
Compilation stops with an error. The problem is that I've done i686 stage3 
install, and the specified directory doesn't exist. However, i686-pc-... exists.

grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No such 
file or directory
/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/
libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la' 
is not a valid libtool archive
make[1]: *** [libbx_sdl.la] Error 1
make[1]: Leaving directory `/var/tmp/portage/bochs-2.1.1/work/bochs-2.1.1/gui'
make: *** [bochs_plugins] Error 2


Expected Results:  
Successful installation,

Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.5-20050130, glibc-2.3.4.
20041102-r1, 2.6.12-gentoo-r6 i686)
=================================================================
System uname: 2.6.12-gentoo-r6 i686 Intel(R) Pentium(R) M processor 2.00GHz
Gentoo Base System version 1.6.12
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share
/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/shar
e/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/
distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa arts avi berkdb bitmap-fonts crypt emboss encode esd fam fortran
 gdbm gif gpm gtk gtk2 imagemagick imlib ipv6 jpeg libg++ libwww mad mikmod mmx 
motif mp3 mpeg ncurses ogg oggvorbis opengl oss pam pdflib perl png python qt qu
icktime readline ruby sdl spell ssl tcltk tiff truetype truetype-fonts type1-fon
ts vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-09-27 12:31:08 UTC
Try this and report back:

fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu
Comment 2 Zeljko Vrba 2005-09-27 12:47:12 UTC
ok, it compiles fine now. thanks.
Comment 3 Kerin Millar 2005-09-27 12:53:51 UTC
Zeljko, I'm curious ... did you make use of any of the binary packages available
on the optional 2nd CD (specifically, the packages-x86-2005.1.iso CD)?

The reason I ask is because all of the packages on that particular CD image are
built with CHOST="i386-pc-linux-gnu" which will eventually cause unpleasant
issues to occur if you mix these packages with a base system built using a
different CHOST; this would be the case when using an i686 stage3 tarball for
example.
Comment 4 Zeljko Vrba 2005-09-28 08:31:50 UTC
Actually, I have used the packages CD and p4 stage3. Should I do something to 
fix it?