After the last update of Retropie for RP4 - Could not successfully build lr-flycast

BuZz

@Darksavior no new changes since you last built. That was a change I did earlier. Sorry for confusion, was just detailing what I changed earlier apart from rolling back the code a few commits.

Darksavior

@BuZz Sorry for the delay. Sent. I don't remember when I last built flycast that worked with chd. It was either earlier this week or last week.
Looks like it just got reported as a problem: https://github.com/libretro/flycast/issues/816

BuZz

@Darksavior that's good in a way as it means I didn't break it :-)

I'll bisect it and maybe roll back/revert whatever broke it until it's fixed upstream.

BuZz

@Darksavior I didn't manage to build a revision that worked with a Dreamcast CHD (didn't try Naomi). Some older revisions didn't crash but just didn't recognise it. I'll revisit this but best bet is to wait for upstream to fix the various issues for now I guess.

SartreFan

Had the same issue with lr-Flycast and runncommand log points to line 1247 of the runcommand but it seems unrelated. I did notice this on line 1227:

if [[ "$(ps -o comm= -p $(ps -o ppid= -p $PPID))" != "emulationstatio" ]]; then

Is that supposed to be "emulationstation" instead of "emulationstatio"?

BuZz

@SartreFan that's unrelated (and the missing n is intentional).

tackett1980

@BuZz

Im having the same problem just tried it.

BuZz

@tackett1980 which problem? Please be specific and provide information. This thread has had discussion about more than one issue.

davidgrohl

I installed 4.5.13 and tryied install lr-flycast. I get error while compiling: flycast_libretro.so not found.

mitu

@davidgrohl Did you update youre RetroPie-Setup script ? Please do so and then re-try to install again - a binary install should be available also.

tackett1980

@davidgrohl

This is the same error I get. My retropie script was updated before I tried it too.

BuZz

Can't help without a build log and information about your set up.

rejesterd

Just noting that I was able to update flycast from source just a moment ago. No build errors this time.

davidgrohl

@rejesterd said in After the last update of Retropie for RP4 - Could not successfully build lr-flycast:

Just noting that I was able to update flycast from source just a moment ago. No build errors this time.

Great mate. I’ll try as soon as I can!

rejesterd

@BuZz @Darksavior The flycast update completed successfully today, but now it doesn't load my .chd games like it did before. I didn't test much further before reverting to my working clone from last week, but this is from my original flycast build log from Feb 8th:

git clone --recursive --depth 1 --branch master "https://github.com/libretro/flycast.git" "/home/pi/RetroPie-Setup/tmp/build/lr-flycast"
Cloning into '/home/pi/RetroPie-Setup/tmp/build/lr-flycast'...
HEAD is now in branch 'master' at commit 'fb7d27704bfef725638dd55bc8481456b47aa671'

That's a known working version that can load chd files.. so before the texture-related changes went in, it looks like.

tackett1980

Ok I tried again and got no errors.

I changed nothing I just tried again.

roslof

@rejesterd yeah, I can confirm that rebuilding older versions that used to play nicely with CHDs won't launch CHD games for me either. The "bus error" still appears in the log. Couldn't find much info on that.

It's like some library or configuration file changed and the issue is not build-specific. Trying to learn more, but couldn't find anything unusual in the roms directory, configs/dreamcast, nor opt/retropie/libretrocores directories. Full removal and rebuild yields the same issue.

BuZz

Upstream builds again so I'll be updating the module after testing. The CHD issue could be related to some changes I made so I'll recheck that also.

roslof

@BuZz yeah, I had just figured it out -- Something to do with the recent change to the lr_flycast.sh changes that reference scriptmodules/libretrocores/lr-flycast/01_flags_fix.diff . I reverted to previous lr_flycast.sh and was able to build/run with the latest upstream build.

Appreciated, as always.

BuZz

@roslof yep. previously we were generating armv6 code due to our CFLAGS not being passed during link time optimisation. Lto can be buggy so I may disable it but I'm narrowing down currently which flags are causing the issue.