Dear all,
I have downloaded and compiled successfully the source code of Pike-v7.8.700. Now when I clone the git repository of Pike, the make complains about VPATH is not supported by make. I have modified VPATH variable to point to the where the source code (compiled previously) resides, but the problem is still there. Any tip for that?
Regards,
D.
Hi Danesh,
What type of system are you using? What version of make is complaining? I assume you're trying to compile from the 8.0 pre-release branch?
Bill
On Thu, 13 Mar 2014, Danesh Daroui wrote:
Dear all,
I have downloaded and compiled successfully the source code of Pike-v7.8.700. Now when I clone the git repository of Pike, the make complains about VPATH is not supported by make. I have modified VPATH variable to point to the where the source code (compiled previously) resides, but the problem is still there. Any tip for that?
Regards,
D.
Hi there,
I have a Linux machine (OpenSuSE 13.1) and I use GNU Make 3.82. According to the instructions, I cloned the following repository by running
git clone git://pike-git.lysator.liu.se/pike.git
so I am not sure whether it is a pre-release or stable one. Another thing is that I use rather older version of autoconf i.e. 2.13 because newer versions of autoconf are not backward compatible. I am not sure if it can be the source of the problem. I downloaded the source code of Pike and it compiled successfully. The error comes up when I clone the git repository.
Regards,
D.
On Thu, Mar 13, 2014 at 4:36 PM, Bill Welliver bill@welliver.org wrote:
Hi Danesh,
What type of system are you using? What version of make is complaining? I assume you're trying to compile from the 8.0 pre-release branch?
Bill
On Thu, 13 Mar 2014, Danesh Daroui wrote:
Dear all,
I have downloaded and compiled successfully the source code of Pike-v7.8.700. Now when I clone the git repository of Pike, the make complains about VPATH is not supported by make. I have modified VPATH variable to point to the where the source code (compiled previously) resides, but the problem is still there. Any tip for that?
Regards,
D.
Hmm,
As for the branch, you should get something that looks like this (I think the branch will vary depending on the last commit):
[hww3@delta pike]$ git branch 7.6 7.9 * 8.0
So you might need to do a "git checkout 8.0", assuming 8.0 is the version you want.
I also assume you're just doing a simple "make" in the top level directory. That should make everything happen automatically. I don't use autoconf 2.13 any more, but I think it should still work, though i might need to take some time to confirm that.
Bill
On Thu, 13 Mar 2014, Danesh Daroui wrote:
Hi there,
I have a Linux machine (OpenSuSE 13.1) and I use GNU Make 3.82. According to the instructions, I cloned the following repository by running
git clone git://pike-git.lysator.liu.se/pike.git
so I am not sure whether it is a pre-release or stable one. Another thing is that I use rather older version of autoconf i.e. 2.13 because newer versions of autoconf are not backward compatible. I am not sure if it can be the source of the problem. I downloaded the source code of Pike and it compiled successfully. The error comes up when I clone the git repository.
Regards,
D.
On Thu, Mar 13, 2014 at 4:36 PM, Bill Welliver bill@welliver.org wrote:
Hi Danesh,
What type of system are you using? What version of make is complaining? I assume you're trying to compile from the 8.0 pre-release branch?
Bill
On Thu, 13 Mar 2014, Danesh Daroui wrote:
Dear all,
I have downloaded and compiled successfully the source code of Pike-v7.8.700. Now when I clone the git repository of Pike, the make complains about VPATH is not supported by make. I have modified VPATH variable to point to the where the source code (compiled previously) resides, but the problem is still there. Any tip for that?
Regards,
D.
On Fri, Mar 14, 2014 at 3:38 AM, Bill Welliver bill@welliver.org wrote:
As for the branch, you should get something that looks like this (I think the branch will vary depending on the last commit):
[hww3@delta pike]$ git branch 7.6 7.9
- 8.0
So you might need to do a "git checkout 8.0", assuming 8.0 is the version you want.
8.0 ought to be the default, but the above will quickly confirm that.
I also assume you're just doing a simple "make" in the top level directory. That should make everything happen automatically. I don't use autoconf 2.13 any more, but I think it should still work, though i might need to take some time to confirm that.
I've just done a build using autoconf 2.69 on OS X, which worked just fine. That's also the version I use on Debian Linux. I've no idea what's required though.
ChrisA
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:
config.status: WARNING: '/home/danesh/pike/src/Makefile.in' seems to ignore the --datarootdir setting configure: WARNING: No Login-related functions, username and password will be silently ignored configure: WARNING: Outdated postgresql version, using potentially unsafe string escaping function configure: WARNING: gtk/gtk.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: gtk/gtk.h: proceeding with the compiler's result
D.
On Thu, Mar 13, 2014 at 5:54 PM, Chris Angelico rosuav@gmail.com wrote:
On Fri, Mar 14, 2014 at 3:38 AM, Bill Welliver bill@welliver.org wrote:
As for the branch, you should get something that looks like this (I think the branch will vary depending on the last commit):
[hww3@delta pike]$ git branch 7.6 7.9
- 8.0
So you might need to do a "git checkout 8.0", assuming 8.0 is the version you want.
8.0 ought to be the default, but the above will quickly confirm that.
I also assume you're just doing a simple "make" in the top level
directory.
That should make everything happen automatically. I don't use autoconf
2.13
any more, but I think it should still work, though i might need to take
some
time to confirm that.
I've just done a build using autoconf 2.69 on OS X, which worked just fine. That's also the version I use on Debian Linux. I've no idea what's required though.
ChrisA
On Fri, Mar 14, 2014 at 6:12 AM, Danesh Daroui danesh.daroui@gmail.com 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
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 rosuav@gmail.com wrote:
On Fri, Mar 14, 2014 at 6:12 AM, Danesh Daroui danesh.daroui@gmail.com 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
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 bill@welliver.orgwrote:
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 rosuav@gmail.com wrote:
On Fri, Mar 14, 2014 at 6:12 AM, Danesh Daroui danesh.daroui@gmail.com
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
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 bill@welliver.orgwrote:
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 rosuav@gmail.com wrote:
On Fri, Mar 14, 2014 at 6:12 AM, Danesh Daroui danesh.daroui@gmail.com
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
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Chris Angelico -
Danesh Daroui -
H. William Welliver III