Package Details: lime3ds-git r10343.ceb97be-1

Git Clone URL: https://aur.archlinux.org/lime3ds-git.git (read-only, click to copy)
Package Base: lime3ds-git
Description: An experimental open-source Nintendo 3DS emulator/debugger
Upstream URL: https://github.com/Lime3DS/Lime3DS
Licenses: GPL-2.0
Conflicts: citra, lime3ds, lime3ds-appimage
Submitter: username227
Maintainer: username227
Last Packager: username227
Votes: 1
Popularity: 0.68
First Submitted: 2024-05-05 04:14 (UTC)
Last Updated: 2024-05-20 22:24 (UTC)

Required by (0)

Sources (37)

Latest Comments

1 2 Next › Last »

username227 commented on 2024-05-14 22:41 (UTC)

OK, the pkgbuild has been updated to use ninja and now should build properly. Let me know if there are any issues.

username227 commented on 2024-05-14 15:45 (UTC)

oh, that's wonderful. Thanks for the update. I appreciate all of your help. I have gone through my pacman logs to see if I could identify a questionable package update with no luck. Let me know if I can be of help, such as with testing. Anything that can be built through this pkgbuild can easily be done in a clean chroot to use best testing practices.

lumenor2 commented on 2024-05-14 15:41 (UTC)

I actually am s0mebodyhelpme on that issue, just fyi.

username227 commented on 2024-05-14 15:38 (UTC) (edited on 2024-05-14 15:38 (UTC) by username227)

This is a complicated project with lots of submodules. It could also be an update to one of the submodules that citra uses, which would affect all of the forks. But in that case, we'd have to figure out why it's only happening on arch. This is more than I am capable of investigating. The best bet is to give it time to see what happens in the issue, now that it's been verified by three different people.

lumenor2 commented on 2024-05-14 15:26 (UTC) (edited on 2024-05-14 15:27 (UTC) by lumenor2)

It could be a change done by all forks (they tend to commit the same things) or an arch-specific issue. I considered that it could be clang/llvm, but even updating those to version 19 from lordheavy's packages gives another error that occurs earlier on in the build. At any rate, this will probably require some more investigation, @username227.

Edit: it is to be noted that i tried to build on a fork that hadn't been updated in 2 months and still failed. This is puzzling.

username227 commented on 2024-05-14 15:10 (UTC)

Interesting. This actually doesn't surprise me. I tried specifying older builds of certain submodules that I suspected might be causing the problem, but with no luck. It could have been an upstream arch change last week that caused the problem, but the only other thing I can think to do is to timeshift back to my backup two weeks ago and retry, but i'm really not willing to do that.

lumenor2 commented on 2024-05-14 15:05 (UTC)

Tried building other forks of Citra. It appears the latest git of every one of them (and even older versions of Lime3DS) fail to build on fresh Arch.

username227 commented on 2024-05-14 11:06 (UTC)

Thanks for letting me know, lumenor. I am getting the same error running the pkgbuild in a clean chroot, and I was getting the same error building manually from the source. Since this is the case, the problem is not with the pkgbuild. The github issue I posted is here for anyone who wants updates:

https://github.com/Lime3DS/Lime3DS/issues/179.

Stay tuned.

lumenor2 commented on 2024-05-14 10:59 (UTC) (edited on 2024-05-14 13:31 (UTC) by lumenor2)

It's not compiling for me towards the end. Reaches 100% but doesn't finish when linking the executable, just like in the issue you posted in Github.

Edit: it should be noted that I'm in a fresh Arch install.

1 2 Next › Last »