Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 262188 - dev-libs/glib-{2.16.6,2.18.4} - {standard input}:63: Error: suffix or operands invalid for `cmpxchg'
Summary: dev-libs/glib-{2.16.6,2.18.4} - {standard input}:63: Error: suffix or operand...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 20:01 UTC by Sasha Polonsky
Modified: 2009-03-12 18:19 UTC (History)
1 user (show)

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


Attachments
/var/tmp/portage/dev-libs/glib-2.16.6/temp/build.log (build.log,62.08 KB, text/plain)
2009-03-11 20:03 UTC, Sasha Polonsky
Details
Output of emerge --info (emerge--info.txt,2.70 KB, text/plain)
2009-03-11 20:04 UTC, Sasha Polonsky
Details
/var/tmp/portage/dev-libs/glib-2.16.6/temp/environment (environment.txt,103.65 KB, text/plain)
2009-03-11 20:08 UTC, Sasha Polonsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sasha Polonsky 2009-03-11 20:01:09 UTC
Glib of the versions mentioned in bug summary just fail to emerge on x86_64 machine. Without Glib, there is no syslog-ng and no Midnight Commander - which for me means no Gentoo Linux at all. The bug appears with MAKEPOPTS=-j4 and with MAKEOPTS=-j1, as well as both with CFLAGS="-O3" and CFLAGS="-O2". Some additional info attached.

Reproducible: Always

Steps to Reproduce:
1. Run emerge glib (which will start emerging glib-2.16.6)
2. See error message
3. export ACCEPT_KEYWORDS="~x86"
4. Run emerge "=dev-libs/glib-2.18.4" (which will start emerging glib-2.18.4)
5. See error message
6. Enjoy your Gentoo without syslog-ng and mc.




make: *** [all] Error 2
 *
 * ERROR: dev-libs/glib-2.16.6 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2693:  Called die
 * The specific snippet of code:
 *       emake || die "make failed"
 *  The die message:
 *   make failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/glib-2.16.6/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.16.6/temp/environment'.
 *

>>> Failed to emerge dev-libs/glib-2.16.6, Log file:

>>>  '/var/tmp/portage/dev-libs/glib-2.16.6/temp/build.log'

 * Messages for package dev-libs/glib-2.16.6:

 *
 * ERROR: dev-libs/glib-2.16.6 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2693:  Called die
 * The specific snippet of code:
 *       emake || die "make failed"
 *  The die message:
 *   make failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/glib-2.16.6/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/glib-2.16.6/temp/environment'.
 *
livecd glib #
Comment 1 Sasha Polonsky 2009-03-11 20:03:22 UTC
Created attachment 184730 [details]
/var/tmp/portage/dev-libs/glib-2.16.6/temp/build.log
Comment 2 Sasha Polonsky 2009-03-11 20:04:52 UTC
Created attachment 184731 [details]
Output of emerge --info
Comment 3 Sasha Polonsky 2009-03-11 20:08:23 UTC
Created attachment 184732 [details]
/var/tmp/portage/dev-libs/glib-2.16.6/temp/environment
Comment 4 David Abbott (RETIRED) gentoo-dev 2009-03-11 22:37:11 UTC
This may have something to do with it;
ACCEPT_KEYWORDS="x86"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
Comment 5 Jeroen Roovers (RETIRED) gentoo-dev 2009-03-12 18:08:49 UTC
You have set an x86 profile while you run an amd64 (x86_64) Gentoo system. Please fix that by all means before you report any more bugs.
Comment 6 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-03-12 18:12:06 UTC
To clarify this a bit further, although you are running an Intel CPU, you should set
  ACCEPT_KEYWORDS="amd64"
as this is the official arch for any x86_64 system in Gentoo. This has historical reasons and cannot be changed to x86_64 easily.
Comment 7 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-03-12 18:19:42 UTC
And of course set your /etc/make.profile symlink to an amd64 profile as well.