POV-Ray : Newsgroups : povray.unix : Compile failing on FreeBSD 9.2 Server Time: 17 Jun 2019 07:49:26 GMT
  Compile failing on FreeBSD 9.2 (Message 1 to 6 of 6)  
From: jhu
Subject: Compile failing on FreeBSD 9.2
Date: 13 Dec 2013 03:10:01
Message: <web.52aa7a129fd24322d19b0ec40@news.povray.org>
Povray 3.7

1. Went into unix directory
2. ./prebuild.sh goes fine
3. cd to main directory
4. ./configure COMPILED_BY=" " ends up with:


checking which architecture to optimize for... x86_64-unknown-freebsd9.2 (using
-march=native)

Makefiles
---------
stat: illegal option -- c
usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
stat: illegal option -- c
usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'



Incidentally, it compiles fine in Debian 7.


Post a reply to this message

From: jhu
Subject: Re: Compile failing on FreeBSD 9.2
Date: 13 Dec 2013 03:40:00
Message: <web.52aa81638b6a8ab5d19b0ec40@news.povray.org>
Hmmmm... this is interesting.

If I run ./prebuild.sh on the Linux machine, then copy the entire directory over
to the FreeBSD machine, ./configure will run without a hitch. Unfortunately,
compiling via make will fail unless the following is done

CFLAGS="-Dlseek64" CXXFLAGS=$CFLAGS ./configure

which ends up with

g++ -DHAVE_CONFIG_H  -DPOVLIBDIR=\"/usr/local/share/povray-3.7\"
-DPOVCONFDIR=\"/usr/local/etc/povray/3.7\"
-DPOVCONFDIR_BACKWARD=\"/usr/local/etc\" -I. -I..  -I../vfe/unix  -I../unix
-I../source  -I../source/base  -I../source/backend -pthread -I/usr/local/include
 -pipe -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -s -O3
-ffast-math -march=native -Dlseek64=lseek -D_THREAD_SAFE -pthread -MT
vfeplatform.o -MD -MP -MF .deps/vfeplatform.Tpo -c -o vfeplatform.o `test -f
'unix/vfeplatform.cpp' || echo './'`unix/vfeplatform.cpp
unix/vfeplatform.cpp: In member function 'virtual bool
vfePlatform::UnixShelloutProcessing::ExecuteCommand(const std::string&, const
std::string&)':
unix/vfeplatform.cpp:376: error: 'WEXITSTATUS' was not declared in this scope
*** [vfeplatform.o] Error code 1

Stop in /tank/jhu/temp/povray-3.7.0.0/vfe.
*** [all-recursive] Error code 1

Stop in /tank/jhu/temp/povray-3.7.0.0.
*** [all] Error code 1


Post a reply to this message

From: jhu
Subject: Re: Compile failing on FreeBSD 9.2
Date: 13 Dec 2013 04:50:00
Message: <web.52aa91b78b6a8ab5d19b0ec40@news.povray.org>
Aha! Needed to add #include <sys/wait.h> in vfe/unix/vfeplatform.cpp

So, to compile on FreeBSD 9.2

1. ./prebuild.sh  on a Linux system
2. copy entire directory to FreeBSD system
3. add #include <sys/wait.h> in vfe/unix/vfeplatform.cpp
4. CFLAGS="-Dlseek64=lseek" CXXFLAGS=$CLFAGS ./configure


Post a reply to this message

From: clipka
Subject: Re: Compile failing on FreeBSD 9.2
Date: 14 Dec 2013 01:20:34
Message: <52abb262@news.povray.org>
Am 13.12.2013 04:08, schrieb jhu:

> Makefiles
> ---------
> stat: illegal option -- c
> usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
> stat: illegal option -- c
> usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]

This is a known issue with BSD-style systems, first reported for OS X; 
see GitHub issue #7 for the problem, and how OS X people currently work 
around it:

https://github.com/POV-Ray/povray/issues?state=open

You might also want to read issue #9, and maybe also #5 and #10.

The dev team have already looked into this, and made some code changes 
that will hopefully address the problems, but that code hasn't made its 
way into the Git repo yet.


Post a reply to this message

From: jhu
Subject: Re: Compile failing on FreeBSD 9.2
Date: 14 Dec 2013 17:10:01
Message: <web.52ac8fc28b6a8ab59aa9a0450@news.povray.org>
clipka <ano### [at] anonymousorg> wrote:
> Am 13.12.2013 04:08, schrieb jhu:
>
> > Makefiles
> > ---------
> > stat: illegal option -- c
> > usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
> > stat: illegal option -- c
> > usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
>
> This is a known issue with BSD-style systems, first reported for OS X;
> see GitHub issue #7 for the problem, and how OS X people currently work
> around it:
>
> https://github.com/POV-Ray/povray/issues?state=open
>
> You might also want to read issue #9, and maybe also #5 and #10.
>
> The dev team have already looked into this, and made some code changes
> that will hopefully address the problems, but that code hasn't made its
> way into the Git repo yet.

How about two prebuild.sh scripts, one for Linux systems and one for BSD
systems?


Post a reply to this message

From: clipka
Subject: Re: Compile failing on FreeBSD 9.2
Date: 15 Dec 2013 01:08:06
Message: <52ad00f6$1@news.povray.org>
Am 14.12.2013 18:05, schrieb jhu:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 13.12.2013 04:08, schrieb jhu:
>>
>>> Makefiles
>>> ---------
>>> stat: illegal option -- c
>>> usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
>>> stat: illegal option -- c
>>> usage: stat [-FLnq] [-f format | -l | -r | -s | -x] [-t timefmt] [file ...]
>>
>> This is a known issue with BSD-style systems, first reported for OS X;
>> see GitHub issue #7 for the problem, and how OS X people currently work
>> around it:
>>
>> https://github.com/POV-Ray/povray/issues?state=open
>>
>> You might also want to read issue #9, and maybe also #5 and #10.
>>
>> The dev team have already looked into this, and made some code changes
>> that will hopefully address the problems, but that code hasn't made its
>> way into the Git repo yet.
>
> How about two prebuild.sh scripts, one for Linux systems and one for BSD
> systems?

The differences are comparatively minor, so having two scripts would 
probably just add unnecessary maintenance overhead for the future. If 
the fix we've come up doesn't work, the next best thing would probably 
be a small conditional block in the prebuild.sh script, governed either 
by some smart BSD-detection code or a simple script parameter.


Post a reply to this message

Copyright 2003-2008 Persistence of Vision Raytracer Pty. Ltd.