[arch-general] Issues compiling Jepp

Sergi Pons Freixes sachiel2014 at gmail.com
Mon Nov 7 04:11:35 EST 2011


Hi All,

I'm trying to install Jepp ( http://jepp.sourceforge.net/ ), but even after
talking with the developer we cannot get it right. So, I'm gonna try asking
here just in case somebody could give us some insight.

I have a Linux 3.0-ARCH #1 SMP PREEMPT  x86_64 Intel(R) Core(TM) i5-2500
CPU @3.30GHz GenuineIntel GNU/Linux

Using openjdk for java: openjdk6 6.b22_1.10.4-1
And Python 2.7: python2 2.7.2-2

Actually, my default Python is python 3.2.2-1, but as Jepp has not been
ported to Python 3, before beginning the installation procedure I do an
"export PYTHON=/usr/bin/python2", so it uses the path to the Python 2
binary (and libraries, as I can see on the logs).

So, there is no problem when running autogen.sh (automake 1.11.1-2 here),
and ./configure also runs ok. When doing the "make", it stalls with:
...
Making all in jep
make[3]: Entering directory `/home/sergi/installs/jep-2.4/src/jep'
/bin/sh ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
-I. -I../..   -I/usr/lib/jvm/java-6-openjdk/include
-I/usr/lib/jvm/java-6-openjdk/include/linux -I/usr/include/python2.7
-g -O2 -MT jep_object.lo -MD -MP -MF .deps/jep_object.Tpo -c -o
jep_object.lo `test -f 'python/jep_object.c' || echo
'./'`python/jep_object.c
mv -f .deps/jep_object.Tpo .deps/jep_object.Plo
mv: cannot stat `.deps/jep_object.Tpo': No such file or directory
make[3]: *** [jep_object.lo] Error 1
make[3]: Leaving directory `/home/sergi/installs/jep-2.4/src/jep'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/sergi/installs/jep-2.4/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/sergi/installs/jep-2.4'
make: *** [all] Error 2

Apart from that, I cannot glance any problem, missing dependency or warning
before, so no clue of why it's not building correctly. I've also tried with
other gcc versions, no luck. Mike Johnson, the developer of Jepp, pointed:
"That's weird, the -MF flag is passed to the compiler and gcc should have
written out that file."
and
"...any idea why that is. It must be a bug in autotools, you can try to
upgrade them.

Or you can manually make the .deps folder and an empty file for each one it
complains on. The dependency files are just make rules used to regenerate
just the changed objects if a source file changes. Unless you're changing
stuff, it won't matter..."

So... any suggestion?

Regards,
Sergi


More information about the arch-general mailing list