[gentoo-user] AbiWord 2.6.4 build failure

[gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

[-- Attachment #1: Type: text/plain, Size: 3661 bytes --]

Dear Gentoo users,

The latest Portage-stable AbiWord refuses to compile on my system, with
either + or -gnome. (Currently I have the old 2.4.6 fully functional.) I am
in the process of an emerge world, so all the dependencies of AbiWord are
already up-to-date, plus several were rebuilt recently (like goffice). Not
sure whether necessary, but ./.configure complained, so I installed
dev-util/valgrind. I also tried this suggestion by CJoeB, to re-emerge
XML-Parser, but to no avail. Below you will find the messages towards the
error.

Could anyone suggest a work around? Thank you,
Liviu

x11-libs/goffice
0.4.3(0.4)(17:42:58 18/10/08)(-debug -doc -gnome)
0.6.4(0.6)(20:33:23 19/08/08)(-debug -doc -gnome)



################## Build debug ##################
mv -f .deps/xap_Dlg_ListDocuments.Tpo .deps/xap_Dlg_ListDocuments.Po
mv -f .deps/xap_Dlg_History.Tpo .deps/xap_Dlg_History.Po
mv -f .deps/xap_Dlg_DocComparison.Tpo .deps/xap_Dlg_DocComparison.Po
rm -f libXap_xp.a
ar cru libXap_xp.a xap_Dlg_Print.o xap_Dlg_PrintPreview.o xad_Document.o
xap_App.o xap_AppImpl.o xap_Args.o xap_Clipboard.o xap_Dialog.o
xap_DialogFactory.o xap_Dictionary.o xap_Dlg_About.o xap_Dlg_ClipArt.o
xap_Dlg_FileOpenSaveAs.o xap_Dlg_FontChooser.o xap_Dlg_HTMLOptions.o
xap_Dlg_Language.o xap_Dlg_Image.o xap_Dlg_MessageBox.o xap_Dlg_Password.o
xap_Dlg_PluginManager.o xap_Dlg_WindowMore.o xap_Dlg_Zoom.o
xap_Dlg_Insert_Symbol.o xap_Dlg_Encoding.o xap_FakeClipboard.o
xap_FontPreview.o xap_Frame.o xap_FrameImpl.o xap_InputModes.o
xap_LoadBindings.o xap_Log.o xap_Module.o xap_ModuleManager.o xap_Prefs.o
xap_Preview.o xap_Preview_Zoom.o xap_Draw_Symbol.o
xap_Scrollbar_ViewListener.o xap_Strings.o xap_StatusBar.o
xap_Toolbar_ControlFactory.o xap_ViewListener.o xav_View.o
xap_EncodingManager.o xap_Dlg_ListDocuments.o xap_Dlg_History.o
xap_Dlg_DocComparison.o
i686-pc-linux-gnu-ranlib libXap_xp.a
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 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'.
*
################## End of build debug ##################




On Sat, Feb 9, 2008 at 2:59 PM, CJoeB <colleen.beamer@gmail.com> wrote:
>>> Why all of a sudden can't I compile goffice without gnome?
>>>
>
> Thanks, not necessary.  I think I solved it.  I just re-emerged
> XML-Parser. and things seem to be okay.
>

[-- Attachment #2: Type: text/html, Size: 4312 bytes --]

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Fabrice Delliaux]

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 ?

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2035 bytes --]

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Arttu V.]

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.

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Alan McKinnon]

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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2895 bytes --]

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Daniel Pielmeier]

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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Alan McKinnon]

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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

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
#################

[-- Attachment #2: Type: text/html, Size: 2462 bytes --]

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Walter Dnes]

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>

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

On Tue, Oct 21, 2008 at 1:17 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>  MAKEOPTS="-j1"
>
I tried both MAKEOPTS="-j1" and #MAKEOPTS="-j1", with +gnome and -gnome, to no avail; it errors at the same spot:
"GNUmakefile:964: *** mixed implicit and normal rules.  Stop."

I will post below the configuration options reported by Portage; perhaps it contains clues. 
Liviu


####################
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-debug --disable-symbols --disable-gnomeui --disable-gucharmap --disable-gnomevfs --enable-spellcheck --with-libxml2 --without-expat --disable-libabiword --enable-printing --enable-threads --disable-scripting --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for library containing strerror... none required
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking CFLAGS... -O2 -march=pentium-m -pipe -fomit-frame-pointer
checking CXXFLAGS... -O2 -march=pentium-m -pipe -fomit-frame-pointer
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for long int... yes
checking size of long int... 4
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for printing support... true
checking for GLIB... yes
checking for GMODULE... yes
checking for GTHREAD... yes
checking for GTK... yes
checking for PANGOFT2... yes
checking for X... libraries , headers 
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for GNOMEPRINT... yes
checking for FREETYPE... yes
checking whether binary relocation support should be enabled... no
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking for XFT... yes
checking for GSF... yes
checking for GSF_HTTP... yes
checking for GOFFICE... yes
checking for SPELL... yes
checking for FRIBIDI... yes
checking for ANSI C header files... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for strings.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking for xml2-config... /usr/bin/xml2-config
checking for WV... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for LIBPNG... yes
checking popt.h usability... yes
checking popt.h presence... yes
checking for popt.h... yes
checking for libjpeg
checking for jpeg_start_decompress in -ljpeg... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for working alloca.h... yes
checking for alloca... yes
checking return type of signal handlers... void
checking whether scandir select requires const struct dirent... yes
checking for valgrind... valgrind
checking valgrind/memcheck.h usability... yes
checking valgrind/memcheck.h presence... yes
checking for valgrind/memcheck.h... yes
configure: creating ./config.status
config.status: creating goffice-bits/GNUmakefile
config.status: creating abiword.pc
config.status: creating libabiword.pc
config.status: creating GNUmakefile
config.status: creating src/GNUmakefile
config.status: creating src/af/GNUmakefile
config.status: creating src/af/tf/GNUmakefile
config.status: creating src/af/ev/GNUmakefile
config.status: creating src/af/ev/xp/GNUmakefile
config.status: creating src/af/ev/cocoa/GNUmakefile
config.status: creating src/af/ev/qnx/GNUmakefile
config.status: creating src/af/ev/unix/GNUmakefile
config.status: creating src/af/ev/unix/gnome/GNUmakefile
config.status: creating src/af/ev/win/GNUmakefile
config.status: creating src/af/gr/GNUmakefile
config.status: creating src/af/gr/xp/GNUmakefile
config.status: creating src/af/gr/cocoa/GNUmakefile
config.status: creating src/af/gr/unix/GNUmakefile
config.status: creating src/af/gr/qnx/GNUmakefile
config.status: creating src/af/gr/win/GNUmakefile
config.status: creating src/af/util/GNUmakefile
config.status: creating src/af/util/xp/GNUmakefile
config.status: creating src/af/util/xp/t/GNUmakefile
config.status: creating src/af/util/unix/GNUmakefile
config.status: creating src/af/util/qnx/GNUmakefile
config.status: creating src/af/util/win/GNUmakefile
config.status: creating src/af/tf/xp/GNUmakefile
config.status: creating src/af/xap/GNUmakefile
config.status: creating src/af/xap/xp/GNUmakefile
config.status: creating src/af/xap/cocoa/GNUmakefile
config.status: creating src/af/xap/qnx/GNUmakefile
config.status: creating src/af/xap/win/GNUmakefile
config.status: creating src/af/xap/unix/GNUmakefile
config.status: creating src/af/xap/unix/t/GNUmakefile
config.status: creating src/af/xap/unix/hildon/GNUmakefile
config.status: creating src/config/GNUmakefile
config.status: creating src/config/platforms/GNUmakefile
config.status: creating src/config/require/GNUmakefile
config.status: creating src/config/require/win/GNUmakefile
config.status: creating src/other/GNUmakefile
config.status: creating src/other/spell/GNUmakefile
config.status: creating src/other/spell/xp/GNUmakefile
config.status: creating src/pkg/GNUmakefile
config.status: creating src/pkg/maemo/GNUmakefile
config.status: creating src/pkg/maemo/abiword.desktop
config.status: creating src/pkg/maemo/com.abisource.abiword.service
config.status: creating src/pkg/maemo/debian/GNUmakefile
config.status: creating src/text/GNUmakefile
config.status: creating src/text/fmt/GNUmakefile
config.status: creating src/text/fmt/xp/GNUmakefile
config.status: creating src/text/fmt/unix/GNUmakefile
config.status: creating src/text/ptbl/GNUmakefile
config.status: creating src/text/ptbl/xp/GNUmakefile
config.status: creating src/text/ptbl/xp/t/GNUmakefile
config.status: creating src/wp/GNUmakefile
config.status: creating src/wp/ap/GNUmakefile
config.status: creating src/wp/ap/xp/GNUmakefile
config.status: creating src/wp/ap/cocoa/GNUmakefile
config.status: creating src/wp/ap/qnx/GNUmakefile
config.status: creating src/wp/ap/unix/GNUmakefile
config.status: creating src/wp/ap/unix/hildon/GNUmakefile
config.status: creating src/wp/ap/win/GNUmakefile
config.status: creating src/wp/ap/win/ToolbarIcons/GNUmakefile
config.status: creating src/wp/impexp/GNUmakefile
config.status: creating src/wp/impexp/cocoa/GNUmakefile
config.status: creating src/wp/impexp/unix/GNUmakefile
config.status: creating src/wp/impexp/qnx/GNUmakefile
config.status: creating src/wp/impexp/win/GNUmakefile
config.status: creating src/wp/impexp/xp/GNUmakefile
config.status: creating src/wp/main/GNUmakefile
config.status: creating src/wp/main/xp/GNUmakefile
config.status: creating src/wp/main/cocoa/GNUmakefile
config.status: creating src/wp/main/cocoa/bundle/GNUmakefile
config.status: creating src/wp/main/cocoa/bundle/Info.plist
config.status: creating src/wp/main/cocoa/AbiWord.app/GNUmakefile
config.status: creating src/wp/main/cocoa/AbiWord.app/Contents/GNUmakefile
config.status: creating src/wp/main/cocoa/AbiWord.app/Contents/MacOS/GNUmakefile
config.status: creating src/wp/main/cocoa/AbiWord.app/Contents/Frameworks/GNUmakefile
config.status: creating src/wp/main/cocoa/AbiWord.app/Contents/Resources/GNUmakefile
config.status: creating src/wp/main/cocoa/AbiWord.app/Contents/Resources/English.lproj/GNUmakefile
config.status: creating src/wp/main/qnx/GNUmakefile
config.status: creating src/wp/main/unix/GNUmakefile
config.status: creating src/wp/main/win/GNUmakefile
config.status: creating src/wp/test/GNUmakefile
config.status: creating src/wp/test/xp/GNUmakefile
config.status: creating src/wp/test/unix/GNUmakefile
config.status: creating src/wp/test/unix/testwrap.sh
config.status: creating src/wp/test/win/GNUmakefile
config.status: creating src/wp/test/win/testwrap.sh
config.status: creating src/wp/test/cocoa/GNUmakefile
config.status: creating src/tools/GNUmakefile
config.status: creating src/tools/cdump/GNUmakefile
config.status: creating src/tools/cdump/xp/GNUmakefile
config.status: creating src/tools/po2str/GNUmakefile
config.status: creating src/tools/po2str/xp/GNUmakefile
config.status: creating src/tools/scripts/GNUmakefile
config.status: creating src/tools/scripts/unix/GNUmakefile
config.status: creating src/bindings/GNUmakefile
config.status: creating src/bindings/perl/GNUmakefile
config.status: creating src/bindings/perl/examples/GNUmakefile
config.status: creating user/GNUmakefile
config.status: creating user/wp/GNUmakefile
config.status: creating user/wp/scripts/GNUmakefile
config.status: creating user/wp/strings/GNUmakefile
config.status: creating user/wp/templates/GNUmakefile
config.status: executing depfiles commands
 
Configured to build on a Unix/Linux platform.
Configured with printing capabilities.
Configured with XFT support.
 
  XML Parser:             libxml2 in -lxml2 -lz -lm
  zlib:                   zlib in -lz
  PNG Library:            libpng in -lpng12  
  popt:	                  libpopt in -lpopt
  WV Library:             -lwv -lwmf -lwmflite -lfreetype -lX11 -ljpeg -lgsf-1 -lgobject-2.0 -lxml2 -lglib-2.0 -lpng -lz -lm  
  iconv:                  system iconv
  spelling:               enchant
  goffice:                system
  gnome-vfs:              no (as requested)
  gnome-ui:               no (as requested)
  libabiword:             no
  binreloc:               no

  installing in:          /usr
#############



-- 
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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Fabrice Delliaux]

Le Tue, 21 Oct 2008 11:21:37 +0200,
Liviu Andronic a écrit :

> "GNUmakefile:964: *** mixed implicit and normal rules.  Stop."

Can you please upload this Makefile somewhere and give us a link for
download ? Something in your build environment is probably interfering
with some variables defined in this Makefile.

And also : somewhere in /var/tmp/portage/app-office/abiword you should
have a file called *environment* or *environment.bz2*

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

Hello,


On Tue, Oct 21, 2008 at 12:23 PM, Fabrice Delliaux <netfab@gmail.com> wrote:
> Can you please upload this Makefile somewhere and give us a link for
> download ? Something in your build environment is probably interfering
> with some variables defined in this Makefile.
>
> And also : somewhere in /var/tmp/portage/app-office/abiword you should
> have a file called *environment* or *environment.bz2*
>
I've just uploaded the two files:
Makefile: http://s000.tinyupload.com/index.php?file_id=02299843822915416335
Environment: http://s000.tinyupload.com/index.php?file_id=05207412456599355087

I also added "emerge --info" output below.
Liviu

################################
localhost liviu # emerge --info
Portage 2.1.4.4 (default/linux/x86/2008.0/desktop, gcc-4.1.2,
glibc-2.6.1-r0, 2.6.22-gentoo-r5-0.2 i686)
=================================================================
System uname: 2.6.22-gentoo-r5-0.2 i686 Intel(R) Pentium(R) M processor 1.60GHz
Timestamp of tree: Sun, 05 Oct 2008 01:45:04 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p33
dev-java/java-config: 1.3.7, 2.1.6-r1
dev-lang/python:     2.5.2-r7
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r2
sys-devel/automake:  1.4_p6, 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d
/etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild
/etc/splash /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache collision-protect distlocks metadata-transfer
parallel-fetch sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="en_GB.UTF-8"
LC_ALL="en_GB.UTF-8"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac aalib acl acpi aiglx alsa amr audiofile bash-completion
bitmap-fonts bluetooth branding bzip2 cairo cdda cddb cdparanoia cdr
cli cracklib crypt cups dbus ddloader directfb dri dvd dvdr dvdread
encode fam flac fortran gdbm gif gnome gpm gstreamer gtk hal iconv
imagemagick ipv6 isdnlog javascript jpeg kerberos kpathsea lame ldap
libcaca libnotify lyx mad matroska midi mmx mp3 mpeg mudflap ncurses
nls nptl nptlonly nsplugin ogg opengl openmp pam pcre pdf perl png
ppds pppd python qt3 qt3support qt4 quicktime readline reflection
scanner sdl seamonkey session slang spell spl sqlite sse sse2 ssl
startup-notification svg sysfs tcpd texlive threads tiff truetype
truetype-fonts type1-fonts unicode usb vcd vidix vorbis wifi
win32codecs wmf x264 x86 xfce xml 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
mmap_emul mulaw multi null plug rate route share shm softvol"
APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon
authn_dbm authn_default authn_file authz_dbm authz_default
authz_groupfile authz_host authz_owner authz_user autoindex cache dav
dav_fs dav_lock deflate dir disk_cache env expires ext_filter
file_cache filter headers include info log_config logio mem_cache mime
mime_magic negotiation rewrite setenvif speling status unique_id
userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard
mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz
cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
LIRC_DEVICES="all" USERLAND="GNU" VIDEO_CARDS="i810 vesa fbdev v4l"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK,
LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS,
PORTAGE_RSYNC_EXTRA_OPTS
################################



-- 
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

(http://s000.tinyupload.com/?del_id=96046955341935787829
http://s000.tinyupload.com/index.php?del_id=08873273853539429570)

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Fabrice Delliaux]

Hi,

Thanks for the links.


Le Wed, 22 Oct 2008 12:09:22 +0200,
Liviu Andronic a écrit :

> I've just uploaded the two files:
> Makefile:
> http://s000.tinyupload.com/index.php?file_id=02299843822915416335

You probably upload the wrong file. This can't be this one.


But I think I found the problem, and it seems to be a bug : make is
actually failing on this line in the Makefile :

> /* -*- mode: C++; tab-width: 4; c-basic-offset: 4; -*- */


Can you please run the following commands to copy the ebuild to an
overlay ( assuming /usr/local/portage is the overlay ) :

 # cd /usr/local/portage
 # mkdir -p app-office/abiword/files
 # cd app-office/abiword
 # cp /usr/portage/app-office/abiword/abiword/abiword-2.6.4.ebuild .

Then, edit abiword.2.6.4.ebuild, and add the following src_unpack
function :

> src_unpack() {
>	unpack ${A}
>	cd "${S}"
>
>	epatch ${FILESDIR}/fix-build.patch
> }

Download the fix-build.patch from here to /tmp/fix-build.patch :

	http://s000.tinyupload.com/index.php?file_id=39475871613771688451

Finally run :

 # cd /usr/local/portage/app-office/abiword
 # cp /tmp/fix-build.patch files/
 # ebuild abiword.2.6.4.ebuild digest
 # emerge =abiword-2.6.4


If it fix the problem, you should open a bug at http://bugs.gentoo.org,
with your emerge --info, the build log when it fails, and the patch.

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

Hello Fabrice,

Thanks for taking a look, and for the patch.

On Wed, Oct 22, 2008 at 2:24 PM, Fabrice Delliaux <netfab@gmail.com> wrote:
>> Makefile:
>> http://s000.tinyupload.com/index.php?file_id=02299843822915416335
>
> You probably upload the wrong file. This can't be this one.
>
I also have a GNUmakefile [3] file. Perhaps this is the one.


> If it fix the problem, you should open a bug at http://bugs.gentoo.org,
> with your emerge --info, the build log when it fails, and the patch.
>
Unfortunately it did not, and failed at the exact same spot:
"GNUmakefile:964: *** mixed implicit and normal rules.  Stop.". Here
are the tweaked ebuild [2] that I used, and the GNUmakefile [3]. The
funny thing about the error message, concerning [3], I suppose, is
that the file has no "964" line. It ends at 886.

[2] http://s000.tinyupload.com/index.php?file_id=69162862283435311671
[3] http://s000.tinyupload.com/index.php?file_id=65647828039080848641

Is there other information that could be of help?
Liviu


##################
localhost dwn # emerge -va =abiword-2.6.4
[..]
[ebuild     U ] app-office/abiword-2.6.4 [2.4.6] USE="spell xml -debug
-gnome" 0 kB [0=>1]      ### It's well taking the local overlay ebuild
[..]
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/portage
[..]
>>> Unpacking abiword-2.6.4.tar.gz to /var/tmp/portage/app-office/abiword-2.6.4/work
 * Applying fix-build.patch ...

        [ ok ]    ###second confirmation
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/app-office/abiword-2.6.4/work/abiword-2.6.4 ...
./configure --prefix=/usr --host=i686-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --disable-debug
--disable-symbols --disable-gnomeui --disable-gucharmap
--disable-gnomevfs --enable-spellcheck --with-libxml2 --without-expat
--disable-libabiword --enable-printing --enable-threads
--disable-scripting --build=i686-pc-linux-gnu
##################






-- 
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

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Fabrice Delliaux]

Le Wed, 22 Oct 2008 20:45:14 +0200,
Liviu Andronic a écrit :
> and the GNUmakefile [3]. The
> funny thing about the error message, concerning [3], I suppose, is
> that the file has no "964" line. It ends at 886.
> 
> [3] http://s000.tinyupload.com/index.php?file_id=65647828039080848641

This upload failed again :)

I know why my previous patch didn't do it's job : the abiword ebuild
doesn't run eautoreconf.

Please try again with the following new patch (replace the older one
with it) :

	http://s000.tinyupload.com/index.php?file_id=66058338642413078582

Re: [gentoo-user] AbiWord 2.6.4 build failure

[Liviu Andronic]

On Wed, Oct 22, 2008 at 10:25 PM, Fabrice Delliaux <netfab@gmail.com> wrote:
> Please try again with the following new patch (replace the older one
> with it) :
>
Worked like a charm. Please see the relevant bug report [1].
Liviu

[1] http://bugs.gentoo.org/show_bug.cgi?id=243448