public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  emerge of ksh93 erroring out.. who can interpret
Date: Mon, 07 Jan 2008 14:52:29 -0600	[thread overview]
Message-ID: <cr25o3pkcgo5mbtc92kg393b34bbj28ncq@4ax.com> (raw)

I'm having a time getting ksh93 to install (build error at the end)

USE='static' emerge -v ksh93

The only other use flag coming up was `nls'

I wasn't real eager for `static' necessarily but without `static' had
already failed and I saw it was a possible flag.  Also it might be
handy sometime in a trouble situation where only `/ ' is mounted.

But that discussion is for some other time.  

Can anyone interpret this emerge failure and have some educated
guesses what I should do to get it to compile.  That message follows
the eix output below.  

My feeble take on the message is that it is related to the compiler. 

eix shows two installed and I guess that may be the problem:
eix -I gcc$

  [D] sys-devel/gcc
  Available versions:  
	(2.95)	2.95.3-r9 ~2.95.3-r10
	(3.1)	3.1.1-r2
	(3.2)	**3.2.2 3.2.3-r4
	(3.3)	~3.3.6-r1
	(3.4)	3.4.6-r2
	(4.0)	[M]~*4.0.3 [M]~*4.0.4
	(4.1)	[M]~4.1.0-r1 [M]4.1.1-r3 [M]4.1.2
	(4.2)	[M]~4.2.0 [M]~4.2.1 [M]~4.2.2

	{altivec bootstrap boundschecking build d doc fortran gcj gtk
	hardened ip28 ip32r10k java mudflap multilib multislot n32 n64
	nls nocxx nopie nossp objc objc++ objc-gc openmp static test
	vanilla}

  Installed versions: 3.4.6-r2(3.4)(14:36:31 01/02/08)(nls -altivec
  -bootstrap -boundschecking -build -d -doc -fortran -gcj -gtk
  -hardened -ip28 -ip32r10k -multilib -multislot -n32 -n64 -nocxx
  -nopie -nossp -objc -test -vanilla)

	  4.1.1-r3(4.1)(19:54:45 04/19/07)(fortran nls
	  -altivec -bootstrap -build -doc -gcj -gtk
	  -hardened -ip28 -ip32r10k -mudflap -multilib
	  -multislot -n32 -n64 -nocxx -objc -objc++
	  -objc-gc -test -vanilla)

=====================
Compile messages:  Including a few context lines
[...]


3: /usr/bin/cmp -s
/var/tmp/portage/app-shells/ksh-93.20040229/work/src/cmd/ksh93/fun/pushd
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/fun/pushd

3: /bin/mv
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/fun/pushd
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/fun/pushd.old

3: true

3: /bin/cp
/var/tmp/portage/app-shells/ksh-93.20040229/work/src/cmd/ksh93/fun/pushd
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/fun/pushd

3: chmod ugo+x
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/fun/pushd

mamake: *** exit code 1 making cmd/ksh93

package: make: errors making
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386/bin/ksh

package: make done at Mon Jan 7 13:39:31 CST 2008 in
/var/tmp/portage/app-shells/ksh-93.20040229/work/arch/linux.i386

 * 
 * ERROR: app-shells/ksh-93.20040229 failed.
 * Call stack:
 *                ebuild.sh, line 1701:  Called dyn_compile
 *                ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *                ebuild.sh, line   44:  Called src_compile
 *   ksh-93.20040229.ebuild, line   51:  Called die
 * The specific snippet of code:
 *   	cd ${S}; ./bin/package only make ast-ksh CC="$(tc-getCC)" ||
die
 *  The die message:
 *   (no error message)
 * 
 * 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/app-shells/ksh-93.20040229/temp/build.log'.
 * 
 * Messages for package app-shells/ksh-93.20040229:
 * 
 * ERROR: app-shells/ksh-93.20040229 failed.
 * Call stack:
 *                ebuild.sh, line 1701:  Called dyn_compile
 *                ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *                ebuild.sh, line   44:  Called src_compile
 *   ksh-93.20040229.ebuild, line   51:  Called die
 * The specific snippet of code:
 *   	cd ${S}; ./bin/package only make ast-ksh CC="$(tc-getCC)" ||
die
 *  The die message:
 *   (no error message)
 * 

 * 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/app-shells/ksh-93.20040229/temp/build.log'.

-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-07 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 20:52 Harry Putnam [this message]
2008-01-08  9:39 ` [gentoo-user] emerge of ksh93 erroring out.. who can interpret Alan McKinnon
2008-01-09  2:32   ` [gentoo-user] " reader
2008-01-10 19:34     ` Matthias B.
2008-01-11 17:18       ` reader
2008-01-11 18:26         ` Matthias B.
2008-01-11 18:56           ` reader
2008-01-11 21:41             ` Matthias B.
2008-01-14 15:38             ` Alex Schuster
2008-01-14 17:20               ` reader
2008-01-14 19:22                 ` Alex Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cr25o3pkcgo5mbtc92kg393b34bbj28ncq@4ax.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox