Ah, ok. I'd completely missed that part since you mentioned having built
7.8.
Just as a bit of information, the reason you need a working pike to
compile from version control is that a number of files required to build
pike are precompiled using a pike based tool. When a source dist is built,
that precompile step is done for you, thus relieving you of the circular
need to have a working pike to get a working Pike. :)
Please don't hesitate to let us know if you run into any other problems.
Bill
On Fri, 14 Mar 2014, Danesh Daroui wrote:
The thing that I had missed was that I needed to have a working version of
Pike installed before. It was actually in the instructions, but I didn't
notice that because I thought that compiling from scratch from the git
repository should also work like other projects. Anyway, I installed Pike
from its source code and now the git branch works too.
Thanks,
D.
On Fri, Mar 14, 2014 at 3:05 AM, H. William Welliver III
<[email protected]>wrote:
Ok, so I've installed autoconf 2.13 on my SL6.4 vm and it looks like it
has the same problem, so 2.13 support in pike must finally be dead. As for
the log file you attached, I don't see any actual errors. Does the build
just not run post-configure? Or is it failing on that call to
precompile.sh? Do you get a core file anywhere?
Bill
snip:
Creating build...
Creating build/linux-2.6.32-279.el6.i686-i686...
Configure arguments:
Use `make CONFIGUREARGS="..." ...' to change them.
They will be retained in the build directory.
Running /home/hww3/pike/src/configure in
build/linux-2.6.32-279.el6.i686-i686
creating cache ./config.cache
configure: warning:
configure script has been generated with autoconf 2.13 or earlier.
checking whether make sets ${MAKE}... yes
checking whether make supports VPATH... no
configure: error:
Building in a separate directory is not supported without VPATH.
Build in the source directory, or try another make (eg gnumake).
On Mar 13, 2014, at 3:23 PM, Chris Angelico <[email protected]> wrote:
On Fri, Mar 14, 2014 at 6:12 AM, Danesh Daroui <[email protected]>
wrote:
I have only the branch for version 8.0. I upgraded my autoconf (it is
weird
if autoconf 2.13 is the source of the problem!) and now the error with
VPATH
is gone, but at the end, compilation fails and no executable is
generated. I
have attached the log file of my compilation. My branch is also
up-to-date.
I have run "git pull" before and "git fetch" continuously. Any help
will be
appreciated. I also got the following warnings which seem not to be a
big
deal:
This bit looks odd, but I can't be sure that's a problem, and what
you're seeing is listed as a warning:
checking gtk/gtk.h usability... yes
checking gtk/gtk.h presence... no
checking for gtk/gtk.h... yes
It's usable but not present. Odd.
Anyway, see if you can run bin/pike - the executable is created deep
in the build directory, but there's a script ~/pike/bin/pike that
should find stuff and run it.
rosuav@sikorsky:~/pike$ bin/pike
Pike v8.0 release 1 running Hilfe v3.5 (Incremental Pike Frontend)
If that works, 'sudo make install' should also work.
ChrisA
