VRUI – “Unable to locate package”

[solanic]

It didn’t hit me until you said that out loud Sean.

I try not to use Amazon for a lot of reasons.

This is the pc I bought:
https://www.bestbuy.com/site/hp-victus-gaming-desktop-intel-core-i3-12100f-8gb-memory-nvidia-geforce-gtx-1650-512gb-ssd-mica-silver/6504334.p?skuId=6504334

I’ve been staring at the Victus for a couple weeks & saw the Amazon link multiple times & it never occurred to me they could be different. ( nervous grin )

So we helped the community by showing the Victus & TPM chip has issues with 19.3 & 20.1?

I imagine the Pavillion works I guess?

[Sean Robinson]

Missing 1 line of code?

I misread the error and the Linux Mint forum poster is right, the cstddef header is not included in FrameRateViewer.h.

I have been able to build Vrui (and the full AR Sandbox software) in a LM21 virtual machine with two changes. First, the version number has been removed from the libdc1390-dev package. Edit Build-Ubuntu.sh to change libdc1390-22-dev to libdc1390-dev.

Second, FrameRateViewer.h needs to be patched before building. Add a new line to Build-Ubuntu.sh before “make -j$NUM_CPUS INSTALLDIR=$VRUI_INSTALLDIR” (line 65). The added line should contain “patch -p1 < ../../Fix-missing-size_t.patch”.

Create a new text file in the same directory as Build-Ubuntu.sh. This file should be named Fix-missing-size_t.patch and contain the following text.

--- a/Vrui/Vislets/FrameRateViewer.h    2019-07-17 13:48:41.000000000 -0700
+++ b/Vrui/Vislets/FrameRateViewer.h    2022-08-24 09:05:57.472284693 -0700
@@ -27,6 +27,8 @@
 #include <GL/GLNumberRenderer.h>
 #include <Vrui/Vislet.h>

+#include <cstddef>
+
 namespace Vrui {

 namespace Vislets {

Remove the old src directory (if still around) and run the new Build-Ubuntu.sh. Let me know if this works or not.

• This reply was modified 2 years, 3 months ago by Sean Robinson. Reason: fix patch file formatting

[solanic]

SUCCESS SEAN THANK YOU!

How would you recommend we share your fix for Linux Mint 21 in here & Github Issues I opened?

As a rookie, I don’t want to goof how your fix is shared for everyone who’ll see it in the future.

THANK YOU AGAIN! GO ARTICHOKES!

[Sean Robinson]

Congratulations! Now the fun of construction and calibration can begin?

I assume that when @okreylos moves to LM21 the missing include could be added to Vrui for the next release. I don’t think this would cause
backward-compatible problems.

Changing the libdc1390-dev package name will probably be part of an update to Build-Ubuntu.sh when Ubuntu 22.04 LTS and LM21 become recommended distributions. Until that time, the current package name is proper for LM19.

[solanic]

In case this useful for others:

https://forums.linuxmint.com/viewtopic.php?p=2231966#p2231966

So, for anyone else who has this problem: I created a patch for Build-Ubuntu.sh, that doesn’t require a separate patch file. This will work no matter where the build script is located in your machine. Just edit Build-Ubuntu.sh:

[romulogeoflow]

Thanks Sean!

Your solution didn’t work, but I found this one to fix my error.

http://doc-ok.org/?topic=vrui-unable-to-locate-package&paged=2#post-2277

[solanic]

You were able to get your ARS working?
Sorry for delay in reply!

[Author]

Posts