Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 172313 - dev-libs/glib-2.12.9 build error in 'gatomic.c'
Summary: dev-libs/glib-2.12.9 build error in 'gatomic.c'
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-26 17:10 UTC by Jay
Modified: 2007-03-28 03:56 UTC (History)
0 users

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


Attachments
Build Log (build.log,23.62 KB, text/plain)
2007-03-26 17:12 UTC, Jay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jay 2007-03-26 17:10:12 UTC
When trying to compile glib, get a build error from Assembler :
Error: suffix or operands invalid for `cmpxchg`.

(build.log is attached)

Reproducible: Always

Steps to Reproduce:
1.emerge glib
2.
3.

Actual Results:  
Build of glib fails - please see attached build log.
Comment 1 Jay 2007-03-26 17:12:16 UTC
Created attachment 114520 [details]
Build Log
Comment 2 Jay 2007-03-26 17:12:51 UTC
Emerge --info output :

*** Deprecated use of action 'info', use '--info' instead
Portage 2.1.2.2 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.19-gentoo-r2 i686)
=================================================================
System uname: 2.6.19-gentoo-r2 i686 Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
Gentoo Base System version 1.12.1
Timestamp of tree: Mon, 26 Mar 2007 10:00:08 +0000
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.19.2-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=nocona -pipe -ftracer -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-O2 -march=nocona -pipe -ftracer -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ "
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--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"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa bash-completion berkdb bitmap-fonts cdr cli cracklib crypt cups dri dvd esd ffmpeg firefox fortran gdbm gnome2 gpm gtk iconv ipv6 isdnlog java libg++ midi mp3 mplayer msn ncurses nls nptl nptlonly offensive oss pam pcre perl ppds pppd python quicktime readline reflection session spl ssl tcpd truetype-fonts type1-fonts unicode win32codecs x86 xine xinerama xorg xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nv"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

Comment 3 Jay 2007-03-26 21:38:02 UTC
 Bug 125620 shows similar error: 
Error: suffix or operands invalid for `cmpxchg'
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2007-03-26 22:24:36 UTC
Why is this assigned to amd64?
Comment 5 Jay 2007-03-27 22:14:17 UTC
(In reply to comment #4)
> Why is this assigned to amd64?
> 

I also wondered why it had been assigned to amd64.
Incidentally, as with  Bug 125620 - changing CHOST to i686-pcu-linux-gnu gets rid of the build error.
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2007-03-28 03:56:09 UTC
Wow.  Your system is *messed* up...

Why are you using an x86 profile and an amd64 CHOST?

The fact that your system works at all is amazing.  You need to fix your CHOST (or your profile) to match.  Your system is capable of being "amd64" but what you've got now is just an abomination.  ;]

My suggestion would likely be to simply reinstall and keep your CHOST equal to your profile setting.  The "best" x86 CHOST is i686-pc-linux-gnu where the best amd64 is x86_64-pc-linux-gnu

If you are still having trouble after either reinstalling, or fixing your CHOST and recompiling your system entirely, please feel free to REOPEN this bug.