KDEBASE fails to compile (autom4te)

Message

RichieB · Post by **RichieB** » Thu Feb 05, 2004 12:32 pm

Upon emerging -u world and in kdebase3.2.0:

... blah ...

Good - your configure finished. Start make now

cd . && \
/bin/sh /var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/admin/missing --run automake-1.7 --foreign Makefile
cd . && rm -f configure
cd . && make -f admin/Makefile.common configure
make[1]: Entering directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0'
String found where operator expected at /usr/bin/autom4te-2.57 line 280, near "error "need GNU m4 1.4 or later: $m4""
(Do you need to predeclare error?)
syntax error at /usr/bin/autom4te-2.57 line 280, near "error "need GNU m4 1.4 or later: $m4""
BEGIN not safe after errors--compilation aborted at /usr/bin/autom4te-2.57 line 453.
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0'
make: *** [configure] Error 2
make: *** Waiting for unfinished jobs....
cd . && perl admin/am_edit Makefile.in
make: *** Waiting for unfinished jobs....

!!! ERROR: kde-base/kdebase-3.2.0 failed.
!!! Function kde_src_compile, Line 127, Exitcode 2
!!! died running emake, kde_src_compile:make

Anyone any ideas?

caleb · Post by **caleb** » Thu Feb 05, 2004 1:22 pm

Do me a favor; try this again but add a USE="-java" and see if that works:

USE="-java" emerge kdebase......

Klatu · Post by **Klatu** » Thu Feb 05, 2004 3:25 pm

Hi,

had the same problem.

USE="-java" emerge kdebase

didn't fix it...

RichieB · Post by **RichieB** » Thu Feb 05, 2004 3:33 pm

Yep. -java doesn't fix it. Woss going on?

msdn · Post by **msdn** » Thu Feb 05, 2004 3:52 pm

I had a similar problem, but error said that automake should be version 1.7.4. I emerged update for automake (1.8.x) and now it copiles. Try to emerge system, or automake and what automate and compile kde 3.2 again.

Hope it helps

SPiRiTs · Post by **SPiRiTs** » Thu Feb 05, 2004 4:01 pm

exactly same problem for me but with kdeadmin

any ideas ?

SPiRiT

Klatu · Post by **Klatu** » Thu Feb 05, 2004 4:16 pm

It hasn't finished compilation yet, but

quick'n'dirty I guess:

ln -s /usr/bin/autoXXXX-2.59 /usr/bin/autoXXXX-2.5x

for XXXX each of {conf|reconf|m4te|scan|header|update}

solved this for me.

I think you could also edit the detect-auconf.sh script in portage/kdebase-3.2.0/work/kdebase-3.2.0/admin to recognize autoXXXX-2.59 to solve this, but didn't try it.

wo0zy · Post by **wo0zy** » Thu Feb 05, 2004 6:29 pm

Klatu wrote:ln -s /usr/bin/autoXXXX-2.59 /usr/bin/autoXXXX-2.5x

what the x stands for?? i only have the 2.13 and 2.59 version

my problem is the same, but with kdelibs

no idea to solve this??

Klatu · Post by **Klatu** » Thu Feb 05, 2004 6:38 pm

wo0zy wrote:
Klatu wrote:ln -s /usr/bin/autoXXXX-2.59 /usr/bin/autoXXXX-2.5x
what the x stands for?? i only have the 2.13 and 2.59 version

simply for "x". No placeholder.

RichieB · Post by **RichieB** » Thu Feb 05, 2004 6:44 pm

Thanks for the suggestions of ln -s 'ing, but sounds more flaky than puff pastry. I'm not suggesting it won't work but that if I do it wrong there's more than a likely chance I'll bugger things up completely.

One wonders whether anyone can come up with a 'proper' solution?

Cheers!

Klatu · Post by **Klatu** » Fri Feb 06, 2004 1:12 pm

RichieB wrote:Thanks for the suggestions of ln -s 'ing, but sounds more flaky than puff pastry. I'm not suggesting it won't work but that if I do it wrong there's more than a likely chance I'll bugger things up completely.

I don't think that creating these links can cause any damage to your system.
The problem seems to be, that the script responsible for selecting the proper autom4te fails on using autom4te-2.59 for it only looks for autom4te-2.57 and autom4te-2.5x and lower versions. The links provide one quick solution.
And If you run into trouble, you can easily remove the links....

wo0zy · Post by **wo0zy** » Fri Feb 06, 2004 2:48 pm

i've made a complete new install but at the point when its time to choose an environment kde fails with the same errors

what the hell tis going on??

RichieB · Post by **RichieB** » Sun Feb 08, 2004 5:46 pm

Well, I bit this bitter 'ln' fruit and so far it's still compiling (certainly past the point it failed last time.)

It's just a shame that one has to hack.

Then again, this is Gentoo

vlack · Post by **vlack** » Tue Feb 10, 2004 8:28 pm

This doesn't work for me

I have the latest versions of automake and autoconf. I did your ln -s magic. And the KDE compile still fails with the same errors as before. (Similar to the errors at the beginning of this thread; my errors are documented here: http://forums.gentoo.org/viewtopic.php? ... highlight=).

USE="-java", latest versions, very conservative CFLAGS, etc. Anything else I can try?

Klatu · Post by **Klatu** » Tue Feb 10, 2004 9:59 pm

Your problem is different, for your compiler segfaults. Which version of gcc do you use? What are your CFLAGS?
I had no problems compiling kdelibs with gcc 3.3.2 and

Code: Select all

CFLAGS="-march=athlon-xp -O2 -falign-functions=4
-falign-jumps=4 -fomit-frame-pointer -pipe"

Hope it helps

d-fens · Post by **d-fens** » Thu Feb 12, 2004 3:00 pm

Code: Select all

make[1]: Entering directory `/var/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0'
String found where operator expected at /usr/bin/autom4te-2.57 line 280, near "error "need GNU m4 1.4 or later: $m4""
        (Do you need to predeclare error?)
syntax error at /usr/bin/autom4te-2.57 line 280, near "error "need GNU m4 1.4 or later: $m4""
BEGIN not safe after errors--compilation aborted at /usr/bin/autom4te-2.57 line 453.
make[1]: *** [configure] Fehler 1

tried everything, CFLAGS (no segfault anyway), ln -s stuff, changed the ac/am-wrapper, nothing...

autoconf 2.59
automake 1.8.2
gcc-Version 3.3.2 20031218

*desperate*

caleb · Post by **caleb** » Thu Feb 12, 2004 3:51 pm

Try and "emerge -c" and make sure your autoconf/automake is clean of older versions.

Then I would do an "emerge clean kdelibs" or whatever kde package you were trying to install, and try to re-install it.

d-fens · Post by **d-fens** » Thu Feb 12, 2004 4:36 pm

>>> No outdated packages were found on your system.
...
>>> clean: No packages selected for removal.

edit:WOOOHOOOO!!!

i emerged every single version of autoconf/make beginning with the oldest and hoped to remove some lost fragments of outdated packages - SOLVED!!!!

strange thing that portage was thinking that there was nothing left!
thx caleb for support =)

pvincent · Post by **pvincent** » Tue Feb 17, 2004 7:20 pm

same trouble.
To fix it, I had to emerge again autoconf-2.57-r1, and then unmerge it.

Code: Select all

	emerge /usr/portage/sys-devel/autoconf/autoconf-2.57-r1.ebuild
	emerge sys-devel/autoconf-2.57-r1 -C

At the end, the script /usr/bin/autom4te-2.57 no longer exists.
Hope it could help...

Moloch · Post by **Moloch** » Thu Feb 19, 2004 6:38 pm

pvincent wrote:same trouble.
To fix it, I had to emerge again autoconf-2.57-r1, and then unmerge it.
Code: Select all
	emerge /usr/portage/sys-devel/autoconf/autoconf-2.57-r1.ebuild
	emerge sys-devel/autoconf-2.57-r1 -C
At the end, the script /usr/bin/autom4te-2.57 no longer exists.
Hope it could help...

This problem has been killing me. No problems on my main comp, but my slower one, which really needs the faster kde3.2 kept getting the error. You found the fix my friend. Thanks!

Crashed_Again · Post by **Crashed_Again** » Tue Feb 24, 2004 4:00 am

Okay I tried this and it did not work as well. emerge kdebase re-install autoconf and causes the same error.

Can't we get an official answer on this bug?

alaa · Post by **alaa** » Tue Feb 24, 2004 3:45 pm

I had the same problem and was told that the solution is there:

http://forums.gentoo.org/viewtopic.php? ... &start=375

I followed the instructions there and it worked for me.

The gist of it is to re-emerge libsdl, and kdebase-3.2.0 should start compiling. The reason is that libsdl was probably emerged with gcc 3.2, and now it will be compiled with gcc 3.3 and that fixes it.

leftbas · Post by **leftbas** » Tue Feb 24, 2004 6:15 pm

Try this guys...

- Emerge qt-3.3.0
- Emerge arts
- Emerge kdelibs
- Emerge kdebas

In this order, everything emerged without any errors and now I'm running KDE 3.2...without any of the other pakages, tho. I'll emerge them when I take my machine home from work tonight.

Good luck, hope it helps everyone.

Luda · Post by **Luda** » Tue Feb 24, 2004 10:40 pm

pvincent wrote:same trouble.
To fix it, I had to emerge again autoconf-2.57-r1, and then unmerge it.
Code: Select all
	emerge /usr/portage/sys-devel/autoconf/autoconf-2.57-r1.ebuild

	emerge sys-devel/autoconf-2.57-r1 -C
At the end, the script /usr/bin/autom4te-2.57 no longer exists.
Hope it could help...

leftbas wrote:Try this guys...

- Emerge arts

Good luck, hope it helps everyone.

It is compiling! WOOHOOO!
Kdebase is compiling!

I *love* you guys!

Crashed_Again · Post by **Crashed_Again** » Wed Feb 25, 2004 8:11 am

Okay I haven't had any luck with this. Any applcation that is remotely related to kde fails to compile as well. I've tried re-emerging libsdl. I've tried re-emerging every version of autoconf and automake. I've tried emerging in this order:

- Emerge qt-3.3.0
- Emerge arts
- Emerge kdelibs
- Emerge kdebas

Nothing is working for me. I feel like such a noob. I need a step by step on how to resolve this issue. Any help would be appreciated.

P.S. At this point I'm interested in exactly what the problem is too. Whatever is responsible for this issue should die a nasty death!

KDEBASE fails to compile (autom4te)

KDEBASE fails to compile (autom4te)

-java doesn't fix

Come on, people

Re: Come on, people

Bitter logic

still not working here

autom4te.2-57 syntax error

Re: autom4te.2-57 syntax error