Error Buiding on : Ubuntu 22.04 <div class="highlight highligh

yes, i am getting the gear output on the screen : <a href="https://user-images.git

I ran the command till here and getting this output : <div class="highlight highl

Getting this error while building the code about quad HOT 10 CLOSED

pranav083 commented on July 24, 2024

Getting this error while building the code

from quad.

Comments (10)

jpieper commented on July 24, 2024 1

That is not the problem, there are multiple aliases for that URL already. The actual problem is that no 'python' executable is present in your system path.

Can you try doing a sudo apt install python-is-python3 ?

from quad.

pranav083 commented on July 24, 2024

Thanks for the help. After installing that package it was build successfully.

INFO: From PackageTar mech/quad_deploy.tar:
Duplicate file in archive: ./mech/libavutil.so, picking first occurrence
Duplicate file in archive: ./mech/libswscale.so, picking first occurrence
Duplicate file in archive: ./mech/libswresample.so, picking first occurrence
Duplicate file in archive: ./mech/libavcodec.so, picking first occurrence
Duplicate file in archive: ./mech/libavformat.so, picking first occurrence
Duplicate file in archive: ./mech/libavfilter.so, picking first occurrence
Duplicate file in archive: ./mech/libavdevice.so, picking first occurrence
INFO: Elapsed time: 3960.266s, Critical Path: 196.43s
INFO: 4295 processes: 4295 linux-sandbox.
INFO: Build completed successfully, 4313 total actions
//base:test                                                              PASSED in 2.7s
//ffmpeg:ffmpeg_test                                                     PASSED in 0.4s
//gl:test                                                                PASSED in 0.3s
//mech:test                                                              PASSED in 0.2s

Executed 4 out of 4 tests: 4 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeoutINFO: Build completed successfully, 4313 total actions

After That I ran the next command :

mighty@ideapad:~/Documents/project/quad$ ./bazel-bin/simulator/simulator -c configs/quadruped.ini
freeglut (./bazel-bin/simulator/simulator): 
mighty@ideapad:~/Documents/project/quad$

This the output i get. then i follow the given http://localhost:4778/ but it not showing any output the given link.

This is the output i received.

from quad.

jpieper commented on July 24, 2024

Hmmm, I'm not sure. On a local 22.04 system when I run that command I get a 3D window that shows which displays a rendering of the robot.

You may have to debug using gdb or similar to see why the process is exiting early. Does 3D rendering work on your machine generally?

from quad.

pranav083 commented on July 24, 2024

can you please refer any guide on how to check it, especially 3d rendering in system,
and about the gdb do i have to run a different command

from quad.

jpieper commented on July 24, 2024

If you don't know about gdb, then it is probably not feasible to walk you through using it in github issues.

Regarding 3d rendering, can you run:

sudo apt install mesa-utils
glxgears

And does it show some 3d gears?

from quad.

pranav083 commented on July 24, 2024

yes, i am getting the gear output on the screen :
Screencast from 03-05-23 09:30:50 PM IST.webm

And regarding gdb, i have little knowledge about it to how to see the error.

from quad.

jpieper commented on July 24, 2024

Something is likely failing in the freeglut initialization. You'll have to learn how to use a debugger, step through it, and figure out what the problem is on your machine.

gdb can be started with:

gdb --args ./bazel-bin/simulator/simulator -c configs/quadruped.ini

You can set a breakpoint at the initialization by using:

b simulator.cc:67

quad/simulator/simulator.cc

Line 67 in 42bbbff

glutInit(&argc, argv);

You can start the program with

run

And then you can use:

step

to step line by line and figure out where the third party library freeglut fails on your system.

You may have to re-run bazel with -c dbg to get debugging symbols, although that in itself may be a large rabbithole.

from quad.

pranav083 commented on July 24, 2024

Sure , i will try and update you for the same.

from quad.

pranav083 commented on July 24, 2024

I ran the command till here and getting this output :

mighty@ideapad:~/Documents/project/quad$ gdb --args ./bazel-bin/simulator/simulator -c configs/quadruped.ini
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./bazel-bin/simulator/simulator...
(No debugging symbols found in ./bazel-bin/simulator/simulator)
(gdb) b simulator.cc:67
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (simulator.cc:67) pending.
(gdb) run
Starting program: /home/mighty/.cache/bazel/_bazel_mighty/df757a1871e2aa5b6c050095b8fde222/execroot/com_github_mjbots_mech/bazel-out/k8-opt/bin/simulator/simulator -c configs/quadruped.ini
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe88be640 (LWP 77181)]
[New Thread 0x7fffe3fff640 (LWP 77182)]
[New Thread 0x7fffdb7fe640 (LWP 77183)]
[New Thread 0x7fffe37fe640 (LWP 77184)]
freeglut (/home/mighty/.cache/bazel/_bazel_mighty/df757a1871e2aa5b6c050095b8fde222/execroot/com_github_mjbots_mech/bazel-out/k8-opt/bin/simulator/simulator): 
[Thread 0x7fffe37fe640 (LWP 77184) exited]
[Thread 0x7fffdb7fe640 (LWP 77183) exited]
[Thread 0x7fffe3fff640 (LWP 77182) exited]
[Thread 0x7fffe88be640 (LWP 77181) exited]
[Inferior 1 (process 77178) exited with code 01]
(gdb)

It is not able to put the break point as it is not build with the debug symbol enable.

But for me it look more complex than it look from outside.
I you have some plan to put this package up and running in the near future. please update it.

Thanks for the help.

from quad.

jpieper commented on July 24, 2024

Sorry you weren't able to get it working. There must be something different on your machine than on the ones I have tried, but it will be time consuming to figure it out.

Thanks for your patience!

from quad.

Getting this error while building the code about quad HOT 10 CLOSED

Comments (10)

Related Issues (3)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent