From: namgo <namgo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: EmulationStation fails to start
Date: Tue, 03 Oct 2023 16:36:50 +0200 [thread overview]
Message-ID: <20231003143650.SGdyJJVD00ZangAc3FcfrP-UUeLt-8_qfplQljDFhOU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44861@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
New comment by namgo on void-packages repository
https://github.com/void-linux/void-packages/issues/44861#issuecomment-1745096602
Comment:
I've gotten this installed in a fresh VM, bumping the version within xpbs-src from 2.9.4 to 2.11.2 for EmulationStation.
After installing the updated version, the existing error still occurs.
My instinct is that https://github.com/RetroPie/EmulationStation/issues/427#issuecomment-388524825 is an issue, the compilation process assumes that certain files in the user's home directory are already available.
https://github.com/RetroPie/EmulationStation/issues/427#issuecomment-389709761 provides the paths that are checked. What's confusing to me is that it checks the bindir - they should be checking files outside of the bindir (/usr/bin/retropie -> /usr/share, no?).
This appears to explain why it worked for the packager and not us.
site-note: the patch void has looks like it's no longer necessary as the developers include `time.h` possibly making ctime no longer relevant - unless I misunderstand something.
Edit: https://github.com/RetroPie/EmulationStation/issues/819 should address it. Unless I'm wrong, there's no good way to package this until EmulationStation's basedir assumptions conforms to a spec.
next prev parent reply other threads:[~2023-10-03 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:12 [ISSUE] " Newchair2644
2023-10-03 14:28 ` namgo
2023-10-03 14:36 ` namgo [this message]
2023-10-03 15:25 ` namgo
2023-10-03 18:09 ` namgo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231003143650.SGdyJJVD00ZangAc3FcfrP-UUeLt-8_qfplQljDFhOU@z \
--to=namgo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).