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

    lr-mess and lr-mess2016 not compiling

    Scheduled Pinned Locked Moved Help and Support
    compile failedlr-messlr-mess2016
    30 Posts 11 Posters 4.7k 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.
    • H
      hermit
      last edited by

      I managed to compile lr-mess in more than 30 hours
      I'm worried about the update :(
      it would take a procedure where you can choose the drivers / cores

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @hermit
        last edited by

        @hermit said in lr-mess and lr-mess2016 not compiling:

        it would take a procedure where you can choose the drivers / cores

        Just move - before the update - the emulator folder and it shouldn't be caught by the update.

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User
          last edited by

          Sorry for the bump, it seems like the more appropriate topic since it's essentially the same question.

          Has anyone managed to successfully compile lr-mess2016 ?

          I just get the same bug "mess2016_libretro.so not found", after a few hours.
          This seems like the holy grail for mess emulation on the Pi, since lr-mess2016 would be a massive jump in quality from the old mess we currently have. Many machines have had a few years-worth of fixes, including those with which we still struggle to get working properly...i.e.. BBC...etc...
          Would love to get this on the Pi, and I think many here would also feel the same way. Is there any chance of a fix for the compile error ?

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @A Former User
            last edited by

            @John_RM_70 What's the actual error ? The 'not found' is just generic because the compilation fails and the file is not found, but the reason for the failure is somewhere in the logs. Try looking for the most recent log file in ~/RetroPie-Setup/logs, it should have the whole compilation commands and where it failed. What version of RetroPie are you using ?

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @mitu
              last edited by

              @mitu The error is basically the same as the one linked in the OP, the pastebin link.
              I can't post my log file because I cleared it all after 2 fails.
              I have the latest scripts, and my retropie was updated a couple of days ago, so I am on the most recent version.

              mituM 1 Reply Last reply Reply Quote 0
              • mituM
                mitu Global Moderator @A Former User
                last edited by

                @John_RM_70 We still need to see the logs to determine the error. After the discussion in this topic, the memory has been increased during compilation (swap), so it should have worked. I know I compiled lr-mess, but it took more than a few hours.

                ? 1 Reply Last reply Reply Quote 0
                • ?
                  A Former User @mitu
                  last edited by

                  @mitu It's not "lr-mess" that is the problem, this will compile with a larger swap file (2Gb). It's "lr-mess2016" that won't compile due to the missing file "mess2016_libretro.so". No amount of memory configuration will fix that, it has to be server side, not my side.

                  mituM 1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator @A Former User
                    last edited by

                    @John_RM_70 Ah, sorry - I forgot about this (and it's even one of my replies that said it). But, there's someone that patched it to work since this topic was last updated - see this topic.

                    1 Reply Last reply Reply Quote 0
                    • R
                      Raleighguy @mitu
                      last edited by

                      @mitu Quick question: in which file is the compilation concurrency set?

                      mituM 1 Reply Last reply Reply Quote 0
                      • mituM
                        mitu Global Moderator @Raleighguy
                        last edited by

                        @Raleighguy The concurrency is set automatically, based on the #of CPUs you have and the system you're running on. On a PI3, it's probably 2, since it doesn't have enough memory and CPU anyway to sustain 4 compilation threads.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          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.