Jump to content
Sign in to follow this  
Palaiologos

ModIo.cpp errors SVN Linux

Recommended Posts

Hello, It seems that I'm incorrectly compiling code. After the 'make  -j3' command per the build instructions for debian, ModIo.cpp errors appear which I assume means the compiling was unsuccessful. There are a few added screen shot attachments as well if it helps. Thanks for your time in advance.2.thumb.png.47039870704bddeb20afca4f3da11e15.png

4.png

Screenshot from 2018-05-05 05-19-22.png

Screenshot from 2018-05-05 05-20-10.png

Screenshot from 2018-05-05 05-33-06.png

Screenshot from 2018-05-04 06-14-52.png

Share this post


Link to post
Share on other sites

That's probably because the libsodium in your package manager is too old. I can't remember the exact version number but it should be superior to 1.0.0.14

Share this post


Link to post
Share on other sites

Too old or not installed. Check the Build Instructions page for the required minimum version.

  • Like 1

Share this post


Link to post
Share on other sites

So you habe installed libsodium manually?

If so check if you still have the system libsodium package installed. (You should remove that)

Share this post


Link to post
Share on other sites

@Imarok

23 hours ago, Palaiologos said:

libsodium-stable-2018-05-05.tar.gz  29-Apr-2018 15:48

So, what your saying is to do an auto-removal of the libsodium.tar in my above post? or all libsodium packages that are seen in synaptic?

20 hours ago, Imarok said:

system libsodium package

Which one would that be exactly? Apologies for confusion here. Also, I made sure to take into consideration per the build instructions that it was the most recent or required version, as @elexis and @stanislas69 have also pointed out in regards to.

10.png

Share this post


Link to post
Share on other sites

@elexis

1 hour ago, elexis said:

Did you run clean-workspaces.sh after installing/updating libsodium? 

 Yes, was not fully thorough when providing the initially posted screen-shots showing various terminal commands etc., didn't include that part, but with libsodium installed, ran './clean-workspaces.sh'  as @(-_-) had first suggested in the  '0ad/build/workspaces' folder and followed that with apt update all packages and still the same errors persist in the same ModIo.cpp location.

@Imarok

1 hour ago, Imarok said:

Just remove/uninstall all libsodium you have on your machine, then install only the newest one manually. 

Ok, will do.

Share this post


Link to post
Share on other sites
1 hour ago, ffffffff said:

maybe need after sudo make install

LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/" binaries/system/pyrogenesis&

to start

just mentioning

was my god case

Yeah, that could do the same as my suggestion. (Assuming it does what it looks like...)

Share this post


Link to post
Share on other sites

@Imarok Yes, in which the ModIo.cpp errors are now no longer appearing and compiling seems to complete itself. No, when it comes to this part of the process as shown in the second screenshot of original posting, which at first I had assumed were somehow correlated with the ModIo.cpp errors...

Testing

Run the automated tests to verify that everything works as expected like this:

cd ../../..
binaries/system/test

Running

If everything went well, compiling the code worked and all tests passed, it's finally time to run the game:

binaries/system/pyrogenesis

@ffffffff

18 hours ago, ffffffff said:

after sodium lib compile in sodium source folder (make...)

sudo make uninstall in the sodium source folder.

and install again with sudo make install.

then start again compile of 0ad in 0ad source folder.

if it same error try LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/" make

in gcc folder of 0ad 

19.thumb.png.80203e74d85333f45e064530910be169.png

Followed up with...

20.thumb.png.4d2b74d02de9dbd1fca75168d04ce574.png

12.png

13.png

Share this post


Link to post
Share on other sites
9 hours ago, ffffffff said:

first u dont need sudo to make,

only when make install,

so make without sudo

and then sudo make install

then

LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/"  make means it must stand before make as it setting an environmental variable for make.

He doesn't need any inlude paths, as compiling works now.

@Palaiologos have you done update-workspace before? (Without sudo)

Share this post


Link to post
Share on other sites

@Imarok @mapkoc @ffffffff

 

13 hours ago, Imarok said:

have you done update-workspace before?

Yes, without sudo

On 5/6/2018 at 10:11 AM, ffffffff said:

was my god case

Is this an expression in coding?

20 hours ago, mapkoc said:

Did you try to include this path instead? /usr/local/lib/sodium

33.thumb.png.9b3f0d0e15cfd6aeb0bf7903def3a3fb.png

23 hours ago, ffffffff said:

make without sudo

and then sudo make install

then

LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/"

31.thumb.png.efaae958d2da5750708be67e964a693a.png

23 hours ago, ffffffff said:

first u dont need sudo to make,

only when make install

Thanks, learned something new.

30.png.72e5b236881ae940e11506915099afda.png

34.thumb.png.339c700e4ea180fe9e969ba048c446f8.png

 

 

Share this post


Link to post
Share on other sites
16 minutes ago, Palaiologos said:

Is this an expression in coding?

No, that is the white Gaussian noise  @ffffffff  sometimes emits.

I think you need to do make clean and cleanworkspace with sudo and after that updateworkspace and make without sudo.

(Already heard 10,000 days? ;P)

Share this post


Link to post
Share on other sites
23 minutes ago, Imarok said:

No, that is the white Gaussian noise  @ffffffff  sometimes emits.

Heh :) (begins to aimlessly read up on Information Theory)

24 minutes ago, Imarok said:

I think you need to do make clean and cleanworkspace with sudo and after that updateworkspace and make without sudo. 

Will be sure to mess that up somehow. ;)

26 minutes ago, Imarok said:

(Already heard 10,000 days? ;P) 

Fan too I presume?

Felt appropriate to get through sudo this, no sudo this, sudo that, sudo here, sudo there, sudo, Sudo! SUDO!! Appreciate your help.

 

Share this post


Link to post
Share on other sites

You can skip compiling tests with make pyrogenesis.

My system has
/usr/include/sodium.h
/usr/include/sodium/core.h
...
/usr/lib/libsodium.so
/usr/lib/libsodium.so.23
/usr/lib/pkgconfig/libsodium.pc

look at the paths

Share this post


Link to post
Share on other sites
On 5/7/2018 at 7:05 AM, ffffffff said:

LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/"

 

On 5/7/2018 at 9:36 AM, mapkoc said:

Did you try to include this path instead? /usr/local/lib/sodium

"Depending on where the software is being installed, you might need escalated permissions for this step so you can copy files to system directories. Using sudo will often do the trick"

 

"The tarball you download usually doesn’t include a finished Makefile. Instead it comes with a template called Makefile.in and the configure script produces a customised Makefile specific to your system."

Essentially, we are trying to merge the libsodium package into the proper filesystem?

65.png

Share this post


Link to post
Share on other sites

Is compiling still not working for you?

If so remember to always state:

What are you trying to do?

What have you done?

What works?

In what way and how does it work not?

Share this post


Link to post
Share on other sites
1 hour ago, ffffffff said:

i had to do also (after install)


sudo ln -s /usr/local/lib/libsodium.so.18.4.0 /usr/local/lib/libsodium.so.23

or


sudo ln -s /usr/local/lib/libsodium.so /usr/local/lib/libsodium.so.23

but then from 0ad source folder


LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/" binaries/system/pyrogenesis

works

u can also go to 0ad ppa and download libsodium from within the next few days when a23 released ricotz is going to upload correct sodium package to ppa for ubuntus

Afaik all that is NOT needed if you have installed libsodium only manually and don't have any other version around.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...