ns 3.38 installation error on Windows 10 (DyOxgen & Texlive)

[Dr. "A"]

Hi, 

I installed the pre-requisites ns3 release 3.38 for Windows 10 as detailed in Installation guide (nsnam.org) except the manual installation of the official Texlive, due to unclear instructions. 

Now, I get the following errors when building ns3 (built up to 87%);

 

What are the sources of these errors?

Is it related to Texlive or something else and how to resolve these errors?

--Ramy

[Tommaso Pecorella]

Hi,

TeXlive and Doxygen are used to build the documentation, and they shouldn't prevent the "build" to finish.

To clarify...

• "ns3 build" -> builds the libraries and the scripts
• "ns3 build docs" -> creates a local copy of the documentation (and it needs the above).

Typically a user can avoid to build the documentation, as it takes time, space, and there's the one online anyway.

[Tommaso Pecorella]

BTW, about why your build failed... I have no idea. You should have some warnings or errors in the preceding lines. Or you could be out os space on the device.

[Ramy]

Hi Tommaso,

Thanks for the prompt response. couple of points in response to your comments;

- there were no descriptive info in the errors

- i suspected doxygen related issue only because I was not able to install texlive and the build errors happened when he build is referring to print-introspected-dyoxygen 

- there is still a lot of storage space, so I'm not sure OS space is limited. 

I have seens some issues related to print-introspected-dyoxygen and in general windows installation that Gabriel Ferreira has fixed. I hope he chimes in this discussion. 

Thanks

--Ramy

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/BGJIUARDV84/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/854cafd0-6bd9-4b63-a381-74d21bdaacacn%40googlegroups.com.

[Gabriel Ferreira]

Tommaso is definitely correct. Doxygen and TexLive are not required for builds, just for docs.

As far as I know, print-introspected-doxygen is a program that emits doxygen for attributes and stuff like that.

The actual error should be upwards in the log, which by the way seems really bugged in a trippy way. Is that Putty (standalone or msys2), or a different shell?

[Ramy]

Hi Gabriel,

Thanks for the response. Ok, good to know it is not related to doxygen or Texlive. 

Here are my answers to your comments

1- I am doing ./ns3 build  // so I'm doing the normal build not the doc one

2- As I said before there was no error in the log upwards. But I ran the build with verbose and I attached the log (beginning of log is cropped though, that's what I could capture from the terminal. Let me know if it is enough or there is a place in the build directory, I can share the full log from)

3- The shell is the integrated VS code bash terminal (bash downloaded with MSys2/Mingw64)

I truly appreciate it if you can point to a resolution.

Regards

Ramy

To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/7719b709-aa08-4974-b979-05caf85e7654n%40googlegroups.com.

[Tommaso Pecorella]

Stupid question... are you sure you have space left on the device ?

[Ramy]

no. It's a good question. I am not 100% sure but 1) I monitor the RAM utilization and it's not 100%  2) the build fails in the very last bit (close to 98% of build completion) at the same point each time, 3) I increased the swap file size and had the same issue. 

I believe it's something to do with the build environment.

attached the build configuration log. Based on the info in this email and the prior one, I hope you or Gabriel can provide some pointers to a resolution or provide specific instructions to collect logs that enable us to understand the problem. 

Thanks

Ramy

To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/7e47878a-4898-4ec3-ac1a-dcfddb561e14n%40googlegroups.com.

[Gabriel Ferreira]

Based on these specific logs, I can't say much. The line I really wanted to read is completely garbled.

>  lidate [ 1%] Building CXX objecctCo omunptsiiolllesir/d CagMteaenk eecFroiamltpeeisdl/ epdrre ipgneetnn-deiernnatctrieoedss p deoecfpt eetndad-redgnocexitye gsse cnro.fdait crh/_tpsarcrrgientt a-sticcnrhta-rtsocihs_mpuselcuabttedodir-r d_osxcyrgaetnc.hc-cs.uobbdji

Would you mind installing ninja and trying again? pacman -S mingw-w64-x86_64-ninja && ./ns3 clean && ./ns3 configure && ./ns3 build