Le Sat, 18 Oct 2008 20:20:49 +0200,
Liviu Andronic a écrit :

> Could anyone suggest a work around?

What's the content of your make.conf please ?

On Sat, Oct 18, 2008 at 9:34 PM, Fabrice Delliaux <netfab@gmail.com> wrote:

What's the content of your make.conf please ?



# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer"

CXXFLAGS="${CFLAGS}"

CHOST="i686-pc-linux-gnu"
MAKEOPTS="-j3"
FEATURES="sandbox ccache userfetch parallel-fetch collision-protect"
PORTAGE_NICENESS="15"

#PORTAGE_TMPDIR=/tmp
PORTDIR_OVERLAY="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"

#Xorg specific
INPUT_DEVICES="keyboard mouse synaptics evdev"
VIDEO_CARDS="i810 vesa fbdev v4l"


#lirc specific
#LIRC_DEVICES="-devinput -inputlirc -parallel -serial sir"
LIRC_DEVICES="all"

USE="-arts -berkdb -emboss -kde -mikmod audiofile -motif slang flac
* -theora vcd a52 aac xvid mmx imagemagick vidix tiff bzip2

* bash-completion wmf sse sse2 -esd cdda cddb dvd -speex -physfs
* bitmap-fonts truetype-fonts type1-fonts svg aiglx wifi lame
* threads x264 matroska vorbis -xinerama nsplugin -xosd amr _javascript_

* dri hal ddloader scanner libnotify libcaca aalib pdf sqlite texlive
* lyx kpathsea directfb seamonkey -firefox -eds xfce -evo cdparanoia"

#SANE_BACKENDS="the_name_of_your_backend_goes_here "


#source /usr/local/portage/layman/make.conf

PORTAGE_ELOG_SYSTEM="save save_summary echo"
PORTAGE_ELOG_CLASSES="warn error info log"


Liviu

On 10/18/08, Liviu Andronic <landronimirc@gmail.com> wrote:
> PORTDIR_OVERLAY="/usr/portage"
> PORTDIR_OVERLAY="/usr/local/portage"

I don't really know an answer, but I'm curious about what has been
attempted with these two lines. Would it work better without overlays,
i.e., by commenting these two out?

--
Arttu V.

On Sunday 19 October 2008 12:59:35 Arttu V. wrote:
> On 10/18/08, Liviu Andronic <landronimirc@gmail.com> wrote:
> > PORTDIR_OVERLAY="/usr/portage"
> > PORTDIR_OVERLAY="/usr/local/portage"
>
> I don't really know an answer, but I'm curious about what has been
> attempted with these two lines. Would it work better without overlays,
> i.e., by commenting these two out?

Only the second one will take effect.

--
alan dot mckinnon at gmail dot com

On Sun, Oct 19, 2008 at 12:59 PM, Arttu V. <arttuv69@gmail.com> wrote:

On 10/18/08, Liviu Andronic <landronimirc@gmail.com> wrote:

> PORTDIR_OVERLAY="/usr/portage"

> PORTDIR_OVERLAY="/usr/local/portage"



I don't really know an answer, but I'm curious about what has been

attempted with these two lines. Would it work better without overlays,

i.e., by commenting these two out?


Well, doing so (#PORTDIR_OVERLAY="/usr/local/portage") I did get a different error message. Same spot, but now Portage tells me:

################## Build debug ##################

**
** ERROR: app-office/abiword-2.6.4 failed.
** Call stack:
**************** ebuild.sh, line** 49:* Called src_compile
************** environment, line 3299:* Called gnome2_src_compile
************** environment, line 2312:* Called die

** The specific snippet of code:
******** emake || die "compile failure"
*** The die message:
**** compile failure
**
** 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-office/abiword-2.6.4/temp/build.log'.
** The ebuild environment file is located at '/var/tmp/portage/app-office/abiword-2.6.4/temp/environment'.

** This ebuild used the following eclasses from overlays:
**** /usr/portage/eclass/alternatives.eclass
**** /usr/portage/eclass/eutils.eclass
**** /usr/portage/eclass/multilib.eclass
**** /usr/portage/eclass/toolchain-funcs.eclass

**** /usr/portage/eclass/portability.eclass
**** /usr/portage/eclass/gnome2.eclass
**** /usr/portage/eclass/fdo-mime.eclass
**** /usr/portage/eclass/libtool.eclass
**** /usr/portage/eclass/gnome.org.eclass

**** /usr/portage/eclass/gnome2-utils.eclass
**** /usr/portage/eclass/versionator.eclass
**
################## End of build debug ##################

Ideas, anyone?
Liviu

Liviu Andronic schrieb am 19.10.2008 16:51:
> On Sun, Oct 19, 2008 at 12:59 PM, Arttu V. <arttuv69@gmail.com> wrote:
>
>> On 10/18/08, Liviu Andronic <landronimirc@gmail.com> wrote:
>>> PORTDIR_OVERLAY="/usr/portage"
>>> PORTDIR_OVERLAY="/usr/local/portage"
>> I don't really know an answer, but I'm curious about what has been
>> attempted with these two lines. Would it work better without overlays,
>> i.e., by commenting these two out?
>>
>> Well, doing so (#PORTDIR_OVERLAY="/usr/local/portage") I did get a
> different error message. Same spot, but now Portage tells me:
>
> ################## Build debug ##################
> *
> * ERROR: app-office/abiword-2.6.4 failed.
> * Call stack:
> * ebuild.sh, line 49: Called src_compile
> * environment, line 3299: Called gnome2_src_compile
> * environment, line 2312: Called die
> * The specific snippet of code:
> * emake || die "compile failure"
> * The die message:
> * compile failure
> *
> * 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-office/abiword-2.6.4/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/app-office/abiword-2.6.4/temp/environment'.
> * This ebuild used the following eclasses from overlays:
> * /usr/portage/eclass/alternatives.eclass
> * /usr/portage/eclass/eutils.eclass
> * /usr/portage/eclass/multilib.eclass
> * /usr/portage/eclass/toolchain-funcs.eclass
> * /usr/portage/eclass/portability.eclass
> * /usr/portage/eclass/gnome2.eclass
> * /usr/portage/eclass/fdo-mime.eclass
> * /usr/portage/eclass/libtool.eclass
> * /usr/portage/eclass/gnome.org.eclass
> * /usr/portage/eclass/gnome2-utils.eclass
> * /usr/portage/eclass/versionator.eclass
> *
> ################## End of build debug ##################
>
> Ideas, anyone?
> Liviu
>

Where is your portage tree stored? In /usr/portage I guess, so remove
this PORTDIR_OVERLAY="/usr/portage" or replace it with
PORTDIR="/usr/portage" but this is not needed as it is default.
Regarding PORTDIR_OVERLAY="/usr/local/portage" if you have overlays
there you should remove the # comment. I suggest you to read this [1]
and the portage man pages again carefully.

Also the build logs you have posted are completely useless, as the do
not really show the error messages which may trigger this errors.

[1]
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full=1#book_part3

On Sunday 19 October 2008 16:51:32 Liviu Andronic wrote:
> On Sun, Oct 19, 2008 at 12:59 PM, Arttu V. <arttuv69@gmail.com> wrote:
> > On 10/18/08, Liviu Andronic <landronimirc@gmail.com> wrote:
> > > PORTDIR_OVERLAY="/usr/portage"
> > > PORTDIR_OVERLAY="/usr/local/portage"
> >
> > I don't really know an answer, but I'm curious about what has been
> > attempted with these two lines. Would it work better without overlays,
> > i.e., by commenting these two out?
> >
> > Well, doing so (#PORTDIR_OVERLAY="/usr/local/portage") I did get a
>
> different error message. Same spot, but now Portage tells me:
>
> ################## Build debug ##################
> *
> * ERROR: app-office/abiword-2.6.4 failed.
> * Call stack:
> * ebuild.sh, line 49: Called src_compile
> * environment, line 3299: Called gnome2_src_compile
> * environment, line 2312: Called die
> * The specific snippet of code:
> * emake || die "compile failure"
> * The die message:
> * compile failure
> *
> * If you need support, post the topmost build error, and the call stack if
> relevant.
^^^^^^^

You did not do this. You posted the bottommost error.

With the information you supplied it is not possible to assist you in any
meaningful way.


--
alan dot mckinnon at gmail dot com

On 10/19/08, Daniel Pielmeier <daniel.pielmeier@googlemail.com> wrote:
> Where is your portage tree stored? In /usr/portage I guess, so remove
> this PORTDIR_OVERLAY="/usr/portage" or replace it with
> PORTDIR="/usr/portage" but this is not needed as it is default.
> Regarding PORTDIR_OVERLAY="/usr/local/portage" if you have overlays
> there you should remove the # comment. I suggest you to read this [1]
> and the portage man pages again carefully.
>
Thank you for the hints.
Liviu

--
--- Do you know how to read? http://www.alienetworks.com/srtest.cfm Do
you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

On 10/19/08, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>>* * If you need support, post the topmost build error, and the call stack
>> if

>> relevant.
>*********************************** ^^^^^^^
>
> You did not do this. You posted the bottommost error.
>
Well, the error message essentially didn't change from my first posting, so the second time I posted only the diff. Below is the topmost error; if not, please tell me how you would expect it to be.


Thank you,
Liviu

################
make[4]: Leaving directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/xp'
Making all in unix
make[4]: Entering directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/unix'

GNUmakefile:964: *** mixed implicit and normal rules.* Stop.
make[4]: Leaving directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap/unix'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af/xap'

make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src/af'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4/src'

make: *** [all-recursive] Error 1
**
** ERROR: app-office/abiword-2.6.4 failed.
** Call stack:
**************** ebuild.sh, line** 49:* Called src_compile
************** environment, line 3298:* Called gnome2_src_compile

************** environment, line 2311:* Called die
** The specific snippet of code:
******** emake || die "compile failure"
*** The die message:
**** compile failure
#################

On Sat, Oct 18, 2008 at 09:56:48PM +0300, Liviu Andronic wrote

> MAKEOPTS="-j3"

Change this to...

MAKEOPTS="-j1"

and re-run the build. You'd be surprised how often that is the problem.
I run MAKEOPTS="-j1" on a Core Duo. It takes a few minutes longer than
-j3 to update world, but it only takes one crash during a build at -j2
or -j3 to destroy any time that you "save". I know I'm being more
conservative than the Gentoo handbook, but the smoother builds are worth
it. And no, the -j option does *NOT* affect the speed of the binary
that you've built.

--
Walter Dnes <waltdnes@waltdnes.org>