• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Error instaling Retropie 4.6 on Raspbian Buster in a Rpi4 4GbRam

Scheduled Pinned Locked Moved Help and Support
error installretropie 4.6raspberry pi 4
17 Posts 4 Posters 1.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    beyondthegrave
    last edited by 4 May 2020, 04:55

    alt text

    I perform the basic install but it doesn't complete because a missing file Retroarch when cloning from source.

    1 Reply Last reply Reply Quote 0
    • M
      mitu Global Moderator
      last edited by 4 May 2020, 05:04

      The log file you posted cannot be download, I get a Google account prompt. Post the log file - or the portion with the error - on pastebin.com.

      1 Reply Last reply Reply Quote 0
      • B
        beyondthegrave
        last edited by 5 May 2020, 20:57

        The error said:

        Could not successfully build retroarch - Retroarch - front end to libreto emulator cores - required by all lr-* emulators (/home/pi/RetroPie-Setup/tmp/build/retroarch/retroarch not found).

        B 1 Reply Last reply 5 May 2020, 21:05 Reply Quote 0
        • B
          beyondthegrave @beyondthegrave
          last edited by 5 May 2020, 21:05

          @beyondthegrave IMG_20200504_000426325.jpg

          1 Reply Last reply Reply Quote 0
          • M
            mitu Global Moderator
            last edited by mitu 5 Jun 2020, 03:47 5 May 2020, 21:28

            There should be a log file in $HOME/RetroPie/logs/ $HOME/RetroPie-Setup/logs/, which contains the actual error. I was referring to that file's contents. You can remote the existing logs, then attempt another installation to get a fresh log file.

            D 1 Reply Last reply 5 May 2020, 22:31 Reply Quote 0
            • D
              Darksavior @mitu
              last edited by 5 May 2020, 22:31

              @mitu It's $HOME/Retropie-Setup/logs/

              1 Reply Last reply Reply Quote 1
              • B
                beyondthegrave
                last edited by beyondthegrave 5 Jul 2020, 05:09 7 May 2020, 04:08

                I can't find that log.

                I use this tutorial " https://retropie.org.uk/docs/Manual-Installation/ " to install Retropie in Raspbian Buster version.

                How I can delete all the Retropie-Setup directory to get a clean and fresh intallation.

                M 1 Reply Last reply 7 May 2020, 04:15 Reply Quote 0
                • M
                  mitu Global Moderator @beyondthegrave
                  last edited by 7 May 2020, 04:15

                  @beyondthegrave said in Error instaling Retropie 4.6 on Raspbian Buster in a Rpi4 4GbRam:

                  How I can delete all the Retropie-Setup directory to get a clean and fresh intallation.

                  Just delete it using rm, then clone it again.

                  B 1 Reply Last reply 7 May 2020, 05:17 Reply Quote 0
                  • B
                    beyondthegrave @mitu
                    last edited by 7 May 2020, 05:17

                    @mitu I don't know what is the complete command.
                    I have to text only "rm RetroPie-Setup" or I have to use sudo too? This my first time handling a Raspbery Pi.

                    M 1 Reply Last reply 7 May 2020, 05:21 Reply Quote 0
                    • M
                      mitu Global Moderator @beyondthegrave
                      last edited by 7 May 2020, 05:21

                      @beyondthegrave said in Error instaling Retropie 4.6 on Raspbian Buster in a Rpi4 4GbRam:

                      I have to text only "rm RetroPie-Setup" or I have to use sudo too?

                      No, sudo shouldn't be needed.

                      This my first time handling a Raspbery Pi.

                      Then I suggest you install from a pre-made image that you can download from retropie.org.uk/download.

                      B 1 Reply Last reply 7 May 2020, 15:20 Reply Quote 0
                      • B
                        beyondthegrave @mitu
                        last edited by 7 May 2020, 15:20

                        Then I suggest you install from a pre-made image that you can download from retropie.org.uk/download.

                        But the tutorial link in that page only install from the source, and not the downloaded one pre-made image that you recommend me which is in my download folder.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mitu Global Moderator
                          last edited by 7 May 2020, 18:32

                          A manual installation is preferred when you already have a system installed and perhaps some other things installed on it. If you're not in that situation, then you should start with a pre-made image and not a manual installation. It's just an alternative method of getting RetroPie working on a Raspberry Pi.

                          The RetroPie image is based on Raspbian Lite, so if you're starting from scratch, there's no reason to prefer a manual installation over the premade image.

                          1 Reply Last reply Reply Quote 0
                          • O
                            Oldies4ever
                            last edited by 13 May 2020, 20:55

                            Hello,
                            I got the same issue here.

                            From the Log File:

                            ...
                            CC tasks/task_decompress.c
                            CC led/drivers/led_rpi.c
                            LD retroarch
                            /usr/bin/ld: obj-unix/release/gfx/drivers_shader/shader_gl_core.o: in function gl_core_shader::Framebuffer::init()': shader_gl_core.cpp:(.text+0x384): undefined reference to glTexStorage2D'
                            /usr/bin/ld: shader_gl_core.cpp:(.text+0x4d4): undefined reference to glTexStorage2D' /usr/bin/ld: obj-unix/release/gfx/drivers_shader/shader_gl_core.o: in function gl_core_shader::Pass::build_semantic_uint(unsigned char*, slang_semantic, unsigned int)':
                            shader_gl_core.cpp:(.text+0xa74): undefined reference to glUniform1ui' /usr/bin/ld: shader_gl_core.cpp:(.text+0xaa8): undefined reference to glUniform1ui'
                            /usr/bin/ld: shader_gl_core.cpp:(.text+0xaf0): undefined reference to glUniform1ui' /usr/bin/ld: shader_gl_core.cpp:(.text+0xb0c): undefined reference to glUniform1ui'
                            /usr/bin/ld: obj-unix/release/gfx/drivers_shader/shader_gl_core.o: in function gl_core_shader::Pass::build_commands(gl_core_shader::Texture const&, gl_core_shader::Texture const&, gl_core_viewport const&, float const*)': shader_gl_core.cpp:(.text+0x1860): undefined reference to glBindBufferBase'
                            /usr/bin/ld: shader_gl_core.cpp:(.text+0x1a2c): undefined reference to glBindBufferBase' /usr/bin/ld: obj-unix/release/gfx/drivers_shader/shader_gl_core.o: in function gl_core_cross_compile_program':
                            shader_gl_core.cpp:(.text+0x5780): undefined reference to glGetUniformBlockIndex' /usr/bin/ld: shader_gl_core.cpp:(.text+0x57a0): undefined reference to glGetUniformBlockIndex'
                            /usr/bin/ld: obj-unix/release/gfx/drivers_shader/shader_gl_core.o: in function gl_core_filter_chain_create_from_preset': shader_gl_core.cpp:(.text+0x76bc): undefined reference to glTexStorage2D'
                            /usr/bin/ld: obj-unix/release/gfx/drivers/gl.o: in function gl2_read_viewport': gl.c:(.text+0x758): undefined reference to glMapBufferRange'
                            /usr/bin/ld: gl.c:(.text+0x7cc): undefined reference to glUnmapBuffer' /usr/bin/ld: obj-unix/release/gfx/drivers/gl.o: in function gl2_load_texture_image.constprop.26':
                            gl.c:(.text+0x2168): undefined reference to glTexStorage2D' /usr/bin/ld: obj-unix/release/./libretro-common/gfx/gl_capabilities.o: in function gl_query_extension':
                            gl_capabilities.c:(.text+0x84): undefined reference to glGetStringi' /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function gl_core_set_texture_frame':
                            gl_core.c:(.text+0x308): undefined reference to glTexStorage2D' /usr/bin/ld: gl_core.c:(.text+0x420): undefined reference to glTexStorage2D'
                            /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function video_texture_load_gl_core': gl_core.c:(.text+0x5d4): undefined reference to glTexStorage2D'
                            /usr/bin/ld: gl_core.c:(.text+0x6f0): undefined reference to glTexStorage2D' /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function gl_core_read_viewport':
                            gl_core.c:(.text+0x904): undefined reference to glMapBufferRange' /usr/bin/ld: gl_core.c:(.text+0x94c): undefined reference to glUnmapBuffer'
                            /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function gl_core_destroy_resources': gl_core.c:(.text+0xa84): undefined reference to glBindVertexArray'
                            /usr/bin/ld: gl_core.c:(.text+0xba0): undefined reference to glDeleteSync' /usr/bin/ld: gl_core.c:(.text+0xd54): undefined reference to glDeleteVertexArrays'
                            /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function gl_core_init': gl_core.c:(.text+0x1c10): undefined reference to glTexStorage2D'
                            /usr/bin/ld: gl_core.c:(.text+0x1f68): undefined reference to glGenVertexArrays' /usr/bin/ld: gl_core.c:(.text+0x1f70): undefined reference to glBindVertexArray'
                            /usr/bin/ld: gl_core.c:(.text+0x1f78): undefined reference to glBindVertexArray' /usr/bin/ld: obj-unix/release/gfx/drivers/gl_core.o: in function gl_core_frame':
                            gl_core.c:(.text+0x2b70): undefined reference to glBindVertexArray' /usr/bin/ld: gl_core.c:(.text+0x2e14): undefined reference to glBindVertexArray'
                            /usr/bin/ld: gl_core.c:(.text+0x3368): undefined reference to glTexStorage2D' /usr/bin/ld: gl_core.c:(.text+0x3454): undefined reference to glClientWaitSync'
                            /usr/bin/ld: gl_core.c:(.text+0x345c): undefined reference to glDeleteSync' /usr/bin/ld: gl_core.c:(.text+0x35a0): undefined reference to glFenceSync'
                            /usr/bin/ld: obj-unix/release/gfx/drivers_font/gl_core_raster_font.o: in function gl_core_raster_font_upload_atlas': gl_core_raster_font.c:(.text+0x1d0): undefined reference to glTexStorage2D'
                            collect2: error: ld returned 1 exit status
                            make: *** [Makefile:201: retroarch] Error 1
                            /home/pi/RetroPie-Setup
                            Could not successfully build retroarch - RetroArch - frontend to the libretro emulator cores - required by all lr-* emulators (/home/pi/RetroPie-Setup/tmp/build/retroarch/retroarch not found).

                            Log ended at: Wed May 13 17:40:33 -03 2020
                            Total running time: 0 hours, 4 mins, 53 secs

                            M 1 Reply Last reply 14 May 2020, 02:40 Reply Quote 0
                            • M
                              mitu Global Moderator @Oldies4ever
                              last edited by 14 May 2020, 02:40

                              @Oldies4ever How are you installing RetroPie ? RetroArch installs fine from source with the latest RetroPie version.
                              Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

                              1 Reply Last reply Reply Quote 0
                              • O
                                Oldies4ever
                                last edited by 14 May 2020, 17:22

                                Hello @mitu

                                Thank you for your reply.

                                You'll find the requested Info below:

                                Pi Model or other hardware: Raspberry Pi 4 Model B Rev 1.1 4GB - Compatible: raspberrypi,4-model-bbrcm,bcm2711
                                OS: Raspian Buster 10.4 Lite
                                Power Supply used: Original Power Supply - 15.3W / 5.1V / 3.0A DC output
                                RetroPie Version Used: 4.6.1
                                Built From: Source - https://github.com/RetroPie/RetroPie-Setup.git
                                USB Devices connected: Keyboard
                                Controller used: Keyboard
                                Error messages received: "Could not successfully build retroarch - RetroArch - frontend to the libretro emulator cores - required by all lr-* emulators (/home/pi/RetroPie-Setup/tmp/build/retroarch/retroarch not found)."
                                Log found in /dev/shm/runcommand.log (if relevant): N/A
                                Guide used: https://retropie.org.uk/docs/Manual-Installation/
                                File: N/A
                                Emulator: Retroarch

                                Please see the complete log file: https://pastebin.com/pUh02qLn

                                1 Reply Last reply Reply Quote 0
                                • M
                                  mitu Global Moderator
                                  last edited by 14 May 2020, 17:40

                                  Can't reproduce the error - did you modify anything in your config.txt (disabling KMS) ? Don't you have a binary installation option for RetroArch ?

                                  1 Reply Last reply Reply Quote 0
                                  • O
                                    Oldies4ever
                                    last edited by Oldies4ever 14 May 2020, 18:35

                                    Hello @mitu

                                    Thank you very much for your hint about KMS in the config.txt file.
                                    I really didn't paid attention to this.
                                    It was really commented, I don't know why. I didn't ever edit this file.
                                    Now the installation has finished successfully.

                                    The solution was really uncomment the two lines below regarding KMS dtoverlay into /boot/config.txt (and restart) :

                                    [pi4]
                                    # Enable DRM VC4 V3D driver on top of the dispmanx display stack
                                    dtoverlay=vc4-fkms-v3d
                                    max_framebuffers=2
                                    
                                    [all]
                                    dtoverlay=vc4-fkms-v3d
                                    start_x=0
                                    gpu_mem=256
                                    hdmi_enable_4kp60=1
                                    

                                    Thank's a lot for your help. I hope this topic may help many other friends to enjoy Retropie.

                                    Kind Regards.

                                    1 Reply Last reply Reply Quote 1
                                    17 out of 17
                                    • First post
                                      17/17
                                      Last post

                                    Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                    Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                                      This community forum collects and processes your personal information.
                                      consent.not_received