 |
|
|
|
|
|
| |
| |
|
|
From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 10:08:01
Message: <528e21d1$1@news.povray.org>
|
|
|
| |
| |
|
|
On 11/21/2013 07:15 AM, Joel Yliluoma wrote:
In the +automake section this is where things start to differ from what
I'm getting:
<snipped a bunch>
> configure.ac:185: error: required file 'unix/config/compile' not found
> configure.ac:185: 'automake --add-missing' can install 'compile'
then I think this is what's causing the rest of the problems:
> source/Makefile.am:35: warning: source file 'frontend/shelloutprocessing.cpp' is
in a subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
> automake: warning: possible forward-incompatibility.
> automake: At least a source file is in a subdirectory, but the 'subdir-objects'
> automake: automake option hasn't been enabled. For now, the corresponding output
> automake: object file(s) will be placed in the top-level directory. However,
> automake: this behaviour will change in future Automake versions: they will
> automake: unconditionally cause object files to be placed in the same
subdirectory
> automake: of the corresponding sources.
> automake: You are advised to start using 'subdir-objects' option throughout your
> automake: project, to avoid future incompatibilities.
> source/Makefile.am:35: warning: source file 'frontend/rendermessagehandler.cpp'
is in a subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
> source/Makefile.am:35: warning: source file 'frontend/console.cpp' is in a
subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
> (and so on repeated for a few dozen cpp files)
> /usr/share/automake-1.14/am/library.am: warning: 'libpovray.a': linking libraries
using a non-POSIX
> /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
> source/Makefile.am:32: while processing library 'libpovray.a'
> vfe/Makefile.am:35: warning: source file 'unix/vfeplatform.cpp' is in a
subdirectory,
> vfe/Makefile.am:35: but option 'subdir-objects' is disabled
> vfe/Makefile.am:35: warning: source file 'unix/unixoptions.cpp' is in a
subdirectory,
> vfe/Makefile.am:35: but option 'subdir-objects' is disabled
> vfe/Makefile.am:35: warning: source file 'unix/unixconsole.cpp' is in a
subdirectory,
> vfe/Makefile.am:35: but option 'subdir-objects' is disabled
> vfe/Makefile.am:35: warning: source file 'unix/platformbase.cpp' is in a
subdirectory,
> vfe/Makefile.am:35: but option 'subdir-objects' is disabled
> /usr/share/automake-1.14/am/library.am: warning: 'libvfe.a': linking libraries
using a non-POSIX
> /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
> vfe/Makefile.am:32: while processing library 'libvfe.a'
>
> + autoconf --warnings=all
<snipped some more>
> sed: can't read ./Makefile.in: No such file or directory
because of the above fail ... I'm thinking there needs to be some kind
of error detection here that makes an aborted sequence apparent
> It generates a "configure" script in "unix/.." .
>
> Then I do: cd ..; ./configure COMPILED_BY="Bisqwit <bis### [at] iki fi>".
> configuring stops at the following error:
> ---------
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: error: cannot find input file: `Makefile.in'
>
>
> Bash's autocomplete gives me the following list of versions of autotools:
>
> unix$ automake
> automake automake-1.14 automake-1.4 automake-1.8 automake-1.9
> unix$ autoconf
> autoconf autoconf2.13 autoconf2.50 autoconf2.59 autoconf2.64
> unix$ autohead
> autoheader autoheader2.13 autoheader2.50 autoheader2.59 autoheader2.64
> unix$ acloc
> aclocal aclocal-1.14 aclocal-1.4 aclocal-1.8 aclocal-1.9
>
> autoconf version is 2.69. automake version is 1.14.
> autoheader version is 2.69. aclocal version is 1.14.
for what it's worth I'm using:
automake (GNU automake) 1.11.1
autoconf (GNU Autoconf) 2.68
autoheader (GNU Autoconf) 2.68
aclocal (GNU automake) 1.11.1
Post a reply to this message
|
|
| |
| |
|
|
From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 11:51:44
Message: <528e3a20$1@news.povray.org>
|
|
|
| |
| |
|
|
On 11/21/2013 10:08 AM, James Holsenback wrote:
> for what it's worth I'm using:
>
> automake (GNU automake) 1.11.1
> autoconf (GNU Autoconf) 2.68
> autoheader (GNU Autoconf) 2.68
> aclocal (GNU automake) 1.11.1
one other thing that /might/ cause problems ... the version of make you
are using. INSTALL file cites version 3.79 or above. on mine:
make --version
returns GNU Make 3.82
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Have you tried the solutions from the thread named "Packaging povray 3.7 stable
for Arch Linux"? The errors look somewhat similar to me.
Best regards,
Post a reply to this message
|
|
| |
| |
|
|
From: clipka
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 15:23:49
Message: <528e6bd5$1@news.povray.org>
|
|
|
| |
| |
|
|
Am 21.11.2013 20:57, schrieb xyproto:
> Have you tried the solutions from the thread named "Packaging povray 3.7 stable
> for Arch Linux"? The errors look somewhat similar to me.
>
> Best regards,
Indeed. Looks like we should consider those as permanent changes to the
Unix build stuff; but we'll need to check when that option was first
supported by automake.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 21 Nov 2013 13:39:31 +0100, clipka wrote:
> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>> I am having trouble building POV-Ray 3.7.
>
> Am I correctly infering from the subject line that you are running a
> non-stable version of Linux?
It's stable all right. What it isn't is stale.
--
Joel Yliluoma
http://iki.fi/bisqwit/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 21 Nov 2013 10:08:00 -0500, James Holsenback wrote:
> On 11/21/2013 07:15 AM, Joel Yliluoma wrote:
>
> In the +automake section this is where things start to differ from what
> I'm getting:
><snipped a bunch>
>> configure.ac:185: error: required file 'unix/config/compile' not found
>> configure.ac:185: 'automake --add-missing' can install 'compile'
Yes, this seems to be the case.
The problem was eventually resolved by running "automake --add-missing"
in the top directory _after_ prebuild.sh was run once, and then running
prebuild.sh again...
This appeared to generate a symlink, compile->/usr/share/automake-1.14/compile
in unix/config/ . Then it configured and compiled properly.
Why does this not happen otherwise?
I have no idea.
--
Joel Yliluoma
http://iki.fi/bisqwit/
Post a reply to this message
|
|
| |
| |
|
|
From: clipka
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 22 Nov 2013 14:43:32
Message: <528fb3e4$1@news.povray.org>
|
|
|
| |
| |
|
|
Am 22.11.2013 20:03, schrieb Joel Yliluoma:
> On Thu, 21 Nov 2013 13:39:31 +0100, clipka wrote:
>> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>>> I am having trouble building POV-Ray 3.7.
>>
>> Am I correctly infering from the subject line that you are running a
>> non-stable version of Linux?
>
> It's stable all right. What it isn't is stale.
Mind you, I'm not talking about stable = not crashing all the time; I'm
talking about stable = has undergone extensive enough testing to use it
in a production environment.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 21 Nov 2013 11:51:43 -0500, James Holsenback wrote:
> one other thing that /might/ cause problems ... the version of make you
> are using. INSTALL file cites version 3.79 or above. on mine:
>
> make --version
>
> returns GNU Make 3.82
3.81 here. But I don't think it's likely that the version of "make" is
relevant here. The errors happen in prebuild.sh which to my knowledge
never invokes "make".
--
Joel Yliluoma
http://iki.fi/bisqwit/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Joel Yliluoma <bis### [at] ikifi> wrote:
> On Thu, 21 Nov 2013 10:08:00 -0500, James Holsenback wrote:
> > On 11/21/2013 07:15 AM, Joel Yliluoma wrote:
> >
> > In the +automake section this is where things start to differ from what
> > I'm getting:
> ><snipped a bunch>
> >> configure.ac:185: error: required file 'unix/config/compile' not found
> >> configure.ac:185: 'automake --add-missing' can install 'compile'
>
>
> Yes, this seems to be the case.
>
>
> The problem was eventually resolved by running "automake --add-missing"
> in the top directory _after_ prebuild.sh was run once, and then running
> prebuild.sh again...
>
> This appeared to generate a symlink, compile->/usr/share/automake-1.14/compile
> in unix/config/ . Then it configured and compiled properly.
>
> Why does this not happen otherwise?
> I have no idea.
>
>
> --
> Joel Yliluoma
> http://iki.fi/bisqwit/
i play with debian testing amd64 too
Thankyou!
i had the same problem and solve in this way...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Same problem here with Ubuntu 14. The problem with the missing Makefile.in
appears when downloading the ZIP. Retrieving with GIT solves the issue.
Joel Yliluoma <bis### [at] ikifi> wrote:
> On Thu, 21 Nov 2013 13:39:31 +0100, clipka wrote:
> > Am 21.11.2013 13:15, schrieb Joel Yliluoma:
> >> I am having trouble building POV-Ray 3.7.
> >
> > Am I correctly infering from the subject line that you are running a
> > non-stable version of Linux?
>
> It's stable all right. What it isn't is stale.
>
> --
> Joel Yliluoma
> http://iki.fi/bisqwit/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
