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

    Compilation failing for lr-mame2003. Seems likely due to OS-misdetection

    Scheduled Pinned Locked Moved Help and Support
    compiling mamemintmint 20
    3 Posts 2 Posters 250 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.
    • P
      phx
      last edited by

      CPU: AMD 3400G
      Host OS: Linux Mint 20.2
      Build From: Downloaded from GitHub (https://github.com/RetroPie/RetroPie-Setup.git)

      Not sure if this would be a topic for the devs of the individual emulators, but as it seems to occur across emulators it may be a RetroPie-specific issue

      When building the base install, several emulators fail including LR-MAME2003 and LR-Mupen64plus. The base cause seems to be OS misdetection, and Mupen64plus fails while looking for a "windows.h" while MAME2003 fails indicating a missing mame2003_libretro.so as it builds mame2003_libretro.dll instead

      This host has just had the OS freshly installed and previous Retropie installs worked fine, so something seems to have changed in the last 6mo

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

        @phx said in Compilation failing for lr-mame2003. Seems likely due to OS-misdetection:

        Not sure if this would be a topic for the devs of the individual emulators, but as it seems to occur across emulators it may be a RetroPie-specific issue

        Some libretro based projects use a quite similar makefile, which uses uname to determine the system type and trips when the hostname contains [W|w]in, thinking it's a Windows system. What's your hostname ?

        P 1 Reply Last reply Reply Quote 0
        • P
          phx @mitu
          last edited by

          @mitu you, my friend, are a genius (and this is really a stupid bug)
          Yes, the hostname was Inwin as that particular system lives in an Inwin mini-ITX case. Changing the hostname of the system fixed it!

          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.