Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 28437 - emerge xfree fails during link of 'XFree86' with error in function 'VESAScreenInit' with an undefined reference to 'afbScreenInit'
Summary: emerge xfree fails during link of 'XFree86' with error in function 'VESAScree...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: Sparc Linux
: High major (vote)
Assignee: Sparc Porters
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-11 06:49 UTC by Phil West
Modified: 2006-02-04 06:05 UTC (History)
1 user (show)

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


Attachments
the link command and resulting errors (xfree.log,2.85 KB, text/plain)
2003-09-11 06:51 UTC, Phil West
Details
the link command and resulting errors (xfree.log,2.85 KB, application/octet-stream)
2003-09-11 06:52 UTC, Phil West
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Phil West 2003-09-11 06:49:09 UTC
This is on a new install on an Ultra2 SMP.  When I 'emerge xfree' it appears to
compile and build most of the package, then fails with a link error on
"XFree86".  It looks like libdriver.a does not contain a reference to
afbScreenInit, in particular vesa_drv.o.

I've done an 'emerge sync' and have been able to reproduce this after bringing
the system up to date 'emerge -u world'.  I initially built the system using
-mcpu=v9 in CFLAGS, then I read about problems with that so I switched it to
-mcpu=ultrasparc.  Perhaps that has something to do with it?  I didn't rebuild
with an 'emerge -e world' after making the change.  The system is otherwise
clean and working.

Reproducible: Always
Steps to Reproduce:
1. emerge xfree
2.
3.

Actual Results:  
emerge fails with a link error towards the end of the compile process

Expected Results:  
sucessful emerge of xfree

Portage 2.0.49-r3 (default-sparc64-1.4, gcc-3.2.3, glibc-2.3.1-r4, 2.4.21-sparc-r1)
=================================================================
System uname: 2.4.21-sparc-r1 sparc64 sun4u
ccache version 2.2 [enabled]
ACCEPT_KEYWORDS="sparc"
AUTOCLEAN="yes"
CFLAGS="-mcpu=ultrasparc -O2 -pipe"
CHOST="sparc-unknown-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=ultrasparc -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox ccache nostrip cvs"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j8"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="sparc arts apm avi encode esd fbcon foomaticdb gtk imlib kde libwww mad
mikmod motif ncurses nls oggvorbis oss qt sdl spell xmms zlib gdbm berkdb
readline perl acl apache2 crypt cups debug doc gif gnome gtk2 imap ipv6 java
jpeg maildir mozilla mpeg odbc opengl pam pdflib png postgres prelude python
slang ssl tcpd tetex tiff truetype X xml2 xv"
Comment 1 Phil West 2003-09-11 06:51:59 UTC
Created attachment 17494 [details]
the link command and resulting errors
Comment 2 Phil West 2003-09-11 06:52:15 UTC
Created attachment 17495 [details]
the link command and resulting errors
Comment 3 Jason Wever (RETIRED) gentoo-dev 2003-09-11 14:06:43 UTC
That would be my first inclination as well.  IIRC, using -mcpu=v9 can cause some programs to think you are running in 64 bit mode (Gentoo Linux userland runs in 32 bit mode).  Hopefully you haven't installed too much yet :)
Comment 4 Phil West 2003-09-21 15:36:17 UTC
I wiped my install and started over using -mcpu=ultrasparc from the beginning.  I was then able to 
'emerge xfree' without any problems.  I had first tried to do an 'emerge -e world' to update the 
system to use -mcpu=ultrasparc but that failed with some strange errors.  I was also unable to 
complete scripts/bootstrap.sh (in an attempt to update the system), so I suspect the system was 
pretty messed up by the -mcpu=v9 flag.