On 16/03/2024 19:40, William F Pokorny wrote:
> On 3/16/24 11:15, kurtz le pirate wrote:
>> Do you think your yuqk is compatible with JellyFish (Ubuntu 22.4.4) ?
> 
> Hi.
> 
> Yes. My primary development machine is running Ubuntu 22.4.4 too.  :-)
> 
> Bill P.
> 

Great !!!

I made my ubuntu's vm, add somes essantials package and libray.
Now, I get this error when run "make" :


---
make[2] : on entre dans le répertoire
« /home/doubled/build_yuqk/povray-3.8.0-x.yuqk_16941651/source »
  CXX      backend/bounding/boundingtask.o
In file included from ../source/backend/bounding/boundingtask.h:58,
                 from backend/bounding/boundingtask.cpp:39:
../source/backend/support/task.h:53:10: fatal error: boost/function.hpp:
Aucun fichier ou dossier de ce nom
   53 | #include <boost/function.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
---

"function.hpp" does not exist anywhere.
What do you think?





-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message

hi,

kurtz le pirate <kur### [at] gmailcom> wrote:
> ...
> I made my ubuntu's vm, add somes essantials package and libray.
> Now, I get this error when run "make" :
> ---


>   CXX      backend/bounding/boundingtask.o
> In file included from ../source/backend/bounding/boundingtask.h:58,
>                  from backend/bounding/boundingtask.cpp:39:
> ../source/backend/support/task.h:53:10: fatal error: boost/function.hpp:
> Aucun fichier ou dossier de ce nom
>    53 | #include <boost/function.hpp>
>       |          ^~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> ---
> "function.hpp" does not exist anywhere.
> What do you think?

I think you're the "victim" of the Debian / Ubuntu "bright minds" -- who split
every software, at least, into three "packages".  "-devel" typically for the
headers, and documentation too needs to be requested, "-doc" I think.  (you'll
need headers for the other to-be-linked-to libraries too)


regards, jr.

Post a reply to this message

On 3/17/24 10:43, kurtz le pirate wrote:
> "function.hpp" does not exist anywhere.
> What do you think?

I'll assume your './configure ...' command ran OK since you are running 
make.

Did you install the libboost-dev or libboost-all-dev Ubuntu package?
You want the latter one - though in total it install much more than 
POV-Ray absolutely needs.

Bill P.

Post a reply to this message

On 17/03/2024 19:10, William F Pokorny wrote:
> On 3/17/24 10:43, kurtz le pirate wrote:
>> "function.hpp" does not exist anywhere.
>> What do you think?
> 
> I'll assume your './configure ...' command ran OK since you are running 
> make.

Yes it is.


> Did you install the libboost-dev or libboost-all-dev Ubuntu package?
> You want the latter one - though in total it install much more than 
> POV-Ray absolutely needs.

libboost-all-dev has fixed the problem.
Now it's the x11 library which causes issues:(

...
...
/usr/bin/ld : disp_x11.cpp:(.text+0x2b8) : référence indéfinie vers
« XDestroyWindow »
/usr/bin/ld : disp_x11.cpp:(.text+0x2c8) : référence indéfinie vers
« XFreeColormap »
/usr/bin/ld : disp_x11.cpp:(.text+0x2d8) : référence indéfinie vers
« XFreeGC »
/usr/bin/ld : disp_x11.cpp:(.text+0x2e4) : référence indéfinie vers
« XCloseDisplay »
/usr/bin/ld : disp_x11.o : dans la fonction
« pov_frontend::UnixX11Display::UpdateScreen(bool) » :
...
...



I'm still researching and learning how Linux works.




-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message

On 3/18/24 12:26, kurtz le pirate wrote:
> Now it's the x11 library which causes issues:(
> 
> ...
> ...
> /usr/bin/ld : disp_x11.cpp:(.text+0x2b8) : référence indéfinie vers
> « XDestroyWindow »
> /usr/bin/ld : disp_x11.cpp:(.text+0x2c8) : référence indéfinie vers
> « XFreeColormap »
> /usr/bin/ld : disp_x11.cpp:(.text+0x2d8) : référence indéfinie vers
> « XFreeGC »
> /usr/bin/ld : disp_x11.cpp:(.text+0x2e4) : référence indéfinie vers
> « XCloseDisplay »
> /usr/bin/ld : disp_x11.o : dans la fonction
> « pov_frontend::UnixX11Display::UpdateScreen(bool) » :
> ...
> ...

I'm still learning how linux works too... :-)

If you cd to the directory:

/lib/x86_64-linux-gnu or /usr/lib/x86_64-linux-gnu/

Can you list libX11 files?  ls -l libX11*

On my Ubuntu machine I see:

-rw-r--r-- 1 root root 2209016 Oct  2 15:13 libX11.a
lrwxrwxrwx 1 root root      15 Oct  2 15:13 libX11.so -> libX11.so.6.4.0
lrwxrwxrwx 1 root root      15 Oct  2 15:13 libX11.so.6 -> libX11.so.6.4.0
-rw-r--r-- 1 root root 1306280 Oct  2 15:13 libX11.so.6.4.0
lrwxrwxrwx 1 root root      19 Oct  2 15:13 libX11-xcb.so.1 -> 
libX11-xcb.so.1.0.0
-rw-r--r-- 1 root root   14048 Oct  2 15:13 libX11-xcb.so.1.0.0

If you don't see these, maybe your libx11 files are located somewhere 
else? If you can find that location, you can add a link time flag to 
point to it.

Aside: In official versions of POV-Ray there is a file in the unix 
directory with more information on the packages to install, but it's out 
of date and I've never gotten around to updating it. So, the yuqk 
tarball doesn't ship with it. Maybe I should bump up the priority there. 


FWIW, it should be you can configure with '--without-x' and get a text 
only version of the 'povray' executable which the yuqk script wraps. It 
will then have no preview display as the Simple Direct Media 'sdl' 
options (like the x11 preview display) also need x11 to work... 'make 
check' should run - and if so, you would be able to render to output 
image files.

Bill P.

Post a reply to this message

On 18/03/2024 21:26, William F Pokorny wrote:

> 
> Can you list libX11 files?  ls -l libX11*
> 
> On my Ubuntu machine I see:
> 
> -rw-r--r-- 1 root root 2209016 Oct  2 15:13 libX11.a
> lrwxrwxrwx 1 root root      15 Oct  2 15:13 libX11.so -> libX11.so.6.4.0
> lrwxrwxrwx 1 root root      15 Oct  2 15:13 libX11.so.6 -> libX11.so.6.4.0
> -rw-r--r-- 1 root root 1306280 Oct  2 15:13 libX11.so.6.4.0
> lrwxrwxrwx 1 root root      19 Oct  2 15:13 libX11-xcb.so.1 -> 
> libX11-xcb.so.1.0.0
> -rw-r--r-- 1 root root   14048 Oct  2 15:13 libX11-xcb.so.1.0.0

Yes, exactly the same thing


> Aside: In official versions of POV-Ray there is a file in the unix 
> directory with more information on the packages to install, but it's out 
> of date and I've never gotten around to updating it. So, the yuqk 
> tarball doesn't ship with it. Maybe I should bump up the priority there. 


I'm going to check the unix distribution to see if there's any
additional information.


> FWIW, it should be you can configure with '--without-x' and get a text 
> only version of the 'povray' executable which the yuqk script wraps. It 
> will then have no preview display as the Simple Direct Media 'sdl' 
> options (like the x11 preview display) also need x11 to work... 'make 
> check' should run - and if so, you would be able to render to output 
> image files.


I'll take a look at it too...



-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message

hi,

kurtz le pirate <kur### [at] gmailcom> wrote:
> On 18/03/2024 21:26, William F Pokorny wrote:
> > Can you list libX11 files?  ls -l libX11*
> >
> > On my Ubuntu machine I see:
> > ...

> Yes, exactly the same thing

strange that the linker does not "see" the X11 libraries.  the linker works off
a set of cached directories, if you still have the same problem, have a look at
'/etc/ld.so.conf' and the files in '/etc/ld.so.conf.d/', are your library paths
listed ?  (if yes, the cache may need refreshing ( run 'ldconfig')).

also, wondering what (exact) arguments were given to './configure'.


regards, jr.

Post a reply to this message

On 20/03/2024 09:53, jr wrote:
> 
> strange that the linker does not "see" the X11 libraries.  the linker works off
> a set of cached directories, if you still have the same problem, have a look at
> '/etc/ld.so.conf' and the files in '/etc/ld.so.conf.d/', are your library paths
> listed ?  (if yes, the cache may need refreshing ( run 'ldconfig')).


everything looks good for '/etc/ld.so.conf' and the files in
'/etc/ld.so.conf.d/'. Library paths are present.


> also, wondering what (exact) arguments were given to './configure'.

in accordance with 'INSTALL.txt' doc :

./configure -q COMPILED_BY="name" CXXFLAGS="-O2" --prefix=/tmp/yuqk_427af17e


no strange argument.

finally, rebuilding the cache with ldconfig solved the problem.
(I should have used -v to track what was going on).


so :
running ldconfig, then ./configure, then make, then after a long long
list of messages : no error :)

last messages on terminal :




cat ./povray.ini.in | sed
"s,__POVLIBDIR__,/tmp/yuqk_427af17e/share/povray-3.8,g" > ./povray.ini







As everything is ok, i run make check
I can see the rendering of an image which also closes when finished.
I don't know where it's saved (or not).

Then run make install.
No error :)



I think all these problems come from the fact that I made a
'./configure' and 'make' with the missing X11 library. Necessary links
and cache to the right shared libraries have become corrupted.



**THANKS** for all Jr.



-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message

hi,

kurtz le pirate <kur### [at] gmailcom> wrote:
> ...
> finally, rebuilding the cache with ldconfig solved the problem.

super.  glad you're "up and running".


> ...
> last messages on terminal :

most got lost, containing accents :-(.


> ...
> As everything is ok, i run make check
> I can see the rendering of an image which also closes when finished.
> I don't know where it's saved (or not).

you wrote you're "new to Linux".  recommend getting to know 'script(1)'.  for
instance when you render a scene, you can "record" all terminal i/o, eg:
  $ script -c 'povray myscene.pov' log-file
and you have a full "transcript" in the 'log-file'.


regards, jr.

Post a reply to this message

On 20/03/2024 20:20, jr wrote:
> 
>> ...
>> last messages on terminal :
> most got lost, containing accents :-(.
> 


hum... hum...

Big differences between nntp and http.
I made screenshots of both interfaces:





-- 
Kurtz le pirate
Compagnie de la Banquise

Post a reply to this message

Attachments:
Download 'nntp.jpg' (56 KB) Download 'http.jpg' (21 KB)

Preview of image 'nntp.jpg'

Preview of image 'http.jpg'