 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/13/2015 04:59 PM, clipka wrote:
...
>
Thanks for the additional information on what libboost-dev really is.
I was thinking some more and two packages not in the unix/README.md
"Dependencies" list that I'd vote to be there are autoconf and
libsdl-dev. We need the autoconf package for the configuration process.
The Simple DirectMedia Layer libsdl-dev package is required for the
povray render display (+D) to work. The need for latter package is
mentioned in the unix/install.txt file, but I expect the display
capability is something most users will want.
So, to be complete for my fresh Unbuntu 14.04 install I ended up running
this set of commands in an xterm window:
sudo apt-get update
sudo apt-get -y install autoconf
sudo apt-get -y install build-essential
sudo apt-get -y install git
sudo apt-get -y install libboost-all-dev
sudo apt-get -y install libjpeg-dev
sudo apt-get -y install libopenexr-dev
sudo apt-get -y install libpng-dev
sudo apt-get -y install libsdl-dev
sudo apt-get -y install libtiff-dev
sudo apt-get -y install unzip
sudo apt-get -y install zlib1g-dev
The generic names resolve to versions of the libraries which are fine
for the povray 3.7* compile. The build-essentail and unzip are likely
redundant/not strictly needed. Further, git is needed for the build only
if pulling/managing the source code with git.
Lastly, you'd asked about versions of boost and gcc. Unbuntu 14.04
libboost-all-dev resolves to boost version 1.54. The gcc compiler
version is 4.8.4.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> We've been having problems with the Unix build process in the past, often
> related to the boost libraries. I'm wondering where we're at with these issues
> right now with the current master branch.
>
> If the 3.7 build process has ever failed to work "out of the box" for you (i.e.
> strictly following the baseline build instructions described in `unix/README`),
> I'd love to hear from you:
>
> - What variant of Unix are you using?
> - What version of the boost library are you using?
>
> - Does the official stable 3.7.0.0 build "out of the box" on your system?
> Otherwise, what problems do you encounter, and how (if at all) do you manage to
> get it to build?
>
> - Does the current master 3.7.1-alpha.8344773 build "out of the box" on your
> system? Otherwise, what problems do you encounter, and how (if at all) do you
> manage to get it to build?
>
> - Any other observations?
>
>
> (Please do NOT reply if the 3.7 build process has always worked perfectly fine
> for you.)
Fails at the ./prebuild.sh in the unix/ directory. This is both on FreeBSD 10.2
and Debian testing with the official stable 3.7.0.0 build. On both systems I
get:
configure.ac:302: the top level
+ cat ./configure
+ sed -e 's,configure.gnu --help=recursive,& --srcdir=$ac_srcdir,g' -e 's,\(cd
\)\($ac_\)\(pop\)*\(dir\),\1"\2\3\4",g' -e
's,$am_aux_dir/missing,\\"$am_aux_dir\\"/missing,g'
+ mv -f ./configure.tmp ./configure
+ chmod +x ./configure
+ rm -f -r ./autom4te.cache
sed: ./Makefile.in: No such file or directory
So, it's not generating Makefile.in for some reason.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 10.03.2016 um 07:22 schrieb jhu:
> "clipka" <nomail@nomail> wrote:
>> We've been having problems with the Unix build process in the past, often
>> related to the boost libraries. I'm wondering where we're at with these issues
>> right now with the current master branch.
...
>> - Does the official stable 3.7.0.0 build "out of the box" on your system?
>> Otherwise, what problems do you encounter, and how (if at all) do you manage to
>> get it to build?
>>
>> - Does the current master 3.7.1-alpha.8344773 build "out of the box" on your
>> system? Otherwise, what problems do you encounter, and how (if at all) do you
>> manage to get it to build?
...
> Fails at the ./prebuild.sh in the unix/ directory. This is both on FreeBSD 10.2
> and Debian testing with the official stable 3.7.0.0 build. On both systems I
> get:
...
> So, it's not generating Makefile.in for some reason.
Okay... but how about 3.7.1-alpha.8344773 or later?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 03/10/2016 01:22 AM, jhu wrote:
> "clipka" <nomail@nomail> wrote:
>> We've been having problems with the Unix build process in the past, often
>> related to the boost libraries. I'm wondering where we're at with these issues
>> right now with the current master branch.
>>
>> If the 3.7 build process has ever failed to work "out of the box" for you (i.e.
>> strictly following the baseline build instructions described in `unix/README`),
>> I'd love to hear from you:
>>
>> - What variant of Unix are you using?
>> - What version of the boost library are you using?
>>
>> - Does the official stable 3.7.0.0 build "out of the box" on your system?
>> Otherwise, what problems do you encounter, and how (if at all) do you manage to
>> get it to build?
>>
>> - Does the current master 3.7.1-alpha.8344773 build "out of the box" on your
>> system? Otherwise, what problems do you encounter, and how (if at all) do you
>> manage to get it to build?
>>
>> - Any other observations?
>>
>>
>> (Please do NOT reply if the 3.7 build process has always worked perfectly fine
>> for you.)
>
> Fails at the ./prebuild.sh in the unix/ directory. This is both on FreeBSD 10.2
> and Debian testing with the official stable 3.7.0.0 build. On both systems I
> get:
>
> configure.ac:302: the top level
> + cat ./configure
> + sed -e 's,configure.gnu --help=recursive,& --srcdir=$ac_srcdir,g' -e 's,\(cd
> \)\($ac_\)\(pop\)*\(dir\),\1"\2\3\4",g' -e
> 's,$am_aux_dir/missing,\\"$am_aux_dir\\"/missing,g'
> + mv -f ./configure.tmp ./configure
> + chmod +x ./configure
> + rm -f -r ./autom4te.cache
> sed: ./Makefile.in: No such file or directory
>
> So, it's not generating Makefile.in for some reason.
>
>
>
Does the suggested fix at the bottom of git issue 54 fix things for your
3.7.0-stable build ?
See: https://github.com/POV-Ray/povray/issues/54
Aside:
-----
Christoph! I believe you can close git issue 54 as that user is
compiling 3.7.0-stable OK.
Also a reminder one of the main reasons for staying with 3.7.0-stable is
the 17-19% performance hit in 3.7.1. My working machines is currently
just a 2 core i3... I confess to not having lately tested performance
for 3.7.1. Have the developers at all addressed the performance issue?
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
William F Pokorny <ano### [at] anonymous org> wrote:
> On 03/10/2016 01:22 AM, jhu wrote:
> > "clipka" <nomail@nomail> wrote:
> >> We've been having problems with the Unix build process in the past, often
> >> related to the boost libraries. I'm wondering where we're at with these issues
> >> right now with the current master branch.
> >>
> >> If the 3.7 build process has ever failed to work "out of the box" for you (i.e.
> >> strictly following the baseline build instructions described in `unix/README`),
> >> I'd love to hear from you:
> >>
> >> - What variant of Unix are you using?
> >> - What version of the boost library are you using?
> >>
> >> - Does the official stable 3.7.0.0 build "out of the box" on your system?
> >> Otherwise, what problems do you encounter, and how (if at all) do you manage to
> >> get it to build?
> >>
> >> - Does the current master 3.7.1-alpha.8344773 build "out of the box" on your
> >> system? Otherwise, what problems do you encounter, and how (if at all) do you
> >> manage to get it to build?
> >>
> >> - Any other observations?
> >>
> >>
> >> (Please do NOT reply if the 3.7 build process has always worked perfectly fine
> >> for you.)
> >
> > Fails at the ./prebuild.sh in the unix/ directory. This is both on FreeBSD 10.2
> > and Debian testing with the official stable 3.7.0.0 build. On both systems I
> > get:
> >
> > configure.ac:302: the top level
> > + cat ./configure
> > + sed -e 's,configure.gnu --help=recursive,& --srcdir=$ac_srcdir,g' -e 's,\(cd
> > \)\($ac_\)\(pop\)*\(dir\),\1"\2\3\4",g' -e
> > 's,$am_aux_dir/missing,\\"$am_aux_dir\\"/missing,g'
> > + mv -f ./configure.tmp ./configure
> > + chmod +x ./configure
> > + rm -f -r ./autom4te.cache
> > sed: ./Makefile.in: No such file or directory
> >
> > So, it's not generating Makefile.in for some reason.
> >
> >
> >
> Does the suggested fix at the bottom of git issue 54 fix things for your
> 3.7.0-stable build ?
>
> See: https://github.com/POV-Ray/povray/issues/54
>
Yes, that works now. Anyway to commit these changes to the official stable zip
file?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 03/10/2016 04:53 PM, jhu wrote:
>> Does the suggested fix at the bottom of git issue 54 fix things for your
>> 3.7.0-stable build ?
>>
>> See: https://github.com/POV-Ray/povray/issues/54
>>
>
> Yes, that works now. Anyway to commit these changes to the official stable zip
> file?
>
>
Christoph asked if the 3.7.1 master branch compiled OK for you as these
fixes and more have been made there for unix builds. Knowing the current
3.7.1 works (or not) for you would be useful, aside from anything else
with 3.7.0-stable, given you are running FreeBSD 10.2 and Debian instead
of Ubuntu 14* or 15*.
Your question specifically about patching the stable branch prompted me
to look more into git/github - which is a new control method to me. I
was able to create a trivial pull request to the master branch for
another matter as a test and it looks to me like we could patch just the
stable branch.
It also looks like the developers have NOT made such patches to stable
for some other unix specific issues. I suppose for wanting to keep
stable, stable and the lack of resource overall.
The question for the developers is: If I create a 3.7.0-stable specific
pull request with these unix build fixes (github issue #54), would it be
merged into the stable branch?
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
William F Pokorny <ano### [at] anonymousorg> wrote:
> Christoph asked if the 3.7.1 master branch compiled OK for you as these
> fixes and more have been made there for unix builds. Knowing the current
> 3.7.1 works (or not) for you would be useful, aside from anything else
> with 3.7.0-stable, given you are running FreeBSD 10.2 and Debian instead
> of Ubuntu 14* or 15*.
Does this require git or is there some other method of downloading it?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 03/14/2016 12:28 AM, jhu wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
>
>> Christoph asked if the 3.7.1 master branch compiled OK for you as these
>> fixes and more have been made there for unix builds. Knowing the current
>> 3.7.1 works (or not) for you would be useful, aside from anything else
>> with 3.7.0-stable, given you are running FreeBSD 10.2 and Debian instead
>> of Ubuntu 14* or 15*.
>
> Does this require git or is there some other method of downloading it?
>
>
You can use git to grab it:
git pull https://github.com/POV-Ray/povray.git master
However, if you go to the https://github.com/POV-Ray/povray web page
there is a download zip option for the master branch on the right hand
side about the middle of the page.
One of the very cool things about github is it seems to built the zips
automatically as the branches get updated.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 03/14/2016 05:25 AM, William F Pokorny wrote:
> On 03/14/2016 12:28 AM, jhu wrote:
>> William F Pokorny <ano### [at] anonymousorg> wrote:
>>
>>> Christoph asked if the 3.7.1 master branch compiled OK for you as these
>>> fixes and more have been made there for unix builds. Knowing the current
>>> 3.7.1 works (or not) for you would be useful, aside from anything else
>>> with 3.7.0-stable, given you are running FreeBSD 10.2 and Debian instead
>>> of Ubuntu 14* or 15*.
>>
>> Does this require git or is there some other method of downloading it?
>>
>>
>
> You can use git to grab it:
>
> git pull https://github.com/POV-Ray/povray.git master
>
> However, if you go to the https://github.com/POV-Ray/povray web page
> there is a download zip option for the master branch on the right hand
> side about the middle of the page.
>
> One of the very cool things about github is it seems to built the zips
> automatically as the branches get updated.
>
> Bill P.
Hit send (before my coffee...) and it occurred to me if you have not
done an initial install with git you would need to have run a clone of
the code repository first to a local directory with :
git clone https://github.com/POV-Ray/povray.git
before using any git pull commands to stay current locally with
particular versions. The above clone will be set to the master branch by
default.
You can switch versions in your local clone with a command like:
git checkout origin/3.7-stable
to switch to the stable branch. Still very much learning git myself...
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 2016-03-14 05:35, also sprach William F Pokorny:
> Still very much learning git myself...
I am usually a shell guy (vs gui if possible) but I really like using
git through SmartGit http://www.syntevo.com/smartgit/ .
--
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
